Assertion "!status && "vkSetLatencySleepModeNV"" on dual nvidia GPU #94
Comments
|
You can give this branch a try. For further debugging, the output of I assume in all cases where it is not working you get this exact assertion error, am I right? |
|
Ok thanks, I will try that branch. vulkaninfo: PRIMUS_VK_DISPLAYID=10de:1b80 PRIMUS_VK_RENDERID=10de:2204 pvkrun vulkaninfo: EDIT: I tried the branch and no luck.... In this case it appears as kind of silent crash. I get one of both, or the assertion or a silent crash. For example, in Hunt Showdown I get the following output (and it works if I run with the GTX 1080): |
|
Ok, the output of I've given a "blind" solution attempt another try where I hide the extension more thoroughly, so you can try the updated branch again. |
|
Still not working (silent crash). Need some output of any run or similar? I don't know if its of much of help to know this, but I managed to run the games with the 3090 as rendering and the 1080 as display, using docker (using the docker-steam-headless image). This kinds of verify that the problem is with primus-vk or the stack it uses. As before, I attach the output of trying to run "Hunt: Showdown 1896" (not sure if its different). |
If this is actually a segfault, some gdb backtrace of that would be helpful, so we can see which components/functions are involved and if this is still the game trying to use The reason I am trying to hide this extensions is, that all its functions require a I am not sure what the scenario is with docker-steam-headless. Do you just run the container (with its own X-Server on the dedicated GPU) and then use Steam in-Home streaming to see the output? If that's so, then everything in the container only sees vulkan objects of the target GPU, which allows I am also not sure, if the game/application in the stack, that decides to use Another road down, instead of hiding |
|
I'm currently away from home, so I will try debugging with Regarding the use of I have no specific information regarding I tested different proton versions, specifically GE, Experimental (with and without bleeding edge) and 9. Can you specify which version does not have VK_NV_low_latency2? |
I am not sure we need more games for now. If it actually comes from vkd3d-proton that might explain part of the behavior, but I don't know the inner workings of most games (engine, dx10/11/12/vulkan, ...) to draw any conclusions from that. Ideally we would make any game work, so having a single one with a backtrace on what it's doing is enough for now. I believe it was added here (HansKristian-Work/vkd3d-proton@0eb04f8), to expose dx12 low-latency support via |
Can not run many games on steam through proton using pvkrun on my dual GPU system. Or they just don't launch or it gives an assertion:
I have two graphics cards, GTX 1080 with the monitor attached to it and one RTX 3090. My system is Arch running KDE desktop. The command I use to use the GTX 1080 as display and the RTX 3090 as rendering is:
PRIMUS_VK_DISPLAYID=10de:1b80 PRIMUS_VK_RENDERID=10de:2204 pvkrun %command%Running the steam games without pvkrun (display and render on the GTX 1080) works fine. Also running other non steam apps with this command (ex. vkcubes) also work fine (doing the rendering on the RTX 3090 and displaying through GTX 1080).
I tried on X11 and Wayland. On Wayland not even vkcubes is working. Also tried with different version of proton (Experimental, GE, 9.0...)
Any recommendation on how to solve this issue?
The text was updated successfully, but these errors were encountered: