PlayableShow Details
Unknown
gamemoderun VKD3D_ENABLE_DEBUG=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
同台機器與安裝Windows10時比起來 大概只能開一半效能
Linux 存檔後 若用 Windows 執行遊戲 即使無開啟LINUX的存檔 下次Linux開啟時 存檔會毀損
同台機器與安裝Windows10時比起來 大概只能開一半效能
若無設定VKD3D_ENABLE_DEBUG=1則遊戲持續報錯與重啟 只能設定VKD3D_ENABLE_DEBUG=1或是修改檔案使用DX11模式執行遊戲
The game would be playable, but it is absolutely not optimized for the deck. Unfortunately, this great game is no fun on the deck.
I tried the suggestions from the other reports.
unfortunately runs very slowly at 30fps
Edited initial_config_win_safe.cfg to say dx11 in order to prevent crash on teleport
Slowdown during Hearts of the Swamp DLC, possibly not unique to Proton
Played campaign from start to finish with no major issues except crashing on teleport which I fixed with the config edit to run the game in dx11
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
Encountered several crashing issues after recent release of DLC content, however a patch issued 10th July appears to have resolved this. If you are still experiencing issues after this patch run steams "Verify integrity" function which resolved the issue for me, I am assuming it was something stuck in the shader cache still.
No more rift crashing on exe 975 data 570 .
Works grate
When researching, rift jumping causes crashes. have to wait around 1 min or so after stopping the research to be able to jump whith out crashing
Have played though Heart of the Swamp dlc. Game crashes on local rift jumps and between biomes and seams to be caused by research. It seams to be safe to jump if wating 1 min or more after stoping research, though has been slightly more once. Does make defence harder but is mostly playable. vr exe 974 data 569
Teleporting across map crashed a lot with proton 9, works great with proton 8.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_LOG=1 %command%
As of update 2024-06-21 (Heart of the Swamp DLC) the game crashes everytime I teleport to a different location.
Game worked fine before HotS DLC
On the 936 build you *must* change the directx mode to play for more than 10 or so minutes.
Switching to DX11 stopped the random crashing after warping for me: Modify file: Riftbreaker/conf/initial_config_win.cfg Define: render_system to dx11
May crash after warping in game if you don't change to DX11
Not working since Heart of the Swamp DLC Savegame loads but Rift jumping to ANY outpost crashes game New campaign crashes game
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
Was working before update 20240621 No mods. Tried with Proton 8.0-5, 9.0-2 and experimental.
Not working since Heart of the Swamp DLC Savegame loads and playing works on that map but Rift jumping to ANY outpost crashes game New campaign crashes game No way to progress game
I always use experimental, didn't even try standard Proton.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
Modify file: Riftbreaker/conf/initial_config_win.cfg
Define: render_system to dx11
gamemoderun %command%
Works pretty much out of the box. Loading times are a bit high even when loading from an SSD but all in all a solid experience.
Mix of options
Tried both DX12 and DX11
Frame rate drops immediately after building the 2nd or 3rd building. CPU benchmark runs at 3 FPS on default settings. And about 6 FPS on minimal graphics settings.
I tried a variety of proton versions (regular, experimental, GE), launch options (no fsync, no esync, DX, NVAPI), and in game settings (DX11, DX12, vsync on/off, minimal graphics settings.) CPU benchmark always had horrible frame rates. Loading times are rough as well (average being about a minute).
(none - Lutris setup everything for me)
Just used lutris "install" - everything was done by Lutris
Use Lutris to install the game (it sets up everything for you). Used on Garuda gamer edition (that has setup wine, winetricks etc.) by default
GOG-Version at https://lutris.net/games/the-riftbreaker/
PROTON_NO_ESYNC=1 %command%
8.0-2 and 7.0-6 did not work. On 7.0-6, the game would slow down to a crawl at the title screen, and on 8.0-2 the game would generate random inputs on the steam overlay. This would include trying to uninstall random games and trying to enter a product key, but would never complete these steps as they opened a new window.
Will run very well sometimes, but most of the time performance is horrible on my 6800 XT.
It was uncommon but it happened.
Mouse input is not separate from how bad it can perform.
Occasionally the game will load and perform beautifully, but most of the time performance is a fraction of that. When it's doing well, I can max it out at 1440p and get 100+ fps, those other times it's 30 ish or worse.
Tried the common proton fsync or esync options and it made no difference for me so left them off for my general playing.
Tried running it out-of-box and with the command line suggested. Crashed on startup both times.
Tried with the command line argument PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 as recommended.
I thought I got it working last month but with very poor performance (compared to a lesser spec windows machine). I wasn't able to reproduce that today, though I didn't try much tinkering.
No issues
I completed the campaign without any trouble and thoroughly enjoyed the game. Used Proton 8.0-2.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
During dusk/dawn framerate drops to single digits. Great otherwise
It seems very specific to dusk/dawn lightning shifts. Hopefully they can get this fixed
gamemoderun PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
I needed to add the esync and fsync launch parameters, as well as switch to Proton7.0.6 in order for the game to work properly. Without all 3 of those things, the game would either have errors on startup, attempt to launch multiple times, lag and/or crash after a few minutes.
PROTON_NO_ESYNC=1 %command%
Changed value of render_system to "dx11" in steamapps/common/Riftbreaker/conf/initial_config_win.cfg
A few artifacts before applying tinkers
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1
Optional: Set "render_system" from "dx12" to "dx11" in steamapps/common/Riftbreaker/conf/initial_config_win.cfg to switch between render mode
DX12: Missing build overlay around ore deposits
Stuck in loading screen if launch options are not set
GPU Benchmark: 125 fps average on DX11, 225fps average on DX12
DXVK_ASYNC=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 gamemoderun %command%
render_system "dx12" to "dx11" in steamapps/common/Riftbreaker/conf/initial_config_win.cfg Configuration utility does not launch from Steam, the link has been broken for a while.
Since Metal Terror DLC came in, roughly 20% less FPS on DX12. However, DX11 performance remains as before.
2 crashes in 32 hours, very acceptable
PS controller is not detected immediately, have to wait for some seconds during which the cursor keeps moving on its own. Sometimes I have to move with the keyboard to get it un-stuck.
I have some experience with Exor games on Linux, played X-Morph for a while, mostly trying to make it not crash. Played Riftbreaker since launch and have used its benchmark quite extensively. The crashes are not zero but not as many as a year ago. Overall the situation for this engine on Linux has improved considerably.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
40Hz screen, 40FPS capped (in game and via gamescope) vsync off, all quality settings to low. 1280x720p resolution set in game menu
some text is small, will play with UI scaling to see if it improves
DXVK_ASYNC=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
Changed value of set render_system "dx12" to "dx11" in steamapps/common/Riftbreaker/conf/initial_config_win.cfg
Slight hiccups when large enemy waves spawn on a map with a large base.
Native install (click and play) would crash after ~1hr. Haven't had issues after running via latest Proton.
After adjusting launcher options, enabling Proton, and changing a config file the game ran well. Grabbed some modes from NexusMods (not the workshop mods) and the game still ran well. There may be some framerate drops during larger battles on a map with a lot of buildings but it isn't bad.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
(not sure if truly needed but increases battery life path will change if on SD) Edited: /home/deck/.steam/steam/steam apps/common/Rift breaker/conf/intial_config_win.cfg to switch the value for render system to dx11
Force dx11 in config files
Without the sync launch arguments you will experience random freezes that force you to quit the game
As I said Out of the box it refuses to run stable on the deck- odd as the demo ran fantastic out of the box, no tinkering
DXVK_ASYNC=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
Riftbreaker/conf/initial_config_win.cfg: change "set render_system" to "dx11"
Kwin didn't seem to disable composition in fullscreen. This could have impacts on latency and performance. If needed composition can be forced off with a keyboard shortcut (default: Alt+Shift+F12). But I didn't encounter any negative effects because of this.
Stuttering, use DXVK_ASYNC=1 to fix this.
The game is very unstable when set to dx12.
The built in configuration tool/launcher didn't work, instead just launching the game regularly. Because of this you have to change the rendering API in the config files.
Given the mentioned tweaks the game Runs well. GPU benchmark gave me [Avg: 137 fps] [Low 1%: 98 fps] [Low 0.1%: 74 fps]. Unfortunately dx11 prevents some graphics settings. For example ray tracing, even on the unstable dx12 it didn't let me enable it. But the game still looks good, so not a huge loss.
