Linux Port – Feedback, Known Issues, and FAQ

When I turn on HDR Output in the display settings, everything just goes completely white/blown out. Doesn't matter what I do with the Peak white nits or Paper white nits sliders either — tried dropping peak all the way down to 400 and it made zero difference, so it's not a brightness calibration thing.

One thing I noticed poking around the settings: "HDR Output Mode" just shows "scRGB" as a static field, no way to change it. From what I understand scRGB is the format Windows uses to hand off HDR to the desktop compositor (DXGI/DWM), but Wayland compositors like KWin expect PQ/HDR10 encoded content instead through the Wayland color-management protocol. So my guess is the Linux build might still be using the same HDR output path as Windows instead of one built for Wayland, and KWin is misinterpreting the values because of that.

To rule out my setup being the problem: I already went through KDE's own HDR calibration wizard (System Settings → Display), and my desktop, wallpaper, browser etc. all look completely normal with HDR on — no washout at all outside of BeamNG. So it seems isolated to the game specifically.

My specs:

• CachyOS Linux, kernel 7.2.3-1-cachyos
• CPU: Ryzen 7 5700X
• GPU: AMD RX 6950 XT, RADV Vulkan driver, Mesa 26.2.2-arch3.2
• KDE Plasma 6, KWin, Wayland session
• Monitor: AOC AG276QZD2 (QD-OLED, HDR10), DisplayPort
• BeamNG 0.39.4, native Linux build (not Proton)

 

Same issue here, also kde plasma, amd gpu/cpu and cachyOS linux and an qd-oled HDR 10 monitor. in the proton build HDR does work

 

Is it a known issue that you can't subscribe to a mod on the website? When I click on subscribe nothing happens (should open the game, which is running in the BG). Anything wrong I'm doing?

 

Try symlinking the certs

```
ln -sf /etc/ssl/certs /etc/pki/tls/certs/
```

 

while testing yesterday, i noticed launching beamng without steam would make the ps5 controller suddenly have functional sensitive triggers and rpm light?
but when launching through steam with steaminput, none of that was functional? and just disabling steam controller input just breaks the controller function entirely.

am i missing something here? or launching through steam breaks the ps5 controller features?

 

computer is allergic to loading

it will not load. black screen

it will load when i use proton experimental and default (D3D12) but then my MODS are all gone and that's kinda 100GB of used space here

Linux Mint 22.3 x86_63, Cinnamon 6.6.9, i5-10400F and a Radeon RX 5500 with 16gb DDR4

--- Post updated ---

i can hear menu music and apparently i can also hear the UI being interacted with BUT it

is frozen

 

update: apparently just outright a goddamn VULKAN issue. as per logs


Failed to submit to transfer queue [ErrorDeviceLost]
Failed to submit to graphics queue [ErrorDeviceLost]

also im typing this on phone, my pc has crashed due to BeamNG in the background not abiding to close commands.
--- Post updated ---

reloaded PC, obliterated my mods folder and it launched

small issue is that now i'm seeing frame bleeding from Beam's main menu, specifically green (likely foliage) into firefox
im gonna launch GSP with a pessima and see what happens

 

Hi, currently trying to run BeamNG on linux through steam but it crashes almost immediately after startup.

beamng.log shows no errors, it seems to cut off at random points each attempt so it's likely irrelevant.

Running BeamNG directly outside of steam gives the same result, even when running with -safemode.

journactl shows that BeamNG encounters a segfault, but this is the only other information I could find.

Code:

kernel: ===>>> BeamNGMa[4437]: segfault at 68 ip 00007f4bfc241771 sp 00007ffd7cdf5eb0 error 4 in libvulkan_intel.so[41771,7f4bfc20b000+ace000] likely on CPU 2 (core 12, socket 0)
kernel: Code: 56 41 55 41 54 49 89 f4 53 48 81 ec f8 00 00 00 48 89 bd f8 fe ff ff 8b 7a 10 64 4c 8b 2c 25 28 00 00 00 4c 89 6d c8 49 89 cd <81> 7e 68 30 33 9d 3b 0f 84 c2 01 00 00 48 89 95 e8 fe ff ff 83 ef

I have also attached beamng.log, even though there probably isn't much useful information in there.

I'm trying to run BeamNG natively on linux with vulkan. Proton with DX12 works just fine.

Specs:

Spoiler

OS: Arch Linux
Kernel: Linux 7.2.9-arch1-1
Memory: 32GB
CPU: Intel(R) Core(TM) Ultra 5 235U (4+8+2) @ 4.90 GHz
GPU: Intel Graphics @ 2.05 GHz [Integrated]
DE: KDE Plasma 6.7.5 (Wayland)

 

Excluding the fact that you use the inferior operating system
what i did to get mine to run is remove all of my mods, verify files a good 859 times over and over again until i got bored, restart my computer (it had an 8 day uptime) and run the game quite smoothly
not sure if that helps

 

Hi, I'm experiencing the same issue as here (https://www.beamng.com/threads/linux-port-–-feedback-known-issues-and-faq.86422/page-64#post-1950473), but i didn't see anything else about it and have some things I've noticed about it.
First of all a short description of the problem: many letter keys such as a, s, d, and p do not register in the game (except when assigning controls oddly enough). What I believe to be causing this problem is the game is improperly reporting if it's a game or something like that, because holding down the keys long enough brings up KDE's widget to select alternate versions of a letter (like á, â, š, ď, etc.) and this only applies to letters that have alternate versions. I'm reporting this here because I tested with another game and BeamNG both through proton and didn't experience this issue.

Computer Specs: Steam Deck
OS: Fedora 44 KDE
Game Version: 39.4
KDE Version: 6.7.5
Kernel Version: 7.2.10-200.fc44.x86_64 (64-bit)
Etc: Game Running through wayland, launched through Steam

Thanks for making this great game run on linux, and for accidentally teaching me about all the extra characters I can easily use!

 

heh, somehow this time it's not the arch user being the supremacist

i have a feeling this is probably something much lower level, either to do with the graphics drivers or a bug with beamng.
leaning more towards it being the driver's fault, as intel's igpus have always given me a headache with gaming on linux (HL2 STILL crashes on linux with vulkan enabled).
even so, i have verified and tried again many times, haven't gotten it to work.

 

i have an i5-10400F, there is no IGPU, and since i'm using the superior GPU manufacturer I don't require drivers

 

Damn, I remember when 0.15 was new. Time's flying by too fast for my mental to keep up.

 

So there is extreme graphical corruption on Linux making it unplayable.
Proton 11.0-2
Linux Mint 22.3 - Cinnamon 64-bit
AMD Ryzen 5 4500 6-Core Processor
32 GB RAM
AMD Radeon RX 9060 XT 16GB

 

sooo, zero linux bug fixed with 0.40 even tho i literally posted the bug fix to the file reload bug for linux months ago.
probably just missed it but. ey. if you are trying to mod on linux and find out that reloading your vehicle doesnt do the trick, this is why.

 

FSR4 is not supported on linux? Or if it is, how to enable? Fedora KDE and RX 7800 XT

 

"I mod on Linux Mint"

...So you should know that Linux as a system is not a one-size-fits-all like Windows tries to be, yes? There's a reason why we all put our specs here when we have an issue. Some of my issues with Beam are exclusive to me because I run an alienware and Dell HAAATES Linux.