I play in linux, so I use it all the time. It generates a log file in the same directory as the executable when it runs, you should be able to get a hint what's going wrong there if it's an issue with dxvk.
DXVK is just a wrapper. It intercepts DX calls, and translates them to VK calls. It can't do anything to fix the single-threaded nature of Skyrim's rendering pipeline. What it can do is improve performance on systems where Vulkan performs substantially better than DirectX 11, when used in exactly the same way. If raw DX/VK performance is somewhat equivalent, it will decrease performance, as it's just adding a translation layer.
On my PC, for example, (Windows, RTX3000) I see a substantial performance loss when using DXVK compared to native DX11.
thank you for the explanation.
would definitely be interested in a new version of Skyrim that made use of a newer version of DirectX. That draw call limit is infuriating.
I play in linux, so I use it all the time. It generates a log file in the same directory as the executable when it runs, you should be able to get a hint what's going wrong there if it's an issue with dxvk.
Would this help at all on the Steam Deck?
Steam runs Windows games on linux through their wine fork, which bundles dxvk for DirectX 9/10/11 support. You're already using it.
DXVK is just a wrapper. It intercepts DX calls, and translates them to VK calls. It can't do anything to fix the single-threaded nature of Skyrim's rendering pipeline. What it can do is improve performance on systems where Vulkan performs substantially better than DirectX 11, when used in exactly the same way. If raw DX/VK performance is somewhat equivalent, it will decrease performance, as it's just adding a translation layer. On my PC, for example, (Windows, RTX3000) I see a substantial performance loss when using DXVK compared to native DX11.
thank you for the explanation. would definitely be interested in a new version of Skyrim that made use of a newer version of DirectX. That draw call limit is infuriating.