PlayableShow Details
Unknown
MANGOHUD=1 gamemoderun %command%
Sometimes when resizing bottom half of the window frezes or lags
all things work great out of the box, reseted all my progress in single player
(none)
Running MXLinux with newest nVidia drivers. Significant performance problem with no resolution scaling. With resolution scaling in graphical settings set to 1/4 performance greatly increased with little quality impact. Also either after SimRail went v1.0, or using GE proton 9-21, the grass is visible again.
MANGOHUD=1 gamemoderun %command%
Game runs way slower than on Windows, especially in urban areas.
Multiplayer works okay.
Pretty much the only problem is performance.
Playing online works like a charm, Just, selecting the correct mic took a while.
Tested with GE-Proton9-15 and Proton 9. Every aspect of the game works well. Sometimes, the game could run slower than expected, but I couldn't nail the reason.
Now, for the RAM: If the game starts, it uses ~5GB. after a nice hour of playing, the game uses >20GB. Which means, this game is only enjoyable, if you got a beefy gaming machine, with 32GB RAM.
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).
Everything works like on windows; no problems occured when using standard proton
Works like expected
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.
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.
Grass does not draw
People talking about it running worse is most likley due to settings resetting and there is problems with full res on both windows and linux, just switch over to 1/2 res for better FPS
Playable out of the box but expect lower performace
Game running at 20-30 fps most - with my hardware I would expect much more.
Aktuell nicht lauffähig auf Ubuntu 23.10!
nicht funktional
Alle Proton Fassungen von GE und Steam durchprobiert. Lutris spuckt eine Fehlermeldung aus, dass das Game keine Startdateien zum Starten hätte. WINE spuckt direkt einen System Error aus.
mangohud %command%
Grass is not rendering
Early Access does not have save function
GNOME 44.7 / Mutter / Wayland
mangohud %command%
Early Access does not have save function
GNOME 44.6 / Mutter / Wayland
Gras fehlt komplett
Bei manchen Zügen springt die Maus nach drücken der linken Maustaste zurück in die Bildschirmmitte
Gras wird nicht angezeigt, Mauscursor springt in die Bildschirmmitte
Gras wird nicht angezeigt, Mauscursor springt in die Bildschirmmitte
Grass doesn't get rendered.
I didn't notice any issues.
So far, the game works fine on my system. Only problem is the grass, which doesn't show up (any more... it showed up earlier I think).
Regarding performance, I didn't compare it to Windows on the same system. However, I did test it on a laptop with a weak gpu, too. Turned out that the performance difference is quite noticeable compared to Windows there.
In driving mode, every click on train control will reset mouse cursor back to the center of the screen, which makes controlling the train pretty frustrating. Dispatcher seems to work fine on the other hand.
Game was still playable, but Windows version on the same hardware had more FPS on higher settings than Linux + Proton version
Especially low frequency sounds tend to crackle.
Works out of the box, sound might crackle a little. Use Proton Experimental.
With default Proton version, no digital screens in the cab, making the sim quite unplayable. Works with Experimental.
If I use any Proton version except Experimental, the graphical computer displays of the modern trains' cabs don't work. The screens just stay blank. They work fine if I use Proton Experimental.
If the user experiences hiccups like I do in urban areas, the experience is degradated, to the point that the sim becomes not enjoyable.
The game has frequent and long hiccups, especially in urban areas. In places I have maybe 1-2 seconds of smooth running (decent fps, even though lower than on Windows), followed by several hiccups, some maybe half a second or less, and some maybe 2-3 seconds. This makes the simulator barely playable in these areas. The same PC under Windows shows better fps and no hiccups at all.
I suppose it's not a problem with under-spec hardware, because under Windows it runs perfectly. The problem gets way worse if I move the view around, suggesting a bottleneck somewhere when loading new scenery or objects.
Horn sometimes sounds weird. Might be a game bug.
Lots of stuttering. But playable. Disabling Motion Blur helps.
It seems like there is a major performance bottleneck somewhere. I was running at 4k, and I usually do have stable fps with that. This might be the game itself, but it might also be Proton. A native Linux port might be interesting, however according to the official forum this might be not happening any time soon sadly.
Poor performance with ocasional crashes (once or twice / hour)
About 20-60 FPS On Medium wher on Windows there would be about 70 FPS on Ultra
Does not work on Wayland. Loading anything crashes the game and steam. This does not occur when using Xorg.
Mutiplayer works just as expected
After playing some time on both windows and linux the performance does not compare well. On Windows the game feels great on Ultra settings (70-100fps) and using Steam Play dropping down to medium is neccessary and even that does not give stable 30fps.
Using physical keyboard and mouse
Built-in display is too small for the text to be comfortably readable
Seems like these are game bugs though
Only when changing settings, not during driving
My recommendation for this game would be to have a PC-like setup, with kb, mouse and external monitor.
I do not recommend playing this in handheld as the text is hard to read and the locomotives would be too hard to drive anyway.
Deck settings:
- Interpolation set to FSR(3)
Deck modifications:
- 16GB swap
- swap aggressivity = 1 (CryoByte33's tool)
- 4GB VRAM
Game settings:
- resolution: 1600x900
- medium preset
With the settings above, I get around 15FPS in dense areas and around 25-30FPS in more open areas. The frame pacing is very good, so the gameplay feels smooth and I was actually surprised how low the FPS are.
Runs fine
I haven't encountered any problems yet
Slightly less performance than expected, running on Medium Settings with 70-90 FPS on an RTX 3080.
It crashed once in the first hour of gameplay, during the first tutorial. Did not crash again until now
Good game but some problems need to be improved.
On low graphic, I don't see traffic light. Cause me to lose scenario.
Sometimes, your scenario failed because of bad spawning.
Some big freeze but it's due to loading map.
This report has been writen when the game is on playtest.
The game is usable without any need of fixing libraries or linking. Maybe some problems can be explained through the game is still in beta.
The game feels a bit laggy, but I think that it is because it is a demo / beta.
After playing for some hours, the RAM was full and my computer irresponsive. This might be because a low-spec PC
