The release of the new version of DXVK 1.9 has just been announced in which several changes have been made, of which the YUV textures, improvements in latencies and frames stand out. This new version of DXVK requires drivers that support Vulkan 1.1 API, such as Mesa RADV 20.2, NVIDIA 415.22, Intel ANV 19.0, and AMDVLK.
For those who are unfamiliar with the project, they should know that it is a tool that can convert Microsoft DirectX 11 and DirectX 10 graphic calls to Vulkan, the open source graphics API that is compatible with Linux. To use DXVK, in addition to Wine and Vulkan, you will obviously need a Vulkan-compatible GPU.
Main new features of DXVK 1.9
In this new version it is highlighted that added initial support for color subsampling YUV texture formats, such as NV12, which is used for video playback in some games.
Besides that ID3D11VideoProcessor API was implemented, used for video output in the games Nier Replicant and Contra: Rogue Corps and also added support for conservative rasterization for GPUs that support this function. The change allows the NVIDIA ShadowLibs option to be used in Final Fantasy XV and other games.
Moreover, a reduced display lag is mentioned, which can solve problems in games limited by Vsync, FPS caps or DXGI settings and also stopped sending information to applications about Vulkan software implementations, such as Lavapipe, if there is a Vulkan-enabled GPU in the system, which solves problems when games try to use Lavapipe instead of correct controller. To enable Lavapipe, it is proposed to set the environment variable VK_ICD_FILENAMES.
Of the other changes that stand out:
- A component has been added to limit the frame rate limiter, which can be used for the correct operation of games that are not designed for high FPS.
- Improved loading of textures and buffers in D3D9.
- Fixed source overlay not appearing when using DXGI implementation of DXVK
- A workaround has been disabled to reduce the number of random crashes in Nvidia drivers, as the underlying driver issue was fixed in versions 465.xx, which may improve performance in some games.
- Fixed precision issues in shaders not having the refactoringAllowed flag set.
- Fixed some potential issues related to image erasure that could lead to artifacts or broken rendering.
- Fixed an issue where games with uppercase file extensions could create duplicate records or cache files.
Finally if you are interested in knowing more about it About this new release, you can check the details In the following link.
How to add DXVK support to Linux?
DXVK can be used to run 3D applications and games on Linux using Wine, acting as a higher-performance alternative to Wine's built-in Direct3D 11 implementation that runs on OpenGL.
DXVK requires the latest stable version of Wine to run. So, if you don't have this installed. Now we will only have to download the latest stable package of DXVK, this one we found In the following link.
wget https://github.com/doitsujin/dxvk/releases/download/v1.9/dxvk-1.9.tar.gz
After having made the download now we are going to unzip the package just obtained, this can be done with from your desktop environment or from the terminal itself by executing in the following command:
tar -xzvf dxvk-1.9.tar.gz
Then we access the folder with:
cd dxvk-1.9
And we execute the sh command to run the install script:
sudo sh setup-dxvk.sh install
setup-dxvk.sh install --without-dxgi
When installing DXVK in a prefix of Wine. The advantage is that Wine vkd3d can be used for D3D12 games and DXVK for D3D11 games.
Also, the new script allows the dll to be installed as symbolic links, making it easier to update the DXVK to get more Wine prefixes (you can do this via the –symlink command).
How will you see the folder DXVK contains two other dlls for 32 and 64 bits these we are going to place them according to the following routes.
Where "user" you replace it with the username you use in your Linux distribution.
For 64 bits we put them in:
~/.wine/drive_c/windows/system32/
O
/home/”usuario”/.wine/drive_c/windows/system32/
And for 32 bits in:
~/.wine/drive_c/windows/syswow64
O
/home/”usuario”/.wine/drive_c/windows/system32/