Linux Port – Feedback, Known Issues, and FAQ

the game doesnt seem to save graphics settings (and possibly other settings as well), upon restarting the game the graphics settings are back to defaults.

another issue i found is that third party controllers (i.e. 8bitdo sn30 pro+) arent always recongised, that controller works on Windows in Xbox mode but refuses to be recognised by the game on the native linux build.

distro: Nobara 36 (based on Fedora 36)
desktop: KDE Plasma
cpu: ryzen 5 5600G
gpu: Radeon RX6600
mesa version: 23.0-git
kernel version: 5.18.5

 

Also maps randomly crashing is a problem for me. This mainly occurs when driving from the city into the direction of the oil pumps.

I also just remembered, that enabling mods at startup doesn't work. I have to reenable them after the fact.

See here maybe.
--- Post updated ---

Already known. See top post

 

I just have to resize the window again, then it jumps into fullscreen/borderless and works, I guess it's the same issue as having to resize the window on startup
Currently I can't test things on Wayland as XWayland is kinda broken for me since kde 5.25 , but (I'll test again in a bit and report back) I don't have the stuttering issue with X11 and didn't have it with XWayland on kde 5.24

I just tested it again, and just driving the D-Series on GMv2 I get ~270-300fps on fhd standard settings, occasional frametime spikes, but not noticable
with insanely cranked settings I get ~95-120fps, but still no lags and the frametime spikes disappeared

I tested it today on my Laptop (i5-6200U/GTX950M 2GB/16GB DDR4) and I were going through the video settings from the top to the bottom and it crashed when changing the lighting quality to lowest, but it didn't when changing texture quality or anything else

 

Yeah, I tested some of that in one of my earlier posts, and concluded something similar to you. I noticed depending on the setting/order textures can also crash the game, anisotropic filtering too

 

First off, THANK YOU BEAMNG TEAM! I love that I can play Beam without using Proton, it's so much easier.
But, there are some rough spots:

Big issues first

1: Memory leak (Beam uses WAY too much memory)
2: Crash when loading certain maps (East Coast USA is the one everyone keeps talking about here)
3: Crash when changing certain graphics settings, usually shaders
4: Crash when saving car configs, caused by the screenshot for the config thumbnail (Prevented by disabling the screenshot)
5: Some maps have serious performance issues (Italy, Jungle Rock Island, Industrial Site)
6: Game doesn't load unless I move the window around after launching
7: Fullscreen and Borderless display settings don't work

Some issues other people have reported, I haven't seen for myself:

I have had no controller issues, I'm guessing that's the case since I use a basic wired Xbox controller
I have had no rendering issues, barring the game crashing from changing settings

Overall the game is very playable even in this highly experimental state. I applaud the Beam devs for their effort in this port. It made a good first impression for me. I will say a proper bugtracker would be a great addition so the community can report and manage bugs a little easier than using this forum thread.

My system:
OS: Fedora 36 Workstation Edition
GPU: AMD Radeon RX480
GPU Driver: amdgpu
CPU: AMD Ryzen 5 1600x
RAM: 16gb DDR4

 

The FFB was fixed in this last update!

Now I'm only missing the ability to use the HAT or DPAD on my G27 to move the camera. Any ideas? Oversteer (the application) shows the buttons being pressed without an issue, it's only BeamNG the one that doesn't seem to recognize it.

 

FWIW - I suspect a VRAM issue if you're using a 4GB GPU. I've also observed very poor performance on some maps, and performance collapsing beyond a certain number of AIs. This was true under Proton as well, but I think the Vulkan renderer behaves a bit differently in that regard, and not for the better when under VRAM pressure.

 

Italy worked pretty fine under proton, as far as I remember. Utah as well, but both of these maps suffer from severe lack of FPS since I am using the experimental beta. I would guess it's related to PBR, but Italy doesn't have that afaik. That would explain why utah lacks even more fps than italy does. Maybe it's because both maps have a large area of them rendered at a time, since it's a mountainous region each.

 

That may also be the reason for the crashes when loading bigger maps, as for me it always crashes at ~9GB VRAM utilization

 

I'm on 0.25.3 and I'm not getting any audio from the game. I have my USB DAC set as the only enabled audio output in pavucontrol. Arch Linux kernel 5.18.5-zen1-1-zen

https://pastebin.com/XiWZixWG

 

- I have this problem on every map right now and sometimes the sky and sometimes different parts on the screen are black (Only had this on Italy right now). Earlier this day I had this issue without the black lines. The performance was also worse earlier because of high memory usage. I don't know if I changed anything related to this :/

- The game crashes when I try to load the east coast.
With this report in the console:

I hope I translated it right from german

- up and down is mirrored with the sticks of the Dualshock 4 controller but except of this the controller works fine.


Distro: Ubuntu 20.04.4 LTS
RAM: 16GB
GPU: AMD Radeon r9 380 (4GB)
CPU: AMD Ryzen 5 3600

 

Sound works for me, even in 0.25.3, but the DPAD on my G29 doesn't
Garuda Linux, Kernel 5.18.6-zen1-1-zen

 

So I got it to launch on Steam Deck, but it took some tweaking and won't work in all circumstances.

I can't seem to get it to launch from the desktop. I just get a transparent window that does precisely nothing. However, I can get it to launch when added as a Non-Steam shortcut, but I had to disable the framerate limit in the Deck's 3 dots menu in order to keep it actually running without hanging every few seconds.

Also I have yet to figure out how to make it recognize the built in controller. This may be down to Beam or it may be on Valve's end, but I thought I'd share anyways.

Update: I tried plugging in a USB Xbox controller, and same problem. It shows up in the hardware menu but doesn't receive any input from it.

Update 2: got it to launch in desktop mode after deleting the settings folder. Controls seem to work now, at least playing windowed on the Linux desktop.

 

Does the game show up as a playback stream in pavucontrol? You don't specify which DE you're using but KDE Plasma shows the volume of currently playing streams too if you click the speaker tray icon and switch over to the "Applications" tab.

 

This is a known bug, the window has to be resized/moved before loading continues

 

What driver you use for your wheel, kernel included or new-lg4ff? Now I'm not sure if Dpad works, but I think so

 

I'm using the hid-logitech driver (at least it shows up with lsmod | grep hid)
With proton, the DPAD works, it also works in the KDE Settings app (it gets detected as 2 Axes, if I press one direction it goes to 32k or -32k for the other direction, afaik this is expected behaviour)
I'm using it in PS3 mode, as it didn't (fully) work when I tried in PS4 mode (thus, the rpm LEDs also don't work )

 

I now tried the new-lg4ff driver (still need to put the wheel in PS3 mode), nothing seems to be different (except maybe the ffbmeter works with the steering wheel leds when selecting the option in oversteer), the DPAD also is not detected in beamng (native, with proton it works)
Everything else (at least with the lg4ff driver) works perfectly fine

 

With that driver, you will play a lot of Proton/Wine games with FFB support. The kernel driver only enables constant force. With new-lg4ff, the rest of the effects are activated (spring, damper, friction...), as well as other improvements

 

I have the same problem, when doing any inputs every input reduces the fps slightly. With a mouse, it does many inputs a second (polling rate). Same with my wheel. Try spamming the t, y, and u keys (or other non-functional keys) and in the ctrl+f menu see if the fps decreases when spamming those keys. When the many inputs occur, gpuPresent increases by a lot (which is the time that [something] contributes to the delta time) for both of us, increasing the delta time (time between frames), and causing lag. I have no idea what gpuPresent is, though, besides that its a variable representing a part of the delta time.