Can you attach dxvk logs from a time it misbehaves? They should appear next to the exe
As a extra note. The nvapi config is dxgi and so for the most part wont affect d3d9 games (uncommon that d3d9 games query dxgi as it is a dx10+ thing)
Would need a log from DXVK, but it's not uncommon that it just doesn't work at all on AMD drivers because it likes to fail on swapchain creation with VK_ERROR_UNKNOWN (-13).
This isn't supposed to ever happen, but that issue isn't really debuggable either.
Can you attach dxvk logs from a time it misbehaves? They should appear next to the exe
As a extra note. The nvapi config is dxgi and so for the most part wont affect d3d9 games (uncommon that d3d9 games query dxgi as it is a dx10+ thing)
Here I found my logs, see if anything is useful: logs on Gitlab
However it has to be clear that, these logs might only be spawned when I started the games with dxvk2.6 by using 1660super automatically atm. I'm not sure about it.
If you need more information about when it generates what logs, I can do some further tests later.
Would need a log from DXVK, but it's not uncommon that it just doesn't work at all on AMD drivers because it likes to fail on swapchain creation with (-13).
VK_ERROR_UNKNOWNThis isn't supposed to ever happen, but that issue isn't really debuggable either.
Here I found my logs, see if anything is useful: logs on Gitlab
However it has to be clear that, these logs might only be spawned when I started the games with dxvk2.6 by using 1660super automatically atm. I'm not sure about it.
If you need more information about when it generates what logs, I can do some further tests later.
Nothing sticks out in that log at least.
Which GPU is driving the display?
Nothing sticks out in that log at least. Which GPU is driving the display?
7900xtx is driving my primary monitor, which is also where the game displays.
1660super is driving my secondary monitor.
Would need a log from DXVK, but it's not uncommon that it just doesn't work at all on AMD drivers because it likes to fail on swapchain creation with
VK_ERROR_UNKNOWN(-13).This isn't supposed to ever happen, but that issue isn't really debuggable either.
Hi, I've recently solved this issue, by freshly re-installed the windows(formmating the disk partition and then install a fresh new one from official Microsoft).
We found some new cases these days, according to how I solved and what we found, that is, this issue is very likely to only happen to those who switched their main GPU from NV's to others'. So I assume that NV's driver or its software app will leave some "leftovers" even if you delete it by using DDU. (for myself, I have both NV and AMD GPU, but this time I didn't installed NV's driver and its software app on my own initiative<windows auto install driver, with nv control panel only, no nv app or nv experience>)
If u are not going to investigate further, you can just close this issue. cuz the answer is here: freshly re-installing a new Windows.
I just switched my graphics card from RTX 4060ti to RX 7900xtx. Then I found that the game I played with dxvk could no longer run with dxvk(d3d9.dll), more precisely, the game instantly crashes when starting.(It was fine when I was using 4060ti).
I use DXVK because it helps these 32-bit old games like PAYDAY2 and Left4Dead2 to decrease crashes of "out of memory".
This issue happens on both PAYDAY2 and L4D2, but they are quite different, read my following statements for more details.
I tried dxvk version 2.6、2.5.3、1.9.2、1.5.4(the version when nvapi compatibility was not default I guess?), they all have the same issue.
What might be interesting is that I also tried starting the game with dual GPUs(RX 7900xtx for primary, GTX1660super for secondary), the game PAYDAY2 finally ran successfully but no matter how I set, the game only ran by using 1660super. However, for L4D2, it still performs the same crashing at loading screen when starting.
I also tried starting the game by powershell, every time the game starts, it shows "NVIDIA driver settings found"(when 1660s exists) or "NVAPI error"(when there's no nv gpu), even if I disable dxvk's nvapi compatibility by following the instructions offered by ChatGPT (not sure if it works tho：$env:DXVK_NVAPI="0", dxgi.nvapiHack = 1, dxgi.nvapi = false and dxgi.nvapiOpt = false).
I also have a friend who were experiencing the same issue as mine, he also played these games with dxvk before and recently switched his graphics card from NV's 3060ti to AMD's 9070xt as well. Unfortunately I don't know a person that always use AMD graphics card, so I can not be sure if it's because we changed our graphics cards from nv to amd or it's just an issue happens on amd.
Software information
PAYDAY2（Program name - payday2_win32_release.exe）and L4D2
System information
Apitrace file(s)
Unfortunately, the file has almost nothing inside (under 2 bytes, with only an "at" in it when I opened it), could be because the game simply crashed when starting by dxvk and didn't even show up a window.
Log files
On windows platform, so there's no Proton and Wine, only a vulkaninfo.txt
Edit 1 - Additional Information of L4D2
I just did some more tests on L4D2, somehow it didn't crash now (sadly it still crashes for PAYDAY2).
When I was using APItrace, L4D2 can correctly recognize my primary gaming card which is 7900xtx,
but when I was using the newest DXVK 2.6, L4D2 could only run by using GTX1660super, which is the same as PAYDAY2's current issue.
APItrace for L4D2：OneDrive