Linux Port – Feedback, Known Issues, and FAQ

Who's jenkins?

 

I get that same issue also when running that command.

 

Thanks, works now!

 

I have been able to work around the DOF shader crash.

I opened the Proton version and set all graphics to their lowest. I then copied the entire contents of the settings folder across to the linux directory.

I can then launch the game and get into the graphics settings.

It seems to be enabling Anti-Aliasing that immediately causes the same crash to occur.

However I am getting some errors loading vehicles.

 

YES, I am having this exact issue too with loading vehicles! Happens only on a few select vehicles. Below is my info. Hope it gets fixed quickly as I think it's a pretty major bug:



EDIT: I noticed that one of the broken vehicles for me (the Bastion) can spawn in traffic. Odd.

 

Sweet, much appreciated!

 

Holy crap that fixed the shader loading issue for me too. This is such a peculiar issue, I never would have thought some in game graphic settings would break the compilation process of game shaders.

Not to put any pressure on the devs but I feel this issue should be looked into because I get this shader compilation error right out the box. Besides, I would like to say thanks to all the devs for working on a native Linux build, yet alone even considering Linux and also thanks to all the testers / bug finders.

 

I get a lot of compile() issues for shaders.

 

BeamNG is having trouble loading some vehicles



Affected Vehicles (That I've tested): SBR, Vivace, Bastion, ETK800 + ETKC, Scintilla

OS: Debian 13 Trixie
RAM: 2x32GB DDR5
CPU: Ryzen 5 7600 (Overclocked)
GPU: EVGA GTX 1080 Ti SC2 (Overclocked)
SSD: 1TB NVMe
(This is the native version of BeamNG, I did not use proton)

I have tried clearing the cache in the beamng save file folder, and reinstalling the game along with verifying the game files

There is also a missing texture in the SBR

 

It looks like the issue stems from the CMU.lua, that gets loaded when a vehicle uses safety electronics. Once you remove them in the parts selector, and reload the car using Ctrl+R, it loads without an error.

Issue is only on linux-native beamNG, things work fine on windows-BeamNG trough proton

Edit: If you comment out lines 30, 264 and 267 in CMU.lua it seems to work fine. However im not completely sure what the purpose of CMU.lua is, so replicate at your own risk

 

Now I've been able to play the native port for some time again I just want to repeat a huge thanks for the Dev team for all their efforts. It seems like we're getting pretty close to a stable product.

Much to my surprise I've been able to run 19 simplified traffic cars on my 8700k and maintain over 60FPS with consistent frame times. Unfortunately that large number does lead to some crashes after a longer period. Knocking that down to 11 and it's closer to 80FPS with no stability issues. Amazing how far this game has progressed.

A note to anyone who is getting frequent crashes. Reduce Texture detail to low or lowest, Vulkan is still eating a huge amount of VRAM.

 

Thanks, this worked! Definitely not a permanent solution though.

 

I can also confirm this. On top of that I've been having some flickering issues, making the game unplayable but I guess this is a known issue as somebody else already reported on it. The flickering reduces the more I cap the fps. Capping it at 60 fps has reduced it quite a lot but flickering still happens here and there.

OS: Arch Linux (Kernal 6.9.8)
CPU: Ryzen 7 2700
GPU: AMD Radeon RX 570 (8 GB)
RAM: 16 GB DDR4
DE: KDE Plasma 6.1.2

 

Here's a temporary (And sloppy fix):

Head into your BeamNG folder and copy the patch into the base folder, and do git apply ./beamng.txt {Make sure beamng.txt is the name of the file you saved}

All it does is add a fake udp socket (Which appears to be broken in this update, but this is still better than removing the udpSocket lines)

 

I also noticed a bug to where in settings, if you try to set it to a function key, it will just get binded to "F" (Here is me trying to bind "Drop Camera at Player" to F6, but it just says "F", and is activated when I press "F", but if I instead revert it, it's still binded to F8 and works when I press F8)

 

Back from Japan, updated my main System, updated BeamNG, and now I get flickering black frames...
If I were on nVidia with that System, sure, but my PC has an AMD GPU?

interestingly, the Issue also appears with the Windows version in Vulkan mode through Wine

 

Also experiencing the same issues with vehicle loading - weirdly, changing the driver that loads my (NTFS) partition from ntfs-3g to lowntfs-3g causes similar errors with even more vehicles (same socket issue) - fixes above work for most cars for me

 

Same, all AMD system here. Flickering can be fixed temporarily by loading a different car

Otherwise, the performance is really impressive