Joshua-Ashton / d9vk

A Direct3D9 to Vulkan layer using the DXVK backend. [Upstreamed to DXVK]
https://github.com/doitsujin/dxvk
zlib License
832 stars 42 forks source link

Grim Dawn can't get past menu #308

Closed ghost closed 3 years ago

ghost commented 5 years ago

Grim Dawn menu renders incorrectly, unable to move mouse from center screen, seems to be being grabbed. When using D3D9, the game only launches and gets to the menu specifically with x64 D9VK. x86 D9VK and x86/x64 WineD3D get stuck on a black screen when launching and generate 1kb traces.

D3D9 screenshot: https://github.com/casualRR/d9vk-trace/raw/master/d3d9.jpg
D3D11 screenshot: https://github.com/casualRR/d9vk-trace/raw/master/d3dx.jpg

Software information

Grim Dawn, running with Steam launch options: PROTON_USE_D9VK=1 D9VK_HUD=1 %command% /d3d9 /x64

System information

Apitrace file(s)

WineD3D9 black screen launch generated a 1Kb useless trace, so here's a D9VK one in lieu of nothing: https://github.com/casualRR/d9vk-trace/raw/master/gd_trace.7z

Log files

steam-219990.log

LeJimster commented 5 years ago

Experiencing the same issue when I launch in d3d9 mode, it seems like you can move the mouse freely for a second when the game is loading into the menus and then its locked in place, if you try to move the mouse you see it flickering around where it's locked. DXVK works perfectly with dx11 on this game.

@casualRR fyi it's DXVK_HUD for the stats ;-)

If needed I can always boot into windows and try creating a trace from there. Let me know.

Update: Just noticed I misread your bug report.. I don't experience incorrect rendering in dx9 mode, but I notice you have the latest expansion, which I haven't bought yet.

System information

Log files

grimdawn-32bit-steam-219990.log grimdawn-64bit-steam-219990.log Grim Dawn_d3d9.log Grim Dawn_d3d11.log Grim Dawn_dxgi.log

ghost commented 5 years ago

@LeJimster I just uninstalled Forgotten Gods to see if it made a difference - no dice, same problem.
I also tried running at more normal resolution (was at 1080x720, catering to my 3:2 aspected laptop). The issue persisted at 1280x720. I might try the dev branch of Mesa too.
**Edit: using dev branch of Mesa and related libs - same issue ***Second edit: got a Steam/Proton log file that has some debug data in it, attached to first post

LeJimster commented 5 years ago

I just tried Proton 4.11-3 with Grim Dawn and the mouse works fine now, I don't notice any other bugs like you are experiencing, seems like they're Intel specific?

NerosTie commented 3 years ago

Tested with DXVK 1352 + Proton 5.0-9. Everything is ok.

@Joshua-Ashton I think you can safely close this issue. (the apitrace is not even available anymore)