- Driver compatibility
A Vulkan 1.3 capable driver and wine version are required to run
this version of DXVK. See the driver support page for details.
Many features in this release, especially the shader compilation
changes detailed below, require the use of modern Vulkan features,
such as Dynamic Rendering, Extended Dynamic State, and Null
Descriptors. Due to the significant changes required to make use
of them, it was no longer practical to maintain and test code paths
for older drivers which do not support these features.
In practice, any system capable of running D3D11 and D3D12 games
using Proton Experimental right now will be able to run DXVK 2.0.
Note: Third-party Vulkan layers that were not updated for Vulkan 1.3 will no longer work.
D3D9 changes
- Memory management improvements
In order to reduce the likelihood of running out of address space in
32-bit D3D9 games, DXVK will now use memory-mapped files to store
shadow copies of textures. This allows us to unmap memory that is
not being used by the game, thus freeing up significant amounts of
address space, up to several hundred Megabytes. See PR #2663 for
implementation details.
Note: This change does not affect 64-bit games since address space
is not a concern there. It also does not affect D3D10 or D3D11 since
resource uploads work differently in those APIs and are much more
memory efficient.
Render target feedback loops
On drivers which support VK_EXT_attachment_feedback_loop_layout,
reading from an active render target in D3D9 games is now properly
supported, which previously caused rendering artifacts on newer AMD
hardware and required driver-level workarounds. This affects a number
OBS-URL: https://build.opensuse.org/package/show/Emulators:Wine/dxvk?expand=0&rev=33
Marcus Meissner
46aa1c26ac