Unigine Valley: Crash after load about dxvk HOT 8 CLOSED

Same issue as #8.

from dxvk.

@doitsujin :

I tried both heaven and valley again with the current git which includes: a567f6a.
But both still crash, so i guess that one is not a duplicate of Issue #8 .

New logs attached:

Valley_dxgi.log
Valley_d3d11.log
backtrace-20180204.txt

Many thx,
Christian

from dxvk.

Thing with these driver issues on Nvidia is that everything about them is guesswork. And that's the issue here, it's not Unigine Valley that crashes, it's the Nvidia driver that crashes. And it crashes for a lot of random things.

The logs are completely useless because they don't contain any crash info. The backtrace is completely useless because Nvidia's closed source driver doesn't export any symbols. Dumping the shaders which cause the crash is next to useless because pretty much anything in there could cause the issue. Ultimately there is nothing I can do about it except randomly stuble upon a solution.

I won't reopen this particular issue because the title is misleading, but feel free to open a new meta issue for Nvidia driver crashes in general. I don't want 500 different issues covering the exact same problem.

from dxvk.

Vulkan being what it is, I suspect that these are, the vast majority of the time, uncaught undefined behavior bugs running afoul of a driver that's internally fundamentally different. NV has their own GPU debugger that could go a long way towards figuring this stuff out. However, without a GeForce in the hands of someone that knows what they're doing, that doesn't help much.

from dxvk.

@roothorick By "NV has their own GPU debugger" you mean NVIDIA NSight, right?

I'm no GPU expert, but I've got an NVIDIA GPU on a Windows VM. I'll try running Visual Studio and NVIDIA NSight and see if I can provide some more useful logs.

from dxvk.

@doitsujin , ok, thant sounds bad. Will open a meta bug with apps/games which crash the nvidia driver. As you mentioned you have no way to debug it, i am wondering how others are doing that (like feral who also translate dx11->vulkan, or ID which hvae natve vulkan titles) etc..

I Hope @GabrielMajeri is right, and he can debug that issue with nsight, whatever that is :) .

from dxvk.

I managed to get it to work with the example.

It didn't work so well with Unigine Valley though.

from dxvk.

Well....

1. I was thinking of the Linux Graphics Debugger, not knowing at the time it doesn't yet have Vulkan support.

2. The Nsight overlay in the example window is a big red flag. Nsight doesn't have a HUD for Vulkan mode, so apparently Nsight itself is running under DXVK. That's.... not terribly useful. You need to find a way to have DXVK inside Nsight, not the other way around.

from dxvk.