Linux Port – Feedback, Known Issues, and FAQ

im not mad that it works.
game has not crashed yet today.

that being said, i wish i could figure this problem out so that i stop bugging the devs


EDIT: unrelated bug report
native linux build

i cannot for the life of me, take a screenshot with the in-game picture tool.
every pictures are borked.


makes cool corrupt pics tho xD

 

I cannot manage to get the game running on Wayland currently. It works on Xwayland, but when trying to use the environment variable for native it freezes on "|D|gfx| Device created, setting adapter and enumerating modes". For now I can continue running the game through Xwayland, but I'd like to have to option for better performance.

Log from console launch with an empty user folder (the game does not dump anything to the log):

Spoiler: Log

Code:

Shutdown handler: initialize.
  >>>>  [CURRENT_CONFIGURATION=SHIPPING=BNG_SHIPPING]  <<<<
  0.04752|D|saveStoredVersion| Saving version '0.38.3.0' to ini file '/home/wiget/.local/share/BeamNG/BeamNG.drive.ini'
  0.04762|D|crashrpt| Installing crash reporter on path: /home/wiget/.local/share/BeamNG/BeamNG.drive/current/temp/crashReports
  0.15632|I|engine| Virtual Filesystem: user path: /home/wiget/.local/share/BeamNG/BeamNG.drive/current/ (Default behaviour)
  0.15634|D|main| H2 3FE7A49046807CD2034FE84786E1E6A35553
>   0.16644|I|init| Initializing platform...
  0.16671|D|engine| initializing 115 modules (only displaying anything above 0.1 s)...
  0.16673|D|gfx| GFX Init:
  0.16673|D|gfx|    Null device found
  0.16710|D|fmod| FMOD API version: 2.03.09
  0.17474|D|sfx| Using default audio device: Backbone One Analog Stereo
  0.17664|D|_init| SFXFMODDevice FMOD Driver info:
  0.17664|D|_init|  - id: 0
  0.17664|D|_init|  - name: Backbone One Analog Stereo
  0.17664|D|_init|  - systemrate: 48000
  0.17665|D|_init|  - speakermode: 'Stereo' (internal id=3)
  0.17665|D|_init|  - speakermodechannels: 2
  0.22455|D|sfx| Created FMOD device 'Backbone One Analog Stereo'
  0.22456|D|sfx|   CAPS_VoiceManagement
  0.22473|D|sfx|    Provider: FMOD
  0.22474|D|sfx|    Hardware: false
  0.22474|D|sfx|    Buffers: 16
[S_API] SteamAPI_Init(): Loaded '/home/wiget/.local/share/Steam/linux64/steamclient.so' OK.
  0.23406|D|Steam| Could not initialize Steam functions
  0.23406|E|OnlineServiceProvider| Could not initialize online service provider: Steam - Error code 1
  0.24575|I|GELua.| ============== GELUA VM loading ===============
  0.32131|D|GELua.core_versionUpdate.| Current version: '"0.38.3.0.19003"' ('"0.38"'), last version: '' (''), newInstall: 'true'
  0.32132|D|GELua.core_versionUpdate.| Folder cleanup skipped
  0.32138|D|GELua.gameplay_missions_progress.| Loaded 0 condition types from 0 files.
  0.32204|D|GELua.gameplay_missions_missions.| Loaded 2 procedural Mission Generators from 2 files.
  0.32301|D|GELua.gameplay_missions_unlocks.| Loaded 10 condition types from 4 files.
  0.32562|D|engine| ... all modules loaded in 0.159 seconds
  0.32594|D|init| OpenXR: Steam VR mode: disabled
  0.32594|D|init| SaveData cloud sync status: inactive
  0.38841|D|gfx| Available adapters: 3
  0.38843|D|gfx|  - name:GPU (Vulkan), outputName:\\.\DISPLAY3, gfx:Vulkan, gpu:GPU
  0.38843|D|gfx|  - name:GPU (Vulkan), outputName:\\.\DISPLAY4, gfx:Vulkan, gpu:GPU
  0.38843|D|gfx|  - name:GFX Null Device, outputName:, gfx:, gpu:
  0.38843|D|gfx| Attempting to create GFX device 3: GPU (Vulkan) [with output \\.\DISPLAY3]
  0.38844|D|gfx| shader model: 5.0 , available video modes: 23
  0.38845|D|gfx| Device created, setting adapter and enumerating modes

 

I have the same issue on Windows with Vulkan, fwiw

 

Latest version of the mod which works fine on windows is installed.

Here's the log file, I can't make heads or tails of it.

https://drive.google.com/file/d/168jhd1ctW8wbf6X5Asea47UNNHzutBHT/view?usp=sharing

(won't let me upload directly here for some reason)

 

i want to hopefully further give more bug reports, so hopefully this has potential valuable information.

the bugs ive had and reported in this thread regarding "ErrorDeviceLost" is quite inconsistent, one day itll crash while im driving alone in JRI, and the next day, i can play no problem on that same map, but another map will crash.
as inconsistent as it is, when the game crash, its the only consistent thing, at about 10 min of playtime before the game crashes.
if the game didnt crash within 10 min, that "usually" means its fine.

but today, i decided to go on "OGC the ultimate map"
https://www.beamng.com/resources/ogc-one-the-ultimate-map.22814/

and ive officially had the biggest system crash while playing beamng.
it passed the 10 min mark, and ive been playing for almost an hour until this crash.
while i could still move my cursor, i could not even open a terminal.
i use a software called "mission center" that is basically task manager on linux. and i couldnt even kill beamng's task, or any task for that matter.
steam itself, would alternate between different game icons in the "task manager" and would refresh every second.
restarting my system only froze it, i had to manually shut down the desktop by holding the power button.

for the record, i was playing without traffic, by myself, in this map.

beamng's log abruptly stops and give zero information whatsoever.

BUT I HAVE A SYSTEM LOG!!!

i have specifically copied the exact moment beamng crashed, up until i forced my desktop to shut down, in the attached txt log

hopefully there is information in there that can actually be helpful to the devs.

 

What's you system specs, and does crashes happen on other heavy games?, might be hardware issues and only happens for this game?

 

Thats interesting, i only had such behaviour with proton games so far. Full system lockups i mean. My last effort is always to go into a different tty console with CTRL+ALT+F1-12 and hope to reboot the user session from there (cause hdd's and ssd's really dont like it to be powered off by force)

 

im running linux mint 22.2 with a ryzen 5950x and an RX7900XTX with 32gb of ram.
every graphics settings is on ultra/highest i can possibly put it. 1080p tho

and i only get these crashes with beamng, ive been posting about these issues since early dec lol.

idk what to say other than nothing worked. i tried a few combination before forcing a restart. but what can you do when its fully jammed ¯\_(ツ)_/¯

 

thanks for the reply. at least now i know its an amdgpu driver issue.

99% of times ive ran beamng with "-gfx vk debug" enabled, the game ran sub 30 fps and refused to crash. i only got it to crash once with debug enabled.
but i didnt try with the flushLogErrors command. hell, i didnt even know it existed. so ill try that next.

that being said, if its an amdgpu driver issue and that you cant do anything, what is the best next course of action?

bugging amd?

who do i make a bug report to next?

theres no way in hell im going to sit idle and wait for a magical fix, i live for this game.
hell, im constantly trying to mod and make content for this game.
but these issues has been putting a halt on my projects.

and beamng has been the only game this happens with. ¯\_(ツ)_/¯

 

Steam Cloud works now, also, great!
I wonder how you figured that out as BeamNG.drive is still not advertised as "Linux-Compatible" in the store.
I could not find anything regarding "app_mappings" in the steamworks documentation.

 

If you add amdgpu.gpu_recovery=1 to the kernel boot parameters (e.g. GRUB_CMDLINE_LINUX if using grub) does the desktop stay alive or ever recover after the crash to be able to get more log info?

 

Totally offtopic ofc, But same here. Ever since 0.35 got released the game became more and more unplayable for me, it started with vysnc crashing the amd driver, then graphical bugs, then texture corruption and now since im on linux i just cant enjoy the game anymore because its all the previous issues + half the fps. Just havent found my peace with this situation yet to continue modding it

 

ill need to try that and get back to you when i have more data
that being said, the system log continues to log information, but beamng's log is cut short.
but ive just now added that line in my grub file thingy.

forreal its driving me nuts.
i nuked windows in oct after going in circles with support to no avail, because id get "status heap corruption" on there.

and while i believe the game is more stable for me on linux, i still get these extremely inconsistent crashes, and it changes on a day to day basis, which makes it even harder to track down.

and to add insult over injury, i have a 2nd pc with a 2060 super, and id also get the same status heap corruption crashes on windows there.
that being said, ive been meaning to install linux on that desktop with the 2060, just to test beamng out. havent had the time yet.

but if beamng is getting crashes bc of amd drivers, shouldnt they report it or something?
i mean... pardon me for being naive, and thinking that, reporting bugs would get them fixed. (gotta give devs time to cook for sure)
but their drivers are negatively impacting your software, shouldnt this be considered unacceptable?
again, pardon me for being naive.

i need to abandon beamng for a while. this is just infuriating. give the devs time to further look into this issue. but at the same time, more data means more potential to find and fix the issue.
if it was only linux the problem, id be less salty, but the game will literally crash on both windows and linux, multiple people reports status heap corruption issues on windows, the game barely functions as it is. and thats on both nvidia and AMD gpus.

getting really tired of going around in circles like a dumbass with these crashes for months without end.
its my favorite game, i literally mod nothing else. and i cant even play it anymore.
been playing since literally their first fastspring release, and it didnt crash as often as it does now.


sorry to the devs if im giving ya a hard time, i genuinely love this game, i genuinely want whats best for this game, but this is just infuriating.

 

I'm wondering if it's a Linux Mint mesa version 25.0.7 specific driver issue that could be causing this?, have you tried the game on a different distro with a newer mesa? (or update the mesa version via a ppa on mint if you want to go that way),

I'm on Arch Linux with a 7800XT with mesa 25.2.x drivers (now 25.3.3.1 which only just released) and I have no issues running the game daily and my 7800 is also on RDNA3 too, (I do have the occasional black flash during window mode, and even time the mouse show/hides in Fullscreen/Borderless it flashes black each time, and a license plate texture corruption issue too, but nothing to stop from playing), I believe that version of mesa had some Vulkan instabilility until mesa 25.1.x+ had much better support/stability.

Might be something to look into?

 

7700XT user here. Do you also happen to have this issue?

--- Post updated ---
I think this is kinda interesting. My game runs fluidly when i have 8 or less cars. It averages at 73 fps. Now as soon as i spawn a single car more then 8 my avg dip down to 20 fps. Thats a huge drop. So i figured i look at the graph.

With 8 cars PhysicsAndVLUA avg at around 4ms (1ms min, 12ms max)

With 9 cars PhysicsAndVLUA avg at around 37ms (35ms min, 44ms max)

Im running a 6C/6T Intel 9600K. So i imaged that if it where the core limit that it would hit earlier then 8 cars.

Then interestingly it isnt an instant fps drop either. When i pause the game and then unpause you can see that the time PhysicsAndVLUA takes slowly builds up. Can see it here. Everytime the total frame time dips is when i paused the game.


Starts at 11ms then crawls up to 37ms avg. where it stays stable.

 

I get similar flickers here and there yes, note that I believe adding ai traffic is very cpu dependant, has it needs to calculate for each vehicle jbeams also (even though they are simplified ones), heck even parked vehicles alone make the fps drop.

even my 8core 16 thread Ryzen 7700 struggles, hench I hardly add traffic myself (once in a while, but don't likey low fps lol).

 

ive successfully upgraded to Mesa 25.2.8, even if its not the upmost latest release, its progress
while its still too early to say its fixed, ive got plenty of other things to do.
i still have to triple check with my system, ive been holding back upgrading my bios, and mint now has 22.3, its going to be a week of upgrading and testing again.

but genuinely thanks for mentioning these drivers, im still somewhat new to linux, so every bit of information is gonna help. i highly appreciate it.

 

The interesting bit is the sudden jump of the physics frame time. Like it takes 4ms to compute the physics of 8 cars in parallel and then suddenly 37ms for 9. And that not immediately either but it builds up to that spot. If i now also pair this with my earlier report of how the game only ever just takes 50% cpu and completly flats out at that spot (stating that the game is running into a physics limit) then i would say these are the characteristics of a bug in the ipc (things waiting long for data or access to memory) that for some reason only occurs after the 8 car limit in my case