Linux Port – Feedback, Known Issues, and FAQ

0.35 runs fine with the most recent mesa drivers I have access to (arch, 25.1.5), the crashes seem to be caused by the 0.36 update.

Stack trace from Mesa 25.1.4:

 

Same issue sadly. Crashes as soon as I ALT+TAB.

I am running a fresh install of Arch
- Ryzen 3600x
- 16GBs RAM
- RX6800xt

 

Good to know. I was also able to downgrade Mesa to 25.0.2 and it was still crashing with 0.36.4, so that should confirm that the game update broke something.

Yeah it's the same for me as well. It might work for a while, but will crash, if alt-tabbing or even if I open the menu and go to browse vehicles. One working solution is to load the game with AMDVLK drivers. But I'm having trouble having RADV and AMDVLK installed at the same time. AMDVLK will insert itself as the default driver, so if I want to use mesa for other games on Steam, i could add one of these lines to the games launch options:

Code:

AMD_VULKAN_ICD=radv %command%

or

Code:

VK_DRIVER_FILES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%

or

Code:

VK_ADD_DRIVER_FILES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%

The problem is, on Fedora 42 at least, that AMDVLK will still be the driver that the game loads. The only solution I have found so far is to move the actual amdvlk64.so and amd_icd64.json away from their installation directories.
Just too much of a hassle.

 

What i did was add

Code:

AMD_VULKAN_ICD=RADV

to the /etc/environment file, then add

Code:

AMD_VULKAN_ICD=AMDVLK

to the game's environment variables

 

Thanks for the suggestion. What ended up working for me was to add the

Code:

AMD_VULKAN_ICD=RADV

to the /etc/environment file and then add

Code:

VK_DRIVER_FILES=/etc/vulkan/icd.d/amd_icd64.json

to the game's environment variables. And more specifically, in the .desktop file of the game. Can't get this method working, when adding the native Linux version of the game to Steam as a non-steam game, though.

On Fedora, it installs the amd_icd64.json file in /etc/vulkan/icd.d instead of /usr/share/vulkan/icd.d directory, where the rest of the .json files are located. Don't know, if that's the reason why AMD_VULKAN_ICD=AMDVLK does not work, when put to the game's environment variables.

 

This is the solution I am using and also posted here, also works fine performance wise.

 

so on the steam deck the desktop mode loads up the maps fine but when i enter gaming mode and do the same it always gets stuck on loading forest any idea why? edit fixed it for some reason i had to factory reset it then it worked

 

Went back to windows, simply cause linux had stuttering issues in Linux.

 

Let me ask you, what exactly is the reason for this behavior? If this is a driver error and an implicit Vulkan behavior, how will this be fixed in the game code? This should be fixed only in the driver. And also why does this bug not happen again in Wayland-based systems? Interested in technical details

 

I also have one ... a sensitive issue regarding performance...

Why can performance be lower in case-sensitive file systems (mostly Linux-based OSS use case-sensitive FS)?

Of course, I'm an ordinary user, not a programmer. But I have a couple of ideas for this...
Please rate them...
1. Remove uppercase characters from the specification. It will take quite a lot of time to transition and adapt. It may take several releases of the game before the ban is fully implemented. Yes, the oldest mods that are abandoned won't work. But authors who keep track of their mods and new modmakers will be required to comply with the new requirement.
2. Switch to a single API for interacting with files and folders on Windows and Linux. Let's say both use the SDL3 library for interaction.
3. Rewrite the compatibility layer (and transformations) from a high-level language to a low-level one and manually optimize it. For example, take an Assembler
How would you rate the ideas from a professional point of view?

 

After some quick testing with a git-version of the mesa-driver, it seems to be working now. Tried alt-tabbing and "vigorously" browsing the menus and it does not crash anymore. Good find!

 

How do you remap the mesh road node placement key in the BeamNG editor? I can't seem to map it to anything other than ALT+Left Click - the keybinding to move a window around in my window manager.

 

Hello,

I would like to launch the game, but it keeps crashing:

Thread 1 "BeamNG.drive.x6" received signal SIGTRAP, Trace/breakpoint trap.
0x00007fffed119869 in ?? () from libcef.so

I use an NVIDIA GPU with proprietary drivers.


Any idea how to fix this?

#0 0x00007f957ab19869 n/a (/mnt/76561DD3561D94C9/SteamLibrary/steamapps/common/BeamNG.drive/BinLinux/libcef.so + 0x7319869)
#1 0x00007f9579e5cb46 n/a (/mnt/76561DD3561D94C9/SteamLibrary/steamapps/common/BeamNG.drive/BinLinux/libcef.so + 0x665cb46)
#2 0x00007f9579e5b2e9 n/a (/mnt/76561DD3561D94C9/SteamLibrary/steamapps/common/BeamNG.drive/BinLinux/libcef.so + 0x665b2e9)
#3 0x00007f957614f47a n/a (/mnt/76561DD3561D94C9/SteamLibrary/steamapps/common/BeamNG.drive/BinLinux/libcef.so + 0x294f47a)
#4 0x00007f957614f26f n/a (/mnt/76561DD3561D94C9/SteamLibrary/steamapps/common/BeamNG.drive/BinLinux/libcef.so + 0x294f26f)
#5 0x00007f9576139a45 n/a (/mnt/76561DD3561D94C9/SteamLibrary/steamapps/common/BeamNG.drive/BinLinux/libcef.so + 0x2939a45)
#6 0x00007f9576139744 n/a (/mnt/76561DD3561D94C9/SteamLibrary/steamapps/common/BeamNG.drive/BinLinux/libcef.so + 0x2939744)
#7 0x00007f95760b37ca cef_initialize (/mnt/76561DD3561D94C9/SteamLibrary/steamapps/common/BeamNG.drive/BinLinux/libcef.so + 0x28b37ca)
#8 0x0000563187304ec2 n/a (BeamNG.drive.x64 + 0x22bfec2)
#9 0x00005631866b316b n/a (BeamNG.drive.x64 + 0x166e16b)
#10 0x0000563185e18af7 n/a (BeamNG.drive.x64 + 0xdd3af7)
#11 0x000056318555d443 n/a (BeamNG.drive.x64 + 0x518443)
#12 0x00007f957302a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)
#13 0x00007f957302a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)
#14 0x00005631855c5155 _start (BeamNG.drive.x64 + 0x580155)

 

Have any of you guys been able to get SteamVR working with the native version of Linux? For me, It works with Monado, but not with SteamVR.
It's able to show one frame in my headset and then the game hangs. I don't see a crash reporter at that point or any more log entries.

Weird thing is that when I enable VR mode in the game and I have my headset on the table, ie. in idle-mode, the game does not hang, but when I put the headset on, that's when the game stops responding.

Started the game in the terminal with "-gfx vk debug" option added.

Pastebin for the log:
https://pastebin.com/WwXsFYBy

 

That pr was merged and released with Mesa `25.1.7`, I got the update and I've been playing for half and hour and I'm proud to state this issue is now no longer occurring (my game is no longer crashing on the RADV vulkan implementation).

Thank you so much for chasing this! ❤️