ValveSoftware
The Riftbreaker (780310)
Compatibility Report
- Name of the game with compatibility issues: The Riftbreaker
- Steam AppID of the game: 780310
System Information
- GPU: NVIDIA GeForce RTX 3080 Ti
- Driver/LLVM version: 4.6.0 NVIDIA 510.54
- Kernel version: 5.17.0-2-MANJARO
- Link to full system information report as Gist:
- Proton version: 7.0.1
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
Logs CTD during gameplay: steam-780310.tar.xz.txt - please rename to *.tar.xz. Logs CTD starting configuration utility: steam-780310-ctd-configuration utility.log
Relevant log fragment for CTD during gameplay
0190:fixme:vk_topology_from_d3d12_topology: Unhandled primitive topology 0xb.
01a0:fixme:vk_topology_from_d3d12_topology: Unhandled primitive topology 0xb.
4011.935:0140:01d4:err:fsync:get_shm Failed to map page 63561 (offset 0xf849000).
4011.935:0140:01d4:trace:seh:handle_syscall_fault code=c0000005 flags=0 addr=0x7fe73cd5d02e ip=7fe73cd5d02e tid=01d4
4011.935:0140:019c:trace:seh:handle_syscall_fault code=c0000005 flags=0 addr=0x7fe73cd5bf42 ip=7fe73cd5bf42 tid=019c
4011.935:0140:01d4:trace:seh:handle_syscall_fault info[0]=0000000000000001
4011.935:0140:019c:trace:seh:handle_syscall_fault info[0]=0000000000000001
4011.935:0140:01d4:trace:seh:handle_syscall_fault info[1]=0000000000000007
4011.935:0140:019c:trace:seh:handle_syscall_fault info[1]=0000000000000007
4011.935:0140:01d4:trace:seh:handle_syscall_fault rax=00007fe60663df90 rbx=0000000000000000 rcx=0000000000000006 rdx=0000000000000002
4011.935:0140:019c:trace:seh:handle_syscall_fault rax=0000000000000001 rbx=0000000000000001 rcx=0000000000000007 rdx=0000000000000000
4011.935:0140:01d4:trace:seh:handle_syscall_fault rsi=0000000000000007 rdi=0000000000019fe8 rbp=0000000000000001 rsp=000000001dc2e3e0
4011.935:0140:019c:trace:seh:handle_syscall_fault rsi=00000000154edae0 rdi=0000000000000000 rbp=0000000000000000 rsp=00000000154eda80
4011.935:0140:01d4:trace:seh:handle_syscall_fault r8=000000016af382b8 r9=0000000000651d00 r10=00007fe73cdce660 r11=000000001dbcf3e0
4011.935:0140:019c:trace:seh:handle_syscall_fault r8=0000000000000002 r9=00000000154edce0 r10=0000000000000000 r11=0000000067ee0000
4011.935:0140:01d4:trace:seh:handle_syscall_fault r12=0000000000000000 r13=0000000000000000 r14=0000000000000003 r15=000000000114e9e0
4011.935:0140:019c:trace:seh:handle_syscall_fault r12=0000000000000000 r13=00007fe73cdaf810 r14=0000000000000001 r15=00000000154edae0
4011.935:0140:01d4:trace:seh:handle_syscall_fault returning to user mode ip=000000017000dcf4 ret=c0000005
4011.935:0140:019c:trace:seh:handle_syscall_fault returning to user mode ip=000000017000e1b4 ret=c0000005
CTD when starting configuration utility
2893.680:0060:006c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\drivers\\winehid.sys" at 00000003BA2A0000: builtin
2893.809:0060:006c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\imm32.dll" at 00000003AFD00000: builtin
2893.811:0060:006c:trace:seh:dispatch_exception code=6ba flags=0 addr=000000007B0124BE ip=000000007B0124BE tid=006c
2893.811:0060:006c:warn:seh:dispatch_exception unknown exception (code=6ba) raised
2893.811:0060:006c:trace:seh:dispatch_exception rax=000000007b012470 rbx=000000000106da38 rcx=000000000106d750 rdx=0000000000000000
2893.811:0060:006c:trace:seh:dispatch_exception rsi=00000000000000c8 rdi=0000000001750230 rbp=00000001c8e19ce0 rsp=000000000106d730
2893.811:0060:006c:trace:seh:dispatch_exception r8=0000000000000000 r9=0000000000000000 r10=00000000011f0020 r11=a55a5aa5a55a5aa5
2893.811:0060:006c:trace:seh:dispatch_exception r12=000000000106da38 r13=0000000001210210 r14=0000000000000000 r15=0000000001210210
2893.811:0060:006c:trace:seh:call_vectored_handlers calling handler at 00000002279AD660 code=6ba flags=0
2893.811:0060:006c:trace:seh:call_vectored_handlers handler at 00000002279AD660 returned 0
2893.811:0060:006c:trace:unwind:RtlVirtualUnwind type 1 rip 000000007B0124BE rsp 000000000106D730
Symptoms
Intermittently the game crashes to desktop. I attached the logs of the last event. I'm not doing anything special at this moment.
Another problem is that the configuration tool cannot be started. It reports a critical error with stack trace on startup.
Reproduction
CTD during gampleay: Play the game. It will happen eventually. It is not possible to play 1+ hour without a CTD.
CTD configuration utlity: Start the game and choose Configuration utility. The crash immediately happens.
@Diman0 Does it also crash during gameplay if you launch with PROTON_NO_FSYNC=1 %command% ?
@Blisto91
Before I tried with PROTON_LOG=1 PROTON_NO_ESYNC=1 %command%
I've tried with this command PROTON_LOG=1 PROTON_NO_FSYNC=1 %command%
- Configuration utility. Again a crash on startup with a stack trace.
- The game: CTD when reaching main menu steam-780310-ctd-main-menu.log
- The game 2nd try: CTD when reaching main menu steam-780310-ctd-main-menu-2nd-try.log
I've tried again with PROTON_LOG=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
- The game 3rd try: CTD when reaching main menu steam-780310-CTD-main-menu-3rd-try.log
- The game 4th try: I've played for 1.5 hours without any crash.
PROTON_LOG=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command% might be the magic combo.
Some remarks:
- Sometimes when you start the game, graphics is messed up. Everything looks funky. This happens very rarely. Can be resolved by closing the game and closing steam. After that the next game should look normal. No graphic distortion.
- Sometimes the game will CTD when reaching the menu. So far each time when this happens, the game does not crash when I start the game for the 4th time (after 3 crashes). Don't ask me why. I know it does not make sense, but this is what I have observed so far.
I've played for 3 hours now without any crash. It appears proton 7.0-1 with PROTON_LOG=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command% is quite stable.
I am having a couple of issues with this game. I bought the game based on the good experience with the prologue/demo. Issues
- The launch configuration button directly starts the game instead of the configuration screen (works in the demo/prologue)
- Very low performance in dark environments
- There were some issues that some particle effects were missing, but after messing around with proton versions it somehow works now
The worst part is the performance drops. The GPU benchmark showcases this problem very well. I have around 10 fps when starting it from the normal game and around 100 fps when starting from the prologue/demo. The prologue/demo also had this issue but it disappeared after some troubleshooting.
Things I tried to fix the performance:
- Using different proton versions (most don't start the game)
- Changing the game setting from dx12 to dx11
- Using proton GE
- Lowering graphics settings
- Disabling ESYNC and FSYNC
I launched both the main game and the prologue/demo the same benchmark and just quit as soon as I loaded and saw the performance. Prologue (working): proton logs: steam-proton-log-riftbreaker-prologue.log game logs: game_logs_prologue.txt Main game: proton logs: steam-proton-log-riftbreaker.log game logs: game_logs_main.txt
Steam system information: https://gist.github.com/thunder1410/76897c9bd211c74b30968baa4037ce96
Using the PROTON_USE_WINED3D=1 launch option fixes the issue with a significant performance hit.
Getting memory leak on this game after a , I am using proton Experiment and it was almost using all of my 16gbs of ram and causing stability issues.
Anyone else noticing this or getting the same issues?
The game was running fine until the last update... Now I can start the game, but once I should arrive on the game menu it crash and come back to steam.
Any idea on how and where can I get/find some logs to try to understand what is happening ?
I have try with the last proton, experimental, eggrol, different start option... It crash all the time...
Proton 9 is unstable for me. Proton 8 is rock stable. Consider using Proton-GE 8-32. With this proton version it will run without any issues. I use the start options: PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%
Hello @Diman0,what exactly is the game doing to give an unstable feeling?
Please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
Well, the game crashes when using the latest proton-ge based on proton 9. I will give proton 9 a try again and will check if i can produce a log.
Figures, with proton 9.0-2 I don't have any crashes. I do not have access anymore to the savegame that crashed upon loading the game. This could be relevant. Last time I used the latest proton-GE 9-* which crashed to desktop. Possibly this is relevant. Although proton-GE should be better since it uses more up to date libraries (wine, dvk3d etc). One other variable is that I switched from X11 to Wayland today. I have no clue if this is relevant.
So with proton 9.0-2 it appears to work fine now (with Wayland).