Linux Port – Feedback, Known Issues, and FAQ

sadly still doesn't seem to want to start on Wayland with nvidia-open 565

 

I've been playing for a while on the Linux version of the game and have noticed some issues with FFB on my Moza R5 wheel which don't happen when using Proton.

After doing some very unscientific A/B testing between the native Linux version of the game and the Windows version through Proton I have noticed the following issues

1. Wheel jerks suddenly and rapidly in the opposite direction when approaching steering lock, regardless of soft lock settings
2. FFB has noticeably less dynamic range, with forces either being overpowering or not present (this is easiest to feel when driving cars with especially grippy tires)
3. FFB graph doesn't show any useful information, the force being reported seems capped at 0.01% even when my wheel is experiencing full lock
4. When exiting a car/spawning a snowman the game will send a full-strength FFB signal to my wheel and lock it to the left until I enter a car again

I've attached some screenshots of the FFB graph while sliding a D-series around in the dirt to show how the game is reporting the FFB strength

 

Can confirm - game works great on native Linux Nvidia X11, but crashes at startup when using Wayland

 

Native Linux port won't launch for me, when i click it a black BeamNG window appears and then dissappears.
I use Kubuntu 24.10 (Wayland and KDE Plasma).

 

What happens, if you try to launch it in the terminal? What error message do you get?

 

When i try to run it in the terminal this error occurs:

 

I get the same error, but mine continues to load, so maybe that isn't the actual error causing it to crash. Maybe you could copy the whole log as a text to pastebin or something and share a link to it.

 

I'm not sure whether this is an issue on Linux only or not a feature at all: When trying to bind "Right Bumper + Left Trigger" to "parking brake" the brake is triggered only by the Trigger and does not check if the bumper has been pressed.

But the trigger is still acting as an input with a range (analogue?) which is great, eventhough the curve is not shown.

 

I'm running into some issues with the VR version. With SteamVR it immediately freezes on the dialog box that sais "VR support is early access ..."
With Monado I'm getting frames, but apparently almost no models load, it's extremely slow, and I'm only getting a new frame and server tick every 15 seconds.
All this regardless of Lowest Quality light

Edit: It freezes after this:
25.76235|D|pollEvents| OpenXR changed state from 'Unknown' to 'Idle'
25.76238|D|pollEvents| OpenXR changed state from 'Idle' to 'Ready

 

Do you absolutely need steamvr? The linux version runs openxr natively now. Just have to make sure the monado service is already started before enabling VR mode. No real need to run steam unless native linux isn't working for some reason.

 

As Windows keeps neutering itself with every update.. been experimenting with Linux more and more. i got the Binary to run on 2 distros, Mint 22 Cinnamon and Garuda DR460nized with KDE Plasma and KWin. Got mods working with a Symlink to the mods directory and using

Code:

rename 'y/A-Z/a-z/' *

to make them all lowercase.

First impressions are:
Some mods do have weird artifacts (Ibishu RUSH has some invisible parts), need to test with Windows to see if this is a VK issue. kinda forced to keep to windowed mode as i want to run 3 screens. performance kinda sucks for a 7900XT but well playable. FFB is also bit wonky, screen flickers with the cursor on the display unless I use the FPS limiter to match the refresh rate VSync does not work to stop this, cursor clicks dont always register also. Will experiment with my GPD Win Mini once i get to it.

 

im running EndeavourOS

the setting menu is detecting my spacebar as "S" and the shift,strg,alt,cap lock don't work at all

 

I originally posted this question over in the VR thread, but am wondering if it might be a linux/vulkan issue now, after speaking w/ Monado devs.

I get this error when trying to enter VR mode:

ERROR [vk_create_image_from_native] size mismatch, exported 19087728 but requires 21233664​

It's a Monado error message. The openXR runtime fails to initiate and the sim never enters VR mode. One hypothesis over there is maybe the sim is getting GPU devices confused, which would be odd given that I don't have multiple GPUs installed/enabled. Is there maybe some VRAM bookkeeping in the mix that might cause this?

 

Just updated to 0.34. Noticed osme improvements, but also noticed:
I can turn on dynamic relfection, but when leaving the graphics option menu, they immedeately disappear again...
Seems like an issue regarding the saving of settings?
Closing beamng, whiile setting was open, reopening, seems to stay on now.

Strong Window Flicker, but only when using vsync now. (at least for me)

 

It still has some kind of black frame insertion that makes the screen flicker and unplayable for me. Also, I can't lower the resolution to 1080p on my 4k TV (and in 4K it runs very poorly with my PC) I can select the resolution but it doesn't stick when I press apply.

 

For me, it's fine when I set a framelimit, that my pc can barely not reach and it's horrible with vsync,
It's what I mean by "flicker". Do you still get the black frames without vsync and a high fps limit?

 

Yes I do, and in the previous build it was only with high framerate, now I have the problem even with sub-60 fps.

 

Ok, this problem seems hard to solve, because it think it's really inconsistent from each specific case.

But to make sure, this does not happen on x11, right? - That's the one thing that I think is consistent among all the black flicker reports, it only happens on wayland.
Regarding the setting with resoution: Have you tried changing the setting and closing the game (alt f4 for example) immediately, then reopening it?

I actually said something wrong in my last comment, I get less/No flickering, when my famerate is consistently under my Monitors refresh rate!!