{"id":105517,"date":"2022-11-10T21:36:38","date_gmt":"2022-11-10T19:36:38","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-dxvk-2-0-realizaczii-direct3d-9-10-11-poverh-api-vulkan"},"modified":"2022-11-10T21:36:38","modified_gmt":"2022-11-10T19:36:38","slug":"vypusk-dxvk-2-0-realizaczii-direct3d-9-10-11-poverh-api-vulkan","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-dxvk-2-0-realizaczii-direct3d-9-10-11-poverh-api-vulkan","title":{"rendered":"Release of DXVK 2.0, providing Direct3D 9\/10\/11 implementation over the Vulkan API","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of DXVK 2.0 is now available, offering an implementation of DXGI (DirectX Graphics Infrastructure), Direct3D 9, 10, and 11 that works through call translation to the Vulkan API. To use DXVK, drivers supporting Vulkan API 1.3 are required, such as Mesa RADV 22.0, NVIDIA 510.47.03, Intel ANV 22.0, and AMDVLK. DXVK can be used to run 3D applications and games on Linux with Wine, serving as a higher-performance alternative to the built-in Wine implementations of Direct3D 9\/10\/11 that run on top of OpenGL. <\/p>\n
Key Changes: <\/p>\n
\n
The requirements for the Vulkan graphics API version have been raised \u2014 now a driver supporting Vulkan 1.3 is required (previously Vulkan 1.1 was necessary), enabling the implementation of new features related to shader compilation. In practice, DXVK 2.0 can be run on any system that supports using the Proton Experimental package to run games based on D3D11 and D3D12. Winevulkan requires at least Wine 7.1 to operate.\n
The accepted code from the dxvk-native project allows the creation of native DXVK builds for Linux (not tied to Wine), which can be used not only for running Windows applications but also in regular Linux applications, which can be beneficial for creating game ports for Linux without altering the D3D-based rendering code.\n
Support for Direct3D 9 has been expanded, including improved memory management (using reflected files in memory for storing texture copies), the implementation of correct reading from active rendering areas (solving issues with artifacts while playing GTA IV), and a redesigned implementation for transparency checking.\n
For Direct3D 10, the delivery of the d3d10.dll and d3d10_1.dll libraries has been discontinued, as they were not installed by default due to the presence of a more advanced D3D10 implementation in Wine. However, support for the D3D10 API continues in the d3d10core.dll library.\n
Support for Direct3D 11 has been brought up to the functionality level of 12_1 (D3D11 Feature Level), achieving which has involved implementing features such as tiled resources (Tiled Resources), conservative rasterization (Conservative Rasterization), and rasterizer ordered views (Rasterizer Ordered Views).\n
The implementation of the ID3D11DeviceContext interface has been reworked and adjusted to behave more like Windows, representing the device context that generates rendering commands. This revision has improved compatibility with third-party libraries and reduced CPU load. In particular, CPU load has been decreased in games that heavily use deferred contexts (for example, the game Assassin's Creed: Origins) or frequently call the ClearState operation (for instance, the game God of War).\n
Changes related to shader compilation have been made. With Vulkan drivers that support the VK_EXT_graphics_pipeline_library extension, shader compilation for Vulkan has been implemented during the loading of D3D shaders by games, rather than during rendering, resolving issues with stuttering caused by shader compilation during gameplay. The required extension is currently only supported in proprietary NVIDIA drivers starting from version 520.56.06.\n
The Vulkan memory model has been implemented in D3D11 shaders.\n
The limitation on the number of resources that can be bound at one time has been removed.\n
Issues manifesting in games have been addressed:\n