PonPon
Published
%command% -nointro
Selected "Launch with OpenGL"
After switching to OpenGL, observed minor texture artifacts in road decals
Native version locks cursor into the game window, Windows version does not do this (hence why I forced Proton)
Game only reads input from evdev so my Arduino button box (that sends correct inputs over joystick and incorrect inputs over evdev) needed to be reprogrammed to send keystrokes.
Game occasionally froze my PC, with crash logs indicating a problem with dxgi.dll. Switching to OpenGL seems to have fixed this.
Overall, not difficult to run using Proton, but there is a Native version. I recommend trying Native first, then force Proton (launch with DX11) if you don't like Native, then launch with OpenGL if you experience problems with the DX11 version.
Significant performance loss when compared to running Windows. Some audio issues left unresolved. Tinkering had minimal help.
gamemoderun %command%
Tried changing renderer to D3D_11, VULKAN
Game audio did not play after tinkering.
Significantly lowered settings to achieve playable framerate
Controller was locked at full left input, and had to be disabled.
20-40 FPS on medium, as compared to on Windows 10 where I can run max settings at 60 FPS.
Near parity with Windows
Near 60FPS in 2k Very High settings. Some stuttering. Expected 60 FPS.
Performance issues were resolved by updating to latest drivers. There are issues with 4070 graphics cards not being registered in the nvidia-detect/nvidia-driver package causing the incorrect drivers to be installed by the package manager. 535 drivers had to be manually installed from the NVidia website.
Sand didn't render or made "walls"
Sand either renders as "walls" or not at all, making playing the game difficult. Tried many environment flags to no avail; issue seems to be unimplemented methods in vkd3d. See vkd3d-proton#2183.
Heavy texture issues, flickering lights
Occasionally froze on launch
The game requires a specific version of vkd3d, included in bleeding edge Proton Experimental, or the latest GE. For stability, I recommend GE. Also requires two specific tweaks to the in-game settings. First, in the main menu I set "surface quality" to low to fix the rendering issues. Next, I turned off anti-aliasing to fix the flickering lighting. See ValveSoftware/Proton#8206 (comment) for more details.
VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command%
Heavy artifacting in sand, fixed by setting Surface Detail to low from the main menu. Flickering textures, fixed by turning off anti-aliasing.
Even with upscaling, couldn't achieve 1080p60fps and had hitching, on high or above graphics settings.
Crashed in tutorial, fixed by setting launch option
The game currently has many issues, as tracked in ValveSoftware/Proton#8206. The main one preventing launching is fixed in the latest VKD3D, meaning your Proton version needs to include it--either the latest GE, or bleeding edge Experimental. Working through the fixes there the game is in a playable state, albeit with lower frame rate and significant hitching. Unable to verify which of these are Proton-specific issues, but my friends on Windows have reported LOD issues so performance is likely due to being in Beta.
Native works near perfectly OOTB
Minor hitching
Long range comms tutorial did not start
~4 hour session with a full crew at points. No issues.
Minor issues did not affect gameplay. Bug reporting also appeared to be broken. Did not verify these issues are Linux-specific, nor did I test if they were in the Proton version.
Game mostly works, but memory leak causes system crashes
Window needs a moment to resize when tabbing in and out
Had to switch to 1/2 res as others recommend
Memory leak locks up the entire system after ~2 hours of gameplay
Memory leaks only observed in MP, though I have not played the longer SP scenarios
Overall, game works OOTB with any performance issues carrying across from Windows. Minor windowing issues when alt-tabbing, but nothing that affects gameplay. A memory leak was observed during extended play in both driver and dispatch mode; will investigate if other Proton versions fix it.
Modified Flatpak scope to limit memory usage, using systemctl --user edit --force app-flatpak-com.valvesoftware.Steam-.scope
Settings:
[Scope]
MemoryHigh=50%
MemoryMax=75%
Slight jitter when alt tabbing as the taskbar hides itself.
Memory leak caused complete game lockup after ~30 minutes on some dispatch boxes (due to exceeding the MemoryLimit)
Memory leak (see above)
Memory leak cases issues, see tinker instructions. Game will still lock up once exceeding the set limits, though I have seen better results in "less leaky" locations. The fastest I have seen is lockup at around 16GB RAM in 1/2 an hour, though this was at a particularly bad location. Other times, my fix above allows the game to limit its RAM usage more properly allowing for extended play. Leak may also be on Windows but difficult to verify. See my reports in the Proton repo and SimRail forum.
DXVK_HUD=devinfo,fps,memory,gpuload,version,scale=2 %command%
As others have reported, use 1/2 resolution textures or lower to avoid killing VRAM.
Crashes after an hour or two, which for me is every game session
I started on Debian, experiencing a memory leak per my report from when I was on Debian, that caused my system to lock up unless I restricted its memory access. This persisted long enough that I replaced my RAID0 with an SSD and decided to install Nobara. On Nobara, even with its up-to-date custom Nvidia drivers and CUDA support, the game continued to leak memory, though I didn't experience full lockups (which I theorize is due to setting a larger swap). I continued digging, and found that it likely is a known problem in DXVK combined with bad code in the Unity Engine. The launch options above are included to verify I was using DXVK, but also to monitor the VRAM usage. Forcing OpenGL (using the PROTON_USE_WINED3D launch option) just breaks the game.
Today there was a CUDA driver update, which seems to have solved the memory issue, but introduced the random crashes mentioned earlier, which prevents me from playing longer sessions (which in this game is critical due to its 1:1 scale train routes).
-skipintro
Have protontricks installed, but the wineprefix should be fresh
Crackling on initial load, no menu music, item construction sounds missing
After much trial and tribulation, using Proton 6 through 9 and experimental and GE9-1 I finally got it working on GE8-32. No intro flag is due to personal preference; haven't tried without that flag. Briefly loaded a save and didn't test multiplayer, so long-term stability is unknown. Overall seems to have less stuttering than when I play on Windows, though that could be due to the better drives I use on my Linux machine. The missing audio is minor. Will tinker some more to see if I can get the audio working with ProtonTricks.
Works OOTB with no tinkering.
Ran a cold start while hosting a server. No other players joined, but no issues observed.
On Wayland, selected "Play using DirectX 12" on first launch. Played through the tutorials and the above "scenario," which took about an hour. Observed no issues.
