1. Trouble with the game?
    Try the troubleshooter!

    Dismiss Notice

  2. Issues with the game?
    Check the Known Issues list before reporting!

    Dismiss Notice

  3. Before reporting issues or bugs, please check the up-to-date Bug Reporting Thread for the current version.
    0.39 Bug Reporting thread
    Solutions and more information may already be available.

Support Troubleshooter Known Issues Bug reporting

Linux Port – Feedback, Known Issues, and FAQ

Discussion in 'Troubleshooting: Bugs, Questions and Support' started by Car_Killer, Jun 13, 2022.

Page 1 of 66
  1. Car_Killer

    Car_Killer
    Expand Collapse
    Technical Artist / QA
    BeamNG Team

    Joined:
    Sep 24, 2013
    Messages:
    1,765
    Hello all,

    This thread is for feedback and issue reports related to the native Linux version of BeamNG.drive.

    Native Linux support was first introduced experimentally in version 0.25. You can read the original announcement here:
    https://www.beamng.com/game/news/announce/experimental-linux-support/

    The Linux version is still a work in progress. Compatibility may vary depending on the distribution, kernel, GPU driver, desktop environment, display server, compositor, and hardware configuration. We do not provide full official support for it, but we would still like to hear your feedback in this thread.

    The native Linux version is now the default on Steam. If you previously selected Proton or another compatibility tool, open the game’s Steam properties and disable “Force the use of a specific Steam Play compatibility tool.” This allows Steam to launch the native Linux version.

    Documentation page:
    https://documentation.beamng.com/support/troubleshooting/steamdeck_linux/

    Please review the guidelines below before posting. Posts that do not follow the guidelines may be removed or merged.



    Posting guidelines

    Before posting, please make sure to:
    • Update your distribution and kernel.
    • Update your GPU drivers.
    • If you use an NVIDIA GPU, install the proprietary NVIDIA driver. Nouveau and NVK are not supported.
    • If you use AMD or Intel graphics, make sure Mesa and the Vulkan driver packages are up to date.
    • If you use Steam Deck, Steam Machine, or Steam Frame, make sure SteamOS and the device firmware are up to date.
    • Update the game to the latest version, including hotfixes.
    • Remove custom Steam launch options.
    • Disable third-party overlays, recording tools, ReShade, and other software that installs Vulkan layers.
    • Disable all mods and test again.
    • If you have access to Windows, check whether the issue also occurs there using Vulkan.
    • If the problem is related to a mod, test with only that mod enabled before reporting.

    When reporting:
    • Check whether the issue has already been reported. If you have additional information, reply to the existing report instead of creating a duplicate.
    • Clearly describe what is happening and when it happens.
    • Describe how to reproduce the issue, if possible.
    • Attach screenshots or video for visual issues.
    • Attach beamng.log whenever possible, especially for crashes, startup issues, or rendering errors.
    • If the issue occurs only at a specific place on a map, press ALT+O and share the generated URL.

    Reporting template:

    The issue you’ve noticed:
    (Describe what is happening. Attach a screenshot or video if useful.)

    This happens when:
    (Describe how to trigger the issue, if possible. This helps us reproduce it.)

    My specs are:
    (Include distribution and version, kernel version, CPU, GPU, RAM, Mesa or NVIDIA driver version, desktop environment, compositor, X11 or Wayland, and whether this is Steam hardware.)

    Logs:
    (Attach beamng.log whenever possible.)



    Known Issues
    (as of 29.07.2026)

    • The native Linux version shares the known issues of the Vulkan renderer.
    • The BeamNG.drive Launcher and some launcher support tools are not currently available.
    • HDR may not work correctly with some Linux compositors such as SteamOS GameMode/Gamescope.



    FAQ

    1. How do I launch the native Linux version?
    Launch the game normally through Steam on Linux.
    Open Steam → BeamNG.drive → Properties → Compatibility and make sure Force the use of a specific Steam Play compatibility tool is disabled.
    If this option is enabled and a Proton version is selected, Steam will run the Windows version instead.

    2. Where are my settings, mods, logs, and user files located?
    The native Linux user folder is located at:
    ${XDG_DATA_HOME:-$HOME/.local/share}/BeamNG/BeamNG.drive/current
    In most cases, this is:
    ~/.local/share/BeamNG/BeamNG.drive/current
    The current session log is beamng.log. Numbered logs such as beamng.1.log are from earlier sessions.
    The Proton and native Linux versions use different user folder locations. If your settings or mods appear to be missing after switching to native Linux, see the documentation page for migration instructions.

    3. Which graphics API does the native Linux version use?
    The native Linux version uses Vulkan exclusively. It requires Vulkan 1.3 and all Vulkan features used by the renderer.
    Vulkan driver quality is therefore very important. If you experience rendering issues, startup crashes, blurry textures, or performance problems, make sure your GPU driver and system packages are up to date.

    4. Which GPU drivers should I use?
    • NVIDIA: Use the official proprietary NVIDIA driver. Nouveau and NVK are not supported.
    • Modern AMD: Use a recent Mesa version with the RADV Vulkan driver. Avoid AMDVLK and AMDGPU-PRO on modern cards.
    • Older AMD GCN 1 and 2: These GPUs require additional kernel configuration and AMDVLK because RADV disables sparse residency support on them. See the documentation page for details.
    • Intel: Use a recent Mesa version with the ANV Vulkan driver. Many older Intel integrated GPUs do not support the required Vulkan 1.3 features.
    • Steam Deck, Steam Machine, and Steam Frame: Keep SteamOS and the device firmware updated.
    Outdated or incomplete Vulkan drivers are among the most common causes of startup and rendering issues.

    5. Can I use mods on the Linux version?
    Yes. In most cases, mods should work the same as on Windows.
    However, Linux filesystems are usually case-sensitive. Mods with incorrect file or folder capitalization may fail to load textures, materials, sounds, scripts, or other assets even if they work on Windows.
    Always test without mods before reporting a Linux issue.

    6. What is the difference between the native Linux and Proton versions?
    The native Linux version runs directly on Linux and uses the Vulkan renderer.
    The Proton version runs the Windows build through Proton/Wine. It uses additional compatibility layers and may have different performance, compatibility, user-folder behavior, and platform-specific issues.
    The native version avoids the Windows compatibility layer, but compatibility still depends heavily on Vulkan drivers, distribution configuration, desktop environment, compositor, and hardware.

    7. Does the Linux version support texture streaming?
    Yes. The native Linux version uses Vulkan, which supports texture streaming.
    Texture streaming loads texture mip levels on demand instead of keeping every texture at full resolution in VRAM. This reduces VRAM pressure and improves scalability in large scenes.

    8. Does Linux support VR?
    VR support on Linux depends on the OpenXR runtime, GPU driver, headset software, compositor, and required Vulkan and OpenXR extensions.
    VR requires at least 8 GB of VRAM, with 10 GB or more recommended.
    If reporting a VR-related issue, include:
    • Headset model.
    • OpenXR runtime.
    • GPU and driver version.
    • Distribution and kernel version.
    • Desktop environment and compositor.
    • Whether SteamVR, Monado, or another runtime is used.
    • beamng.log.

    9. Does the native Linux version support HDR?
    HDR support on Linux is currently experimental and depends on the entire display stack, including:
    • GPU and Vulkan driver.
    • Desktop environment and compositor.
    • Wayland or X11 session.
    • Gamescope configuration, if used.
    • Display capabilities and connection type.
    • Support for the required Vulkan HDR extensions.
    HDR may currently be broken or unreliable on some SteamOS/Gamescope and desktop Linux configurations.
    If HDR produces incorrect colors, a black screen, washed-out output, or no visible HDR effect, disable HDR and include the following in your report:
    • Display model and connection type.
    • Distribution and version.
    • GPU and driver version.
    • Desktop environment and compositor.
    • Whether you use X11, Wayland, or Gamescope.
    • Whether system-level HDR is enabled.
    • Screenshots or photos of the issue.
    • beamng.log.

    10. The game behaves differently than on Windows. Is that expected?
    Some differences are expected. The native version uses a different platform layer and relies on Linux Vulkan drivers, filesystem behavior, input handling, audio services, windowing and compositor behavior, and Steam integration.
    If you can reproduce the same issue on Windows using Vulkan, mention that in your report. This may indicate a Vulkan renderer issue rather than a Linux-specific issue.

    11. How do I run Banana Benchmark on Linux?
    Open the BeamNG.drive installation folder, enter the BinLinux directory, and run:
    ./banana-bench.x64.sh
    from a terminal emulator.

    12. What information is most useful when reporting Linux issues?
    Please include:
    • beamng.log.
    • Distribution name and version.
    • Kernel version.
    • CPU.
    • GPU.
    • RAM.
    • Mesa version and Vulkan driver, or NVIDIA driver version.
    • Desktop environment and compositor.
    • Whether you use X11, Wayland, or Gamescope.
    • Whether this is a Steam Deck, Steam Machine, Steam Frame, or other Steam hardware.
    • Whether the native Linux or Proton version is running.
    • Steps to reproduce.
    • Screenshots or video for visual issues.
    • ALT+O location URL if the issue is map- or location-specific.
     
    #1 Car_Killer, Jun 13, 2022
    Last edited: Jul 29, 2026 at 12:25 PM
    • Like Like x 17
  2. hacker420

    hacker420
    Expand Collapse

    Joined:
    Dec 29, 2017
    Messages:
    1,155
    I can't seem to start the binaries, when I try to run them from the terminal this appears: Failed to init bngenv: Failed to mount game path in vfs
    My specs: Artix Linux, kernel 5.18.2, RX 5700XT and a Ryzen 7 3700X, Mesa version: 22.1.1
     
    #2 hacker420, Jun 15, 2022
    • Like Like x 1
  3. myogg

    myogg
    Expand Collapse

    Joined:
    Aug 31, 2013
    Messages:
    166
    Thank you so much for adding this!
     
    #3 myogg, Jun 15, 2022
    • Like Like x 3
    • Agree Agree x 3
  4. Car_Killer

    Car_Killer
    Expand Collapse
    Technical Artist / QA
    BeamNG Team

    Joined:
    Sep 24, 2013
    Messages:
    1,765
    Unfortunately, I cannot reproduce the issue:/
     
    #4 Car_Killer, Jun 15, 2022
    • Like Like x 1
  5. LaserPG.ride

    LaserPG.ride
    Expand Collapse

    Joined:
    Feb 27, 2022
    Messages:
    9
    Using OpenSUSE Tumbleweed with /home on XFS, Kernel 5.18.2, Mesa 22.1.1, KDE Plasma 5.25 on X11.

    Intel i7-12700K with 32GB DDR4, UHD770+Radeon RX480; the game does use the discrete GPU after starting.

    Overall graphical performance and menu responsiveness appears to be very low compared to the Windows version via Proton.

    The game appears to stutter for long periods if I hover and keep moving the mouse pointer over the BeamNG.drive window.

    Compared to the Windows Steam version the joypad (Dual Shock 4) does not seem to be detected.

    Below is a performance graph from the game with this version (right click and open in new tab to see the full version). The spikes are when I tried moving the mouse on the screen.

    upload_2022-6-15_15-24-26.png
     
    #5 LaserPG.ride, Jun 15, 2022
    Last edited: Jun 15, 2022
    • Like Like x 2
    • Agree Agree x 1
  6. grekiki

    grekiki
    Expand Collapse

    Joined:
    Jun 15, 2022
    Messages:
    3
    Works fine here aside from no sound. R5 1600x + gtx 1060 3GB on Ubuntu 20.04 LTS.
    (edit: Program wants to send a crash report if I close it by pressing x on top right of the window, aka normal closing method)
    (edit 2: time to try to get beamngpy working)
     
    #6 grekiki, Jun 15, 2022
    Last edited: Jun 15, 2022
    • Like Like x 1
    • Agree Agree x 1
  7. Friz64

    Friz64
    Expand Collapse

    Joined:
    Jun 15, 2022
    Messages:
    1
    The game works fine, even with my steering wheel, except for the already mentioned issues, and the fact that
    - enabling full screen will make the game hang (either borderless or normal fullscreen) (GNOME/Wayland through XWayland)
    - enabling VSync will make the game hang
    - applying graphics presets while in-game will sometimes hang/crash the game

    AMD RX 580, vulkan-radeon 22.1.1-2, Arch Linux
    Huge thanks to the BeamNG devs for this effort!
     
    #7 Friz64, Jun 15, 2022
    • Like Like x 2
  8. waschbaer2004

    waschbaer2004
    Expand Collapse

    Joined:
    Oct 9, 2021
    Messages:
    3
    HUGE Thank you for doing this! After loading for some years it works really great. Cars are loading very fast though. As mentioned, i have no Sound.

    Kubuntu 22.04 + AMD Ryzen 7 2700X + GTX 1660 Super. Also using the Nvidia Driver 510. Using X Window system.
     
    #8 waschbaer2004, Jun 15, 2022
    • Like Like x 2
  9. hacker420

    hacker420
    Expand Collapse

    Joined:
    Dec 29, 2017
    Messages:
    1,155
    Fixed that issue by removing everything from the game folder aside from levels and vehicles, then validated the game files. Now the game works perfectly, finally I can run traffic on high settings at 60 FPS :p
    --- Post updated ---
    Btw, is there some way to tell Steam to launch the Linux binaries by default?
     
    #9 hacker420, Jun 15, 2022
    • Like Like x 2
  10. Car_Killer

    Car_Killer
    Expand Collapse
    Technical Artist / QA
    BeamNG Team

    Joined:
    Sep 24, 2013
    Messages:
    1,765
    You can add binary from binlinux as non steam game inside steam library
     
    #10 Car_Killer, Jun 15, 2022
    • Agree Agree x 1
  11. hacker420

    hacker420
    Expand Collapse

    Joined:
    Dec 29, 2017
    Messages:
    1,155
    Screenshotat2022-06-1517-59-46.png
    This happens when I load Italy, also is it supposed to eat 16 GB of RAM?
     
    #11 hacker420, Jun 15, 2022
    • Like Like x 1
    • Agree Agree x 1
  12. grekiki

    grekiki
    Expand Collapse

    Joined:
    Jun 15, 2022
    Messages:
    3
    Alright you devs are awesome! Beamngpy is working on linux
     

    Attached Files:

    • Screenshotfrom2022-06-1518-34-24.png
    #12 grekiki, Jun 15, 2022
    • Like Like x 1
    • Agree Agree x 1
  13. Car_Killer

    Car_Killer
    Expand Collapse
    Technical Artist / QA
    BeamNG Team

    Joined:
    Sep 24, 2013
    Messages:
    1,765
    Sound issue will be fixed in the next hotfix :)
     
    #13 Car_Killer, Jun 15, 2022
    • Like Like x 10
  14. Beans_On_Butter

    Beans_On_Butter
    Expand Collapse

    Joined:
    Jun 15, 2022
    Messages:
    8
    The game gets stuck on startup after "2.31946|D|GELua.core_settings_graphic.graphic| Applying graphic settings: \\.\DISPLAY1, Window, 1280 x 720 60 Hz" in terminal and only continues to load after dragging the window.

    Loading any map initially caused black environments with the only textures working being the UI and sky box, but it froze as soon as they are visible. This seemed to fix itself after a few relaunches. I only got a screenshot, as I forgot to copy the log file.
    The garage works, light are flickering and it gets into a long error loop when selecting test drive. This also happened when spawning a new car. See log file for the error.

    Dualsense input works, not yet tested with my Dualshock 3 or Logitech G29.

    System:
    Manjaro
    Kernel 5.18.0-1-rt11-MANJARO
    CPU AMD Ryzen 7 4700U
    iGPU with mesa 22.1.1-2
    12 GB of ram, 12 GB of swap partition
    Running on normal preset, dynamic reflection, anti aliasing, and depth of field disabled, and in windowed mode.
     

    Attached Files:

    #14 Beans_On_Butter, Jun 15, 2022
    • Like Like x 2
    • Agree Agree x 1
  15. asu

    asu
    Expand Collapse

    Joined:
    Jun 15, 2022
    Messages:
    5
    Thanks a lot for the effort!

    I also get the black screen issue, which gets resolved when I resize the window. A few things to note additionally:
    • When this happens, on my KDE Plasma Wayland setup, BeamNG and Xwayland CPU usage is rather high (~60% each). Running the game under gdb and breaking once in a while when the freeze occurs almost consistently leads to random Xorg stuff at the top of the stack. There is always lua_pcall in the call stack when I break but there's nothing else interesting I can find. My guess is that the game loops on some windowing code and some graphics stuff initialization happens to get done after triggering a resize event for whatever reason.
    • The same issue occurs with gamescope on my system. There are a few additional logs coming from gamescope itself that may be of use, but those may be irrelevant:
      Code:
      wlserver: [types/wlr_surface.c:741] New wlr_surface 0x55abd4c49f80 (res 0x55abd4c6be70) 
xwm: error 2: BadValue (integer parameter out of range for operation) request 138 minor 31 serial 1020 
xwm: error 2: BadValue (integer parameter out of range for operation) request 138 minor 31 serial 1023 
xwm: error 141: 141 request 138 minor 32 serial 1037 
xwm: error 141: 141 request 138 minor 32 serial 1040
    I don't have a new issue to report (yet) but I can reproduce the black stripe issue (which also happens on the Automation map in my testing, and a few others) and the lack of audio, but that seems to be expected.

    I use arch (btw) on Wayland (KWin), on a ryzen 9 3900X + RX 580 system. Mesa is up to date (22.1.1).
    --- Post updated ---
    I moved the game directory in a case insensitive ZFS dataset, but I still get the ingame warning.
    Is this because some other directory (e.g. my home directory) lives on a case sensitive filesystem, or is it because the fs case sensitivity check is too rudimentary? Is the performance penalty still a worry in such a case?
    EDIT: As it turns out, I didn't pay enough attention to the performance diagnostics menu. The game checks for case sensitivity separately for the game directory and the user directory.
    That being said, it might be good to document how important this is for the user directory vs the game directory as AFAIK it is not unusual for linux users to install games on a NTFS partition for instance (for dual-boot purposes).
     
    #15 asu, Jun 15, 2022
    Last edited: Jun 15, 2022
    • Agree Agree x 1
  16. parkerlreed

    parkerlreed
    Expand Collapse

    Joined:
    Sep 9, 2016
    Messages:
    6
    The issue you’ve noticed:
    Missing VK resource spammed during gameplay. Otherwise it seems to run fine.

    This happens when:
    Whenever in game

    My specs are:
    Ryzen 3700U
    Built in Vega
    Arch Linux
    5.18.3
    Mesa RADV Vulkan 22.1.1

    EDIT: This appears to only happen on the lowest preset.

    EDIT2: Narrowed it down to Lighting setting being on lowest causing the missing VK resource.
     
    #16 parkerlreed, Jun 15, 2022
    Last edited: Jun 15, 2022
    • Like Like x 1
    • Agree Agree x 1
  17. Solitude

    Solitude
    Expand Collapse

    Joined:
    May 29, 2021
    Messages:
    3
    The map loading is extremely long, maybe x20 compared to windows/directx version.

    also, devs, you're gonna hit more issues related to peoples setups, because they are running outside steam's runtime.

    game writes its data to `$HOME/.local/share/BeamNG.drive`, i hope it actually uses `XDG_DATA_HOME`.
     
    #17 Solitude, Jun 15, 2022
    • Like Like x 1
    • Agree Agree x 1
  18. asu

    asu
    Expand Collapse

    Joined:
    Jun 15, 2022
    Messages:
    5
    Does this happen even if you try to play a map you have tried on linux again? This may be normal, as I believe there is some per-map preprocessing going on. I observed long map loading and maxxed out CPU usage only on the first launch on a map.
     
    #18 asu, Jun 15, 2022
    • Like Like x 1
  19. Solitude

    Solitude
    Expand Collapse

    Joined:
    May 29, 2021
    Messages:
    3
    indeed, repeated loading was much faster.
     
    #19 Solitude, Jun 15, 2022
    • Agree Agree x 1
  20. JoLi

    JoLi
    Expand Collapse

    Joined:
    Oct 12, 2020
    Messages:
    252
    Thanks for resolving the audio Issue in the next hotfix!
    Apart from that, most things work fine, except the "bug" with having to move the window to get it to load (when going into FullScreen, the same is needed)

    btw have you done something to make the UI faster? I mean it could still be faster like the Web UI, but damn it's a lot better than on 0.24 I feel like
     
    #20 JoLi, Jun 16, 2022
    • Like Like x 2
(You must log in or sign up to post here.)
Page 1 of 66
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...
    Dismiss Notice