Linux Port – Feedback, Known Issues, and FAQ

I thought I had nouveau due to some issues, but it turns out I'm using the proprietary ones.

 

Just installed BeamNG on my deck to try the mod out and I think I'm settling on the conclusion this is an issue with LUA on Arch due to it being a rolling release it causes issues as the Steam Deck has 0 issues running the same mod on a fresh install. Included is the log from my Steam Deck to confirm there is no issue on an older release. I am on SteamOS 3.8.12 on kernel 6.16.12-neptune.

 

There's some issues on this new update, first of all, the steam controller stopped working completely, I can see the game recognizing the steam controller but it acts as a mouse and keyboard instead of doing what it's supposed to, and yes I tried resetting my config even tho it worked perfectly fine on 0.38.
Yall said you switched the game to wayland, and I don't really know how this is supposed to work atm as steam still runs in xwayland, and this causes a lot of problems, like the game constantly flashing if you play it in full screen to the point that it's actually unplayable and the steam overlay being completely borked, and at least for me, using "SDL_VIDEODRIVER=x11" does nothing, and just in case, I'm playing from NixOS 26.05 on kde wayland

 

This looks like it's a side effect of going to Wayland. Because the Steam Input layer relies on the overlay(at least that's how I believe it works) and the overlay doesn't work in Wayland yet, you'll either need to set `SDL_VIDEODRIVER=x11`, use gamescope, or switch the Steam Controller into the gamepad mode by holding the menu button for 2+ seconds though this is limited to a basic gamepad layout as far as I know. In the past I found that using gamescope helped stop any of the flickering, I am not sure if it will help here because I don't exhibit this flickering any longer.

 

The issue you’ve noticed:
Since updated to 0.39, BeamNG.drive doesn't see my Sony DualSense controller, on 0.38 it was fine.
Also, sometimes, BeamNG detects the controller, but it doesn't register any button or stick movement.


This happens when:
Sony DualSense Controller

My specs are:
Fedora Linux 44 (Workstation Edition) x86_64
Kernel: Linux 7.1.4-204.fc44.x86_64
DE: GNOME 50.3 on Wayland
CPU: AMD Ryzen 5 5600X
GPU: AMD Radeon RX 6600

• Driver: amdgpu/radv
• Mesa 26.1.5

RAM: 64GB


Logs:
https://cringe.rf.gd/uploads/beamng.log

 

"SDL_VIDEODRIVER=x11" does nothing for me sadly

 

full launch option is: SDL_VIDEODRIVER=x11 %command%
works fine for me, steam overlay and steam input work

 

Force Feedback is broken after the latest update, using a Logictech G29 and the hid_logitech_new drivers, it now only works when using the Windows version through Proton

 

Currently my 'letter' keys, so not arrow keys and numpad etc. do not work unless i hold down the caps lock key (not toggle, literally held down) or do combination keybinds like ctrl + n or alt + n but not shift + n

I have tested this in the 'test devices' menu and in-game. oddly enough holding shift does not work either. The following is what shows up in the test devices menu

If i first hold caps lock, then hold a key (so it registers) and then let go of caps lock while holding said key, it stills shows up as being held. While in this state i still cannot press another letter without caps lock but letting go does actually let go of the key

And also if i hold down ctrl or shift (shift also requires caps lock being pressed due to previous bug) + letter and then let go of ctrl (or shift), then letter, it gets stuck while letting me use that letter again in another bind??????
I disabled steam input but it shouldn't affect anything as wayland prevents it anyway.

 

I found out that my 8bitdo Ultimate 2 controller is not recognized at all when launched via Steam... Which seems to be launching the game via Proton. If I launch via the Linux binary, it recognizes. What was the launch property on Steam, again? ./BinLinux/BeamNG.drive.x64 ?

 

You don't actually need any launch argument anymore. They changed it so that as long as your compatibility tool manual selection for the game is unchecked, it will default to the native version

 

I guess I do, since the launch via Steam calls itself “steam runtime” instead of “Fedora 44” and it doesn't recognize my controller.

 

Since native version defaults to wayland now, steam input doesnt work. I have the same controller. Either switch it to xinput mode or switch to xwayland via launch option SDL_VIDEODRIVER=x11 %command%

 

The native version doesn't unlock the new achievements, although even through proton I couldn't unlock the performance index achievements

 

I guess I do, since

Forcing x11 works, but 1) it reverts to the issue I was having, that is, any interface element that's not VUE is so small I can't read (like the steam overlay and the CTRL+F metrics), and 2) this is obviously an issue and should work with wayland, since other games are running with Wayland (namely all my emulators) and the controller works.

EDIT: Also forcing x11 tanks my FPS. So I either have to use the keyboard and play with decent FPS, or suck up 20 FPS with no cars other than my own to use my controller.

 

Had an issue with linux native 0.39 not starting at all with some arbitrary application failed error message. Turns out when using the snap version of steam some game file paths included double forward slashes and beamng couldn't find certain files. I installed the deb version of steam and got it running without an issue.

 

Hello, i think some of you in the office have the steam deck, because you even made dedicated steam deck preset. What should be the expected performance? Im getting between 30-40 FPS on west coast map. GPU on 100% and CPU around 50-60% on all cores. I know steam deck cannot handle modern rendering technique, but i was expecting less of a performance hit. Im running native version (no proton enabled).

 

I just confirmed that my 8bitdo Ultimate 2 controller is not recognized by the game when:

1) launched via Steam in wayland
2) launched via Steam with ./BinLinux/BeamNG.drive.x64 in wayland

It is recognized when:

1) launched via binary¹
2) launched via Steam in X11²

¹L4, R4, PL and PR are not recognized, even though I configured via Steam for them to be button chords.
²L4, R4, PL and PR are recognized with my custom configurations.

This is my official bug report.

Note: Controller is connected via Bluetooth in all tests. 2,4 GHz works in all situations, but without macros. It wasn't like this in 0.38.

 

Version 0.39.1 crashes when changing the lighting quality option up and down a few times when running the native linux version with this steam launch option: SDL_VIDEODRIVER=x11 %command%
Running native without the launch option fixes the crashing, but it causes the steam overlay to stop working and my steam controller (original version) to not work and isn't recognized by the game.
Running the windows version with DX12 through proton experimental also crashes when changing lighting quality.

I experienced the crashes when loaded in a map, but don't when in the main menu.

Specs:
OS - Bazzite 44 with KDE Plasma, Kernel version 7.1.3-ogc5.1.fc44.x86_64 (64-bit)
Monitor - 1440p 165hz HDR Disabled
GPU - RX 7700xt (12gb)
CPU - Ryzen 5 5600x
MEM - 32GB DDR4 3600 CL18
Motherboard chipset - B550
Game is installed on a M.2 gen3 SSD

I Included 4 .Log files.