Hello @HonkingGoose, the desktop session crash should probably also be mentioned to your desktop environment devs and video driver vendor if it hasn't been already.
OMSI 2 Works for me in KDE, however after driving a bit, OMSI 2 Freezes with the this log.
Did somebody figure out how to fix this fullscreen issue (DE is Budgie)?
The orange startup menu has a fine black screen, but afterwards the menu bars of Budgie appear - and other games do not have this issue.
[636630] Busbetrieb-Simulator fails to launch the main OMSI 2 game .exe
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8426.
@GameBurrow posted on 2025-01-29T12:59:23:
OMSI 2 Add-on Busbetrieb-Simulator636630RTX 3070Ti Laptop / RTX 3080 eGPUnvidia-driver 565.77Linux 6.12.11-204.nobara.fc41.x86_64Proton Experimental / GE-Proton9-23 / Proton Hotfix / Proton9.0-4 (all of them)The DLC itself launches and you can navigate it and interact it. Even multiplayer 3D environment works (with some windowing issues). However in all cases when the DLC has to launch the main game omsi.exe nothing happens
This is not system related issue (tested over multiple computers and multiple distros over the past 3 years, all behaved the same).
Z:\home\\kert\\.steam\\steam\\steamapps\\common\\OMSI 2\\ because that's the only way I could locate the game exege-proton9-23x1 2025-01proton experimentalx1 2025-01proton hotfixx1 2025-01proton9.0-4x1 2025-01
Compatibility Report
System Information
Game information:
Version: Release 2.3.004
I confirm:
Test report:
Steps to reproduce:
the whole desktop session is trashed, and you need to re-login into your desktop.
Other observations:
The game crashes a lot, and it also crashes hard, it takes out the entire Gnome display manager, and crashes you out of the desktop session entirely (like logging out).
I can't pinpoint the exact issue here, I've had crashes while:
There is a in-game option to enable/disable multi-threading,
this doesn't seem to make any difference with regards to stability.
Summary:
The game is is unplayable in its current state.
The crashes don't put you back in your previous desktop environment, they take out the entire desktop session; you need to re-login to your desktop session.