dxvk: Assassins Creed Black Flag crashes with DXVK
When playing Assassins Creed IV using DXVK it crashes as soon as I get to the first future storyline scene (Directly after maneuvering the merchant’s ship out of the bay at the beginning). The thing is that my whole system becomes unresponsive and I can’t even change to a different tty. So I had to reset my PC and I wasn’t able to retrieve any debug messages from wine. After trying a few times I was able kill AC and my X Server via ssh. But my log still stops way before the crash happens and doesn’t contain any error messages.
Anyway I tried without dxvk and the game works wothout any problems. Although using wined3d it’s pretty unplayable at ~5-10 fps. Whereas DXVK was easily able run with 60 FPS (capped at my monitor’s refresh rate). Which proves to me that the crash is at least DXVK related.
Software information
Assassins Creed IV: Black Flag
System information
- GPU: GTX 1070 8192 MB
- Driver: 415.22.05 (Vulkan Beta Branch)
- Wine version: 4.0 with esync
- DXVK version: 0.93 and 0.96 (tested with both)
Apitrace file(s)
Unfortunately the game crashes about a second after going to fullscreen when started with apitrace (If I understood it correctly apitrace shouldn’t be executed with DXVK?):
$ &> apitrace.txt WINEPREFIX=~/Games/uplay/ LD_LIBRARY_PATH="/home/user/.local/share/lutris/runners/wine/tkg-4.0-x86_64/lib:/home/user/.local/share/lutris/runners/wine/tkg-4.0-x86_64/lib64:/lib:/lib64:/usr/lib:/usr/lib64:/usr/lib32:/usr/lib64:/home/user/.local/share/lutris/runtime/Ubuntu-18.04-i686:/home/user/.local/share/lutris/runtime/Ubuntu-18.04-x86_64:$LD_LIBRARY_PATH" WINEESYNC=1 WINEDLLOVERRIDES="xaudio2_7=n,b;nvapi,nvapi64=" DXVK_HUD=0 DRI_PRIME=0 ~/.local/share/lutris/runners/wine/tkg-4.0-x86_64/bin/wine ~/Dokumente/apitrace-msvc/x86/bin/apitrace.exe trace -a dxgi ~/"Games/uplay/drive_c/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/games/Assassin's Creed IV Black Flag/AC4BFSP.exe"
However AC runs fine when started by the exact same command (just without apitrace):
$ WINEPREFIX=~/Games/uplay/ LD_LIBRARY_PATH="/home/cedric/.local/share/lutris/runners/wine/tkg-4.0-x86_64/lib:/home/user/.local/share/lutris/runners/wine/tkg-4.0-x86_64/lib64:/lib:/lib64:/usr/lib:/usr/lib64:/usr/lib32:/usr/lib64:/home/user/.local/share/lutris/runtime/Ubuntu-18.04-i686:/home/user/.local/share/lutris/runtime/Ubuntu-18.04-x86_64:$LD_LIBRARY_PATH" WINEESYNC=1 WINEDLLOVERRIDES="xaudio2_7=n,b;nvapi,nvapi64=" DXVK_HUD=0 DRI_PRIME=0 ~/.local/share/lutris/runners/wine/tkg-4.0-x86_64/bin/wine ~/"Games/uplay/drive_c/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/games/Assassin's Creed IV Black Flag/AC4BFSP.exe"
Anyway here is the output of the apitrace crash: https://own.arrakiz.org/index.php/s/yJYdNy7zeqnzPnm (Just click download. The file is somehow too big for any kind of preview.)
Log files
- d3d11.log: https://own.arrakiz.org/index.php/s/kCHQgA69ZyjLKyd
- dxgi.log: https://own.arrakiz.org/index.php/s/5HtR5REAr7dS3J3
I’m sorry that I couldn’t provide more debugging info. I know that a trace would be vital for a diagnosis. But at this point I’m not sure what else to do. If you give me instructions I’m more than willing to give you more info though.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 32 (4 by maintainers)
The game is running fine when setting the Fauturelevel to dx10.1. I was using a DXVK config-file and set d3d11.maxFeatureLevel = 10_1 after it I could play through those scenes mentioned
The game doesn’t really crash, it hangs your GPU.
I’m aware of this problem, but since it freezes the entire system it’s extremely tedious to debug, and I haven’t been able to make any progress when I tried. You could try using wined3d to get past that, I’ve given up on this issue a long time ago.
Can confirm, settings d3d11.maxFeatureLevel = 10_1 does it for me as well.
No. The thing is that I can’t use any debugging tools like Renderdoc with a hung GPU, and this game is particularly annoying since getting a hang report that would at least show the offending shaders is next to impossible. So while it is possible to access the system via SSH, I cannot gain any information at all that would help debug this issue.