protonscr

DCS World Crash to Desktop

dxvkclosed d3d11wine bug
doitsujin/dxvk#5818 · opened 2026-07-30 by wrycu · updated 2026-07-30 · 8 comments · github
1 matching comments, n / p to jump
Wwrycu 2026-07-30 github

DCS Standalone (not steam) Crash To Desktop. This was just while flying in a pre-made mission included with the game. It contains nothing special and I was not doing anything noteworthy when the crash occurred.

Software information

DCS World. Settings mostly on Ultra graphics.

System information

  • GPU: NVIDIA RTX 5090
  • Driver: 610.43.03
  • Wine version: 11.0-2
  • DXVK version: Not sure; whatever Proton 11.0-2 provides.

Log files

dcs.log

Please let me know if you need/want additional information. I can try to reproduce if the apitrace magic is more helpful than the stacktrace provided in the DCS log.

Ninja edit: ty for the work you do <3

BBlisto91 2026-07-30 github

If you can reproduce again then a Wine/Proton log would be appreciated.

Edit:
Start of relevant section in game log

2026-07-25 08:19:45.273 INFO    EDCORE (808): DCS/2.9.28.26283 (x86_64; MT; Windows NT 10.0.19045)
2026-07-25 08:19:45.273 INFO    EDCORE (808): C:\windows\system32\d3d11.dll
2026-07-25 08:19:45.273 INFO    EDCORE (808): # C0000005 ACCESS_VIOLATION at 00006fffd8c3b092 00:00000000
Wwrycu 2026-07-30 github

attached. it expands to be quite large (~450MB); I can shrink debug flags if desired.

steam-default.log.gz

Ddoitsujin maintainer 2026-07-30 github

Does experimental work? The dxvk used in proton-11 is quite old.

Also there's a million d3dcompiler warnings, probably worth checking if native d3dcompiler works. No idea if it wants _43 or _47 or some other version of that library though.

Ddoitsujin maintainer 2026-07-30 github

FWIW Proton's dxvk builds don't have debug symbols, which makes figuring out where the crash happens kind of hard just from the stack trace, but it seems to be inside some sort of SetShaderResources call, which kind of implies use-after-free bugs in the game. Apitrace might actually be helpful here.

Wwrycu 2026-07-30 github
  1. you're right: it was running 2.7.1-498. I tested on experimental (which comes with 3.0.2-5) and confirmed the crash still occurs
  2. I installed native d3dcompiler_47 and both the crash and a graphical glitch I was trying to figure out where to file an issue for appear to be resolved - I can't reproduce either anymore

I'll work on getting apitrace functional for a more detailed log.

BBlisto91 2026-07-30 github

If the issues were solved with native d3dcompiler then you should report it at the Wine (or Proton) tracker. It is one of the libraries they ship.

Wwrycu 2026-07-30 github

Understood, thanks and sorry for wasting your time!

Ddoitsujin maintainer 2026-07-30 github

It's probably still useful to try and capture a trace with the broken d3dcompiler (just setting it to builtin should work), might still help narrow down the problem.

Also I'll take this kind of problem over all the recent low-effort LLM spam any day of the week

Proton versions

DLLs