protonscr

Crimzon Clover World EXplosion

appid 1718160 1 threads, 1 open 5 comments last activity 2023-08-02
Latest maintainer comment · alasky17 · 2023-07-31 · #5391
@AwesamLinux I played around with this a bit, and I got very inconsistent crashing on experimental (and no crashing on 8.0-3) which smells like a race condition that may have been introduced in the 8.0-x branch or maybe you are just suddenly getting unlucky. Could you try disabling the steam overlay for the game and seeing if that fixes the crash consistently?
Threads

Crimzon Clover World EXplosion proton open

#5391 · 5 comments · opened 2021-12-08 · last comment 2023-08-02 by AwesamLinux
Recent activity
  • AwesamLinux · 2023-08-02 · Crimzon Clover World EXplosion
    @alasky17 I have now tested disabling the Steam overlay, and with the overlay disabled game does not crash on launch and not during gameplay either (for as long as I have played anyway). With the Steam overlay disabled I...
  • alasky17maintainer · 2023-07-31 · Crimzon Clover World EXplosion
    @AwesamLinux I played around with this a bit, and I got very inconsistent crashing on experimental (and no crashing on 8.0-3) which smells like a race condition that may have been introduced in the 8.0-x branch or maybe ...
  • AwesamLinux · 2023-07-28 · Crimzon Clover World EXplosion
    ## System Information - GPU: AMD RX 5700 - Driver/LLVM version: Mesa 23.1.3 - Kernel version: 6.4.4-200.fc38.x86_64 - Proton version: proton-8.0-3c ## Symptoms Game crashes on launch (window opens with the loading screen...
  • NRG-R9T · 2021-12-11 · Crimzon Clover World EXplosion
    ## System Information - GPU: RX6700 XT - Driver/LLVM version: Mesa 21.2.5/13.0.0 - Kernel version: 5.15.7 - Link to full system information report as: [Gist of full system information report](https://gist.github.com/NRG-...
  • FrozenFish24 · 2021-12-10 · Crimzon Clover World EXplosion
    False alarm. Turns out I was encountering the issue discussed here: https://bugs.winehq.org/show_bug.cgi?id=50893 Simply `touch`ing my home directory as suggested fixed the problem.

Proton versions over time

Launch lines, newest first

PROTON_USE_WINED3D=1 %command%