Linux Port – Feedback, Known Issues, and FAQ

I'd try installing glibc (sudo apt install glibc)

but would be weird if that isn't installed?

 

I mean, it could be a distro without glibc.

 

Probably. The issues you encountered when using a VM are most likely due to the lack of a dedicated GPU for your VM, I don't know your setup though.

 

Figured out what caused the issue I was having, it was due to proprietary amd gpu drivers not having been properly uninstalled and leaving behind bad files, after fixing this now I can launch the game, with very buggy FFB.

Force feed back is only applied counter clock wise, which last got fixed by updating logitech drivers, the weird part is that the center point of the FFB dead zone correctly updates when turning the wheel.

This potentially feels outside the scope of what BeamNG can fix, I'm not sure if it's only fixable from the driver side or if it is simply some weird signed/unsigned FFB command errata that can be worked around.

 

you could try the new-lg4ff driver

 

The G920 and G923 Xbox version use the HID++ protocol and are not supported by new-lg4ff.

Also fftest seems to exhibit the same behavior, where selecting the spring effect leads to the wheel only applying force counter clockwise (center is defined as 0).

I'll get back when I've modified fftest to see if I can make any sense of this on the user space side.

Edit: So I've poked around for a bit and this is def a driver side issue, whatever .value is set for in autocenter mode or .center for spring mode leads to the same result, however a constant force constraint correctly applies a force in either direction (such as ffmvforce or oversteer), which means this can in theory be worked around until the underlying issue is figured out and patched.

The damper and rumble modes works as expected, periodic mode doesn't have a "center" value but still goes all the way to the left, so that's also unusable.

 

any news on os level crash report before? changing vehicle always triggers the crash

 

I'm running into this issue with the Linux port. I have recently switched to Linux Mint as Windows 11 has become unusable for me. When running the game, apon loading West Coast USA, the screen flickers and then the game locks up and keeps printing 103.92001|E|operator()| Failed to submit to graphics queue [ErrorDeviceLost] in the terminal. I'm on the latest version of Linux Mint, with 32 GB of RAM and an AMD Radeon integrated GPU on an AMD Ryzen 5 5600H 6 core CPU.

EDIT: Opening Johnson Valley quickly reveals 18.24046|E|updateDescritorSet| Missing VK resource is flooding the log. The screen flickers and the following errors flood the log, followed by a hang:

103.66942|E|operator()| Failed to submit to transfer queue [ErrorDeviceLost]
103.66943|E|operator()| Failed to submit to graphics queue [ErrorDeviceLost]
103.66966|E|operator()| Failed to submit to transfer queue [ErrorDeviceLost]
103.66966|E|operator()| Failed to submit to graphics queue [ErrorDeviceLost]
103.67288|E|operator()| Failed to submit to transfer queue [ErrorDeviceLost]
103.67290|E|operator()| Failed to submit to graphics queue [ErrorDeviceLost]

The only map that doesn't do this is Grid Small Pure. I don't know whats going on

 

BeamNG won't open at all

Fatal-ISV assert failed at file:
../../engine/graphics/backends/vk/vkDevice.cpp
Line: 583

Message: "Failed to find a suitable Vulkan device"
Neofetch:
OS: LMDE 5 (elsie) x86_64
Kernel: 5.10.0-23-amd64
Uptime: 7 days, 14 hours, 32 mins
Shell: bash 5.1.4
Resolution: 1366x768
DE: Cinnamon 5.6.8
WM: Mutter (Muffin)
WM Theme: Linux Mint (Mint-Y)
Terminal: gnome-terminal
CPU: AMD A8-4500M APU (4) @ 1.900GHz
GPU: AMD ATI Radeon HD 7640G
Memory: 7397MiB

 

The 7640G does not support the Vulkan API unfortunately.

 

There is a way to get those to work. I've attached a small demonstration.

This requires some finagling from the end user though, and those entries will also be visible to Windows users.

• Launch options for the game need to be set to "Windows" not "Linux", since proton uses the Windows depot
• It is required that the user switches compatibility mode from Proton to "Linux Native" which is a modification of Steam-Play-None, changing this line from "linux" to "windows" in order to launch the linux native binary and vice versa

As you can see rich presence is working, as well as playtime tracking, which is all I wanted to achieve, plus it looks much cleaner this way

It would probably just be easier to create a linux native depot though.
I heard that valve has the ability to override whether the game should launch using proton or the native binaries by default.

 

So is there any other way for me to be able to play BeamNG natively, like maybe a port to OpenGL? Sorry if I'm asking too much.

 

Log attached.

 

Alright I was tired of the vram issues I had, so I just went a bought an RX580 8GiB, and also changed the CPU for a Xeon E5-2640 V4.

To my surprise, I went from barely being able to play in low settings with the gtx 1060 to now medium settings and the game still eats 7GiB of vram, when did this game suddenly started using so much vram? omg.

Also I was getting really bad cpu performance with traffic vehicles, the average framerate would sometimes dip down to 30 fps. Turns out I needed to change the CPU governor from Schedutil to Performance, massive difference, now it is always above 60 fps.

Here is a recording I did showing the difference:


First I do a highway run on schedutil and then I do it again with Performance.

 

I think that's just the Linux version.

 

(Still needs more testing)
just now I plugged in my wheel when the game was running and it caused a GPU reset, making the whole system unusable until a reboot

I don't think there's any useful information here, but these are the "most relevant" lines in the system journal:

Code:

Jul 04 18:19:37 JoLi-HauptPC-archlinux kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=10117877, emitted seq=10117879
Jul 04 18:19:37 JoLi-HauptPC-archlinux kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process BeamNG.drive.x6 pid 20653 thread BeamNG.drive.x6 pid 20710

 

https://gitlab.freedesktop.org/drm/amd/-/issues/1974
that's a mesa problem as far as I could research it.

 

oh sh!t... thanks for doing my job...
seemed like such a casual error message to me that i thought it couldn't possibly have been a bug, but i guess searching for errors is always a mandatory step...

 

I hit that same issue on a 5700 XT so yeah I am aware of that.

 

The Linux port (and the Windows Vulkan version) still crashes the PC for me while loading almost any map.