Linux Port – Feedback, Known Issues, and FAQ

I have the same problem with my G27.

The native version has FFB but the DPAD doesn't work (so I can't move the camera or menus). Also, the wheel is not recognized as such and I need to add all the buttons to the game.

The Proton version (Vulkan) has a working DPAD and the G27 preset added (so I only need to add some custom keys) but the FFB doesn't work.

I have Oversteer and new-lg4ff installed.

If someone knows how to make the FFB work on the Proton version, that would be much appreciated.

 

Try another Proton Version, or try with Lutris and Wine. I think the last version it didn't work is Proton 6.3-8 (I suggest GE-Proton (use ProtonUP-Qt for easy installation))

 

I roamed around all the maps (except Italy -- see below) in the base game (free roaming). 1080p30 was achieved pretty much everywhere (neat!).
Here are my ideas for a potato-PC friendly game (or, if you prefer: Optimization ideas from a guy who can notice the non-optimized bits of the game a bit too much with his 3.2ghz quad core + 10gb ram + RX550-4gb vram):

-Trees need optimization. Jungle rock fps is half of every other map.
-Same for West Coast.
-Traffic also divides fps by half.
-But yes, Italy does not even load here. It might need more than 10gb ram?
--- Post updated ---
Anyway, happy holidays to the devs and thank you very much for the linux port.

 

I can confirm that with Proton version the wheel is recognized correctly, DPAD works as expected, but the FFB doesn't work. Using new-lg4ff as well.

FFB works fine with Proton 6.3-8, but some maps have broken textures.

 

oh then it might have been the other way around, that 6.3-8 was the last version it still worked.
The broken textures are because of the "new" PBR textures, it got fixed in later proton version, else you can also manually copy them: https://github.com/SnoutBug/BeamNG_terrainMaterialCache

 

Yea I tried this on steam deck, works well on desktop mode and using the gamepad config by holding the hamburger button works perfectly, I'm getting like 55 fps at normal settings in west coast usa

I'm having issues with it in game mode though, it frequently just pauses for a few seconds in the menu and in game, making loading anything slow, and controls don't work in game mode either

 

Is there anyway to verify I'm running the native linux version without launching manually? When I use the Steam launcher the Beam launcher does come up but the only option is "launch game" I don't see any choices for Proton or Native.

 

- Linux Port doesn't have a Launcher (yet)
- Options -> Performance -> Operating System (OS): With wine/Proton you'll see some Windows version, with the Linux Port you'll see your Linux distro
--- Post updated ---
that surely is an interesting bug I haven't seen in a while lol...
(Garuda Linux, i5-12600k, 6700xt, Map is Gull Coast, The Car is supposed to be a D-Series)

 

Are you saying this was never implemented?

 

well, if it is implemented, I can't find it....
Not a selection at launch like with other games (3DMark has this thing where you can select forced 32bit or forced 64bit mode)
No "beta" for the Linux version...

@tdev: if it is there, where?

 

AFAIK it is not implemented yet. I mean, the native linux version "just" came out (in June 2022!). We're beta testers basically. But we all have the linux version inside the BeamNG folder! Just launch "Steam/steamapps/common/BeamNG.drive/BinLinux/BeamNG.Drive.x64". It's an executable file. Just be aware, the native version not being officially implemented in steam (yet), this means the loading times will be very long for the first time you load a map (only the first time) because the "shaders" thing will be done 100% in the background with no progress bar whatsoever.

 

When starting the game under a machine running on Arch, the game boots and seems to load in fine, but crashes for seemingly no reason 1-2 seconds after the map loads. There are no visible graphical or audio glitches, or issues in the crash log. The log just cuts off at a random point each time. I'm wondering why I'm having these issues and if there's anything I can do to fix this. Any feedback would be appreciated!

EDIT: The game also immediately crashes using Proton.

 

On my laptop, the game works pretty well with my RX 5500M running ArchLinux under XFCE, I put the settings on low, with mesh quality on high, I play multiplayer (8 players with ~ 100 fps on West Coast USA) with a beammp running in proton, it recognizes beamng although it does not run in proton.

 

I've also been having the same issue, I didn't have this problem before with Arch, no idea what changed it. I've found that loading the game with low graphical settings + partial shadows and no anisotropic filtering (and disabling all the effects, no bloom motion blur, etc) makes it able load maps and stay somewhat stable (it still crashes sometimes), but yeah with any other graphical setting it crashes 1 second after loading any map.

 

Yes I know, I previously mentioned in this thread that the game sometimes uses all the vram, however before it wasn't crashing, when the vram usage went to max the fps would just drop to 30.

Or is this a new issue with a newer version of vulkan that came out recently?

 

I've noticed exactly that, when I come close to the VRAM limit, the game seems to be very likely to crash...
as I almost always play on Ultra preset, it can fill up even 12GB of VRAM pretty fast

 

Hey, great work on the port! I run Steam in a Flatpak and there is an long-standing issue with the Chromium sandbox in a Flatpak sandbox. When I launch the Linux executable via Steam in Flatpak I get:

Code:

  2.37835|I|GELua.main| ============== Engine initialized ==============
[0122/124556.667472:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /home/media/games/steam_linux/steamapps/common/BeamNG.drive/BinLinux/chrome-sandbox is owned by root and has mode 4755.

Note that following the above suggestion (i.e. chwn root and chmod 4755) does not fix the issue.
Here is the same problem in a different game: https://github.com/flathub/com.valvesoftware.Steam/issues/897

It would be nice to be able to pass a --no-sandbox option for us Flatpak wierdos, or even better automatically detected Flatpak and passed --no-sandbox (perhaps not the safest idea, but Flatpak is already sandboxed so...).

BTW Proton version works well (but the Linux executable has much better FPS for me).

 

I'm pretty sure this is the same issue I reported earlier too. I'm also on Arch. Recently it's been happening even before the main menu loads. I will try clearing all settings and trying the ones you have posted above.

 

I did some testing today and the performance definitely improved, though not every option in the graphics menu works reliably and causes the game to crash and then refuse to boot back up. (I'm not quite sure which options cause this, yet)

I've also tried some accessories; a ThrustMaster T248 and the ThrustMaster TH8A Shifter. Now I'm not exactly sure if this is a driver issue or the cause lies somewhere else, but the shifter as well as the steering wheel get assigned the same id:


This causes the buttons of my steering wheel to be assigned to the buttons of my shifter
(The image below shows my shifter key binds and me trying to assign Shift Down to my Shifting pedal on my steering wheel)


Pressing a button on my wheel or my shifter does not light up the icon of the other device (first image), so shifter and wheel send signals independently.

The Shifter is not connected to my wheel directly, but via USB instead:

Code:

05:55:55 me@fedora-workstation ~ → lsusb | grep ThrustMaster
Bus 003 Device 002: ID 044f:b696 ThrustMaster, Inc. Thrustmaster Racing Wheel FFB
Bus 001 Device 003: ID 044f:b660 ThrustMaster, Inc. T500 RS Gear Shift

This is the respective config file:

Code:

{
  "bindings":[
    {
      "action":"gear4",
      "control":"button3"
    },
    {
      "action":"gear3",
      "control":"button2"
    },
    {
      "action":"gear7",
      "control":"button6"
    },
    {
      "isInverted":true,
      "action":"clutch",
      "control":"slider",
      "deadzoneResting":0.01
    },
    {
      "action":"gear1",
      "control":"button0"
    },
    {
      "action":"menu_item_select",
      "control":"button8"
    },
    {
      "action":"gearR",
      "control":"button7"
    },
    {
      "action":"steering",
      "angle":900,
      "control":"xaxis",
      "ffb":{
        "forceCoef":100,
        "frequency":60,
        "gforceCoef":0,
        "lowspeedCoef":true,
        "responseCorrected":false,
        "responseCurve":[
          [
            0,
            0
          ],
          [
            1,
            1
          ]
        ],
        "smoothing":150,
        "smoothing2":0,
        "smoothing2automatic":true,
        "softlockForce":1
      },
      "filterType":2,
      "isForceEnabled":true
    },
    {
      "action":"gear5",
      "control":"button4"
    },
    {
      "isInverted":true,
      "action":"brake",
      "control":"yaxis",
      "deadzoneResting":0.01
    },
    {
      "action":"accelerate",
      "control":"rzaxis",
      "isInverted":true
    },
    {
      "action":"gear2",
      "control":"button1"
    },
    {
      "action":"activateStarterMotor",
      "control":"button9"
    },
    {
      "action":"gear6",
      "control":"button5"
    }
  ],
  "devicetype":"joystick",
  "guid":"030000004f04000096b6000011010000",
  "name":"Thrustmaster Racing Wheel FFB",
  "version":1,
  "vidpid":"03000000"
}

I'm using Fedora Linux 37

I've also tried replacing the files with respect to the guide but to no avail. When using VendorID and ProductID the binds are not detected. joystick0 and joystick1 works, but with the same effect (the binds are overwritten).

Replacing core_input_bindings.bindings[1] and core_input_bindings.bindings[2] with my custom configs using a different vidpid for each device didn't change anything either.

I wonder where those GUIDs are coming from and whether it's possible to reassign them.