protonscr

Warhammer: Chaosbane

appid 774241 1 threads, 1 open 9 comments last activity 2022-11-08
ProtonDB Steam Search within game
Latest maintainer comment · kisak-valve · 2022-03-02 · #5632
Hello @SeraphisCain, it should be noted that `PROTON_USE_WINED3D` is not considered a supported runtime option. It would be more interesting to focus on what's happening with the game and DXVK on the default render path. The symptoms you've described sounds like the game has run out of vram and the video driver has pushed part of the render hot path to system ram. Can you keep an eye on vram usage...
Threads

Warhammer: Chaosbane proton open 3 matching

#5632 · 9 comments · opened 2022-03-02 · last comment 2022-11-07 by hakzsam
comment by hakzsam · 2022-03-11 · view · github
... In the mean time, you can workaround it with `RADV_DEBUG=nocompute %command%` or `RADV_DEBUG=nongg %command%`. Let me ...
comment by nhkcon · 2022-03-11 · view · github
... In the mean time, you can workaround it with `RADV_DEBUG=nocompute %command%` or `RADV_DEBUG=nongg %command%`. Let me ...
Recent activity
  • hakzsam · 2022-11-07 · Warhammer: Chaosbane
    This issue should be fixed properly in Mesa main now https://gitlab.freedesktop.org/mesa/mesa/-/commit/26c8fedc1bb12fa8f3d6c646308f4b46756d77c7
  • nhkcon · 2022-03-11 · Warhammer: Chaosbane
    nongg also works to get the game running on the deck. Thanks for the quick workaround.
  • hakzsam · 2022-03-11 · Warhammer: Chaosbane
    Yes, the problem on your desktop is different, the driver failed to allocate a texture which makes sense somehow given the large resolution you used. Would be interesting to confirm that RADV_DEBUG=nongg on the Deck also...
  • nhkcon · 2022-03-11 · Warhammer: Chaosbane
    > This seems a pretty complex problem to solve actually. In the mean time, you can workaround it with `RADV_DEBUG=nocompute %command%` or `RADV_DEBUG=nongg %command%`. Let me know if it works with that, thanks! On the de...
  • hakzsam · 2022-03-11 · Warhammer: Chaosbane
    This seems a pretty complex problem to solve actually. In the mean time, you can workaround it with `RADV_DEBUG=nocompute %command%` or `RADV_DEBUG=nongg %command%`. Let me know if it works with that, thanks!
  • hakzsam · 2022-03-11 · Warhammer: Chaosbane
    @nhkcon Thanks for the great report, I can reproduce, I will investigate.
  • nhkcon · 2022-03-11 · Warhammer: Chaosbane
    ## System Information - GPU: AMD AMD Radeon RX 580 Series (POLARIS10, DRM 3.42.0, 5.14.21-210.current, LLVM 13.0.0) - Driver/LLVM version: 4.6 (Compatibility Profile) Mesa 21.3.6 - Kernel version: 5.14.21-210.current - L...
  • SeraphisCain · 2022-03-02 · Warhammer: Chaosbane
    @kisak-valve Looks like you're spot on, here. Here's the GPU usage on 7.0-1. VRAM is full, GPU utilization 100%, PCIe bandwidth utilization at 73%: ![image](https://user-images.githubusercontent.com/67637185/156447602-16...

Proton versions over time

Launch lines, newest first

RADV_DEBUG=nocompute %command%
RADV_DEBUG=nongg %command%

Launch options