Linux Port – Feedback, Known Issues, and FAQ

script only help for 100% cpu occupation if it happens to u
in case u get out of ram u could try killing proces just before it reaches limit
if u disable traffic tottaly u still get out of memory probs?
--- Post updated ---
oh and in case u use any mods
disble them xD

 

Hi, the Steam Launch Property:

Code:

mangohud SDL_VIDEODRIVER=wayland ./BinLinux/BeamNG.drive.x64 %command%

Is not working on my machine anymore after the GNOME 49 update.

Specs:

 

I can't get VR to work on the native Linux version. I've got an Index HMD but when I have SteamVR open and click the button to start VR it throws an error: here's what I found in the logs when I press it

Code:

 24.52250|D|operator()| OpenXR 'toggle' called. Current state: disabled
 24.52250|I|init| Enabling OpenXR...
 24.52864|E|logIfError| Error in xrEnumerateInstanceExtensionProperties (1): xri = 0x0, getXrResultStr(-51) = "XR_ERROR_RUNTIME_UNAVAILABLE"
 24.52865|E|setEnable| Unable to enable OpenXR
 24.52865|I|shutdown| Disabling OpenXR...
 24.52865|I|shutdown| OpenXR disabled
 24.52869|D|GELua.render_openxr.| Unable to enable OpenXR
 24.52871|E|GELua.render_openxr.| An OpenXR error was detected with error ID: "generic"
 24.52872|E|GELua.render_openxr.| openXR error detected: An error occurred. Some information is available in the logs. You can contact our <a href="http-external://go.beamng.com/support>support team</a>.
 36.45901|D|BeamNGCefApp::OnBeforeNavigation| External link: http-external://go.beamng.com/vr -> http://go.beamng.com/vr, result: ACCEPT

For what it's worth I couldn't get it to work running the game through Proton either, I get the same error basically.

 

It works ok with. Monado/Envision. Start here: https://gitlab.com/gabmus/envision. I used the AppImage. All problems I encountered were fixed by GROK. Mostly prereqs (Nobara). HTC Vive Pro, RX9060.
Pretty amazing to run BeamNG,BeamMP and VR natively on Linux

 

I was able to get this (and other OpenXR applications) working with Monado

There is still an odd thing that is happening, which is that all of the UI elements are misalligned on the lenses which results in a very disorienting double-vision effect. I've tried tweaking all of the UI settings in the menu to fix it but nothing worked so I ended up disabling it. Everything else seems to render fine even if the performance isn't amazing

 

Try adding OXR_PARALLEL_VIEWS=1 to the game's launch options.

For example, like this:



Or OXR_PARALLEL_VIEWS=1 %command% if you are launching the game from Steam as a non-Steam game.

 

Seems that career mode is completely broken now. I can't access it at all. New or old save, with or without mods.
I've attached the log file with all errors.

 

What exactly is the deciding factor for getting cloud saves to work? Simply being a steam deck ie. steamdeck=1 does not seem to suffice. I was launching the game via Steam using Proton. Or must you explicitly use SteamOS?

 

Yes, I can confirm that the career mode is not working. There is an endless loading on the loading screen and a lot of errors in the terminal.

 

Overall game seems to be working even better than before on Linux! I am getting a "Processing vulkan shaders" pop up when launching through steam (launch options set to use linux version) which I have been skipping, as I wasn't sure if it was processing the shaders for the right version of the game or not.

Career mode works fine for me if I launch directly into it. I was able to create a new save, and load that same save after fully quitting and restarting my PC. I didn't try loading a save from a previous game version.

If I launch Freeroam first, then try to load into Career mode my entire system freezes, and I have to force restart. - EDIT: After letting vulkan shaders process this is no longer an issue, maybe coincidence though, I don't know.


EDIT: Did some quick performance comparisons on WCUSA before and after letting vulkan shaders process. Seems like I get a 3 - 10FPS boost by letting it process (80 before, 85-90 after).

System specs
- OS: Arch Linux (using experimental Wayland launch option)
- CPU: Ryzen 3600x
- RAM: 16GBs
- GPU: RX 6800xt
- Storage (where game is): SSD

 

How do you set launch options to use Linux version?

If I un-tick this in the game's properties, it is still launching the Windows-version of the game.

 

when you clone a vehicle on linux, it throws an error about a file name too long.


and i tested it again to double check, it doesnt happen only if you spawn a vehicle, it happens only after i changed a part on the vehicle.

i spawned a vehicle, cloned it, i didnt get an error.
i changed a single part off of that vehicle, and then i got that error after i cloned it.

so it only happens after you changed a part on the vehicle.

and after this happens the game is stuck on the lil clock and wont budge.

this issue has been happening to me since at least 0.37, (but i didnt try linux before 0.37 so idk)

and just to make 100% sure, i tested this with ZERO MODS INSTALLED!! IN SAFE MODE!!

i spawned with a pessima, cloned it, no problem, i literally added the beam navigator (it doesnt matter which part you change) and then tried cloning, and got the same error again.

THIS IS WITH NO MODS!!!

and i double checked to make sure this issue wasnt happening on windows, its a linux specific problem because of longer file names.


so TLDR: On linux only, you get invalid filename error ONLY AFTER YOU CHANGED A PART!
you can clone configs that wasnt changed, but the second you change a singular part off of your vehicle, you can no longer clone it.
also only on the native linux build. doesnt happen through proton.
--- Post updated ---

if you put this command in your launch options, beamng will launch the native linux build instead

Code:

./BinLinux/BeamNG.drive.x64 %command%

 

@crashmaster Thanks for the tip!

I also tested cloning a car after changing one part on it and I get the same Lua-error as you. And only on the Linux native version.

 

I was about to post this last night, but the website error out for some reason,

a temp fix I found is, for the filename length issue on linux,

goto this location (or right click the game in steam, properties, installed files, browse):
~/.local/share/Steam/steamapps/common/BeamNG.drive/lua/ge/extensions/core/vehicles.lua

change line 1540:

Code:

if type(opts.config) == 'string' and opts.config ~= "" then

to

Code:

if type(opts.config) == 'string' and opts.config ~= "" and not string.find(opts.config, "{") then

fixes the issue for me.

*updated with the actual file name!

 

I can confirm, and it does this on BeamMP. I can't get an error though because the console is currently being spammed by the Nav app.

Edit: Got a picture of it.

 

I'm running into a problem with the Vulkan renderer of BeamNG.drive crashing on startup. I've enabled the Vulkan validation layers and attached a debugger that confirms that the crash relates to a NULL `vkImage` passed to `vkGetImageSubresourceLayout`. You can also see the validation errors in the attached `beamng.log` file.

The Vulkan backend also crashes under Proton in "Vulkan Mode". The "Launch (safe+Vulkan-debug mode)" launch option doesn't work under Proton because it doesn't find the Vulkan validation layers. I didn't know whether this belongs to the Linux or Vulkan thread. I've chosen Linux since it's probably the smaller niche.

- BeamNG.drive 0.38.1.0
- NixOS unstable (flakeref: github:NixOS/nixpkgs/f61125a)
- GNOME 49
- Linux 6.12.60
- Mesa 25.3.1
- Intel(R) Arc(tm) Graphics (MTL)
- Framework Laptop 13 (Intel Core Ultra 7 155H)

The attached `.zip` file contains a `.nix` file that can be run using `nix run --file beamng.nix` (assuming you've installed BeamNG in your steam installation root and you're running NixOS) and the minidump `.dmp` file from the crash.