protonscr
4 results, 5 hits for DXVK_LOG_LEVEL=debug

Fallout: New Vegas fails on Proton 11 and 10, with DXVK D3D9 unless d3d9.hideNvidiaGpu = False is set dxvkclosedd3d9

#5637 · 18 comments · updated 2026-06-02 · 1 matching
comment by AlexeySFdot · 2026-05-18 · view · github
`Running commands DXVK_LOG_LEVEL=debug DXVK_LOG_PATH=$HOME/ PROTON_LOG=1 %command%` [steam-22490.log](https://github.com/user-attachments/files ...

Priston Tale crashes on launch dxvkclosedd3d9windows

#2633 · 3 comments · updated 2026-06-16 · 1 matching
issue by dumpsters · 2022-04-27 · view · github
... default settings API Trace made on windows ``` @set DXVK_LOG_LEVEL=debug @set VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validation @Game.exe ``` ### System information - GPU ...

[DXVK 1.5] Battle.net app not launching, works on 1.4.6 dxvkclosedd3d9can't reproduce

#1282 · 35 comments · updated 2022-11-29 · 2 matching
comment by SveSop · 2020-03-02 · view · github
@AlexandarY Logging the Battle.net app with `DXVK_LOG_LEVEL=debug` you need to look for the logs in the ...
comment by AlexandarY · 2020-03-03 · view · github
@SveSop thanks for the info! I ran Battle.net with` DXVK_LOG_LEVEL=debug` and got back this: > info: Game ...

Observed a deterministic memory access violation (0x...200) during VRAM chunk deallocation on TF2 x64 using DXVK-Master 545 dxvkclosedd3d9windows

#5589 · 17 comments · updated 2026-04-21 · 1 matching
comment by harry24681012-blip · 2026-04-19 · view · github
... I'll enable DXVK_LOG_LEVEL=debug to capture the final Vulkan commands leading up to the 0x...200 error ...