Linux Port – Feedback, Known Issues, and FAQ

I've got more details for this, the ffb signal gets sent to my wheel any time I'm in a vehicle that doesn't have a ffb config (walking, props, trailers, etc) and I confirmed that this doesn't happen on Proton.

I captured some logs from the game; this is what I get when I exit and then enter the vehicle

Code:

604.652|D|GELua.util_richPresence.Rich Presence|Playing Freeroam on Gridmap V2 with Walking
604.668|D|GELua.core_input_bindings.bindings|Loaded 31 bindings for device joystick0
604.669|E|addBinding|Could not create a description for binding keyboard0::*
604.670|D|GELua.core_input_bindings.bindings|Loaded 289 bindings for device keyboard0
604.670|D|GELua.core_input_bindings.bindings|Loaded 19 bindings for device mouse0
604.670|D|getFFBID|          Found 0 FFB binding candidates to be assigned for action "steering" in vehicle 'pickup', vehicle ID 43690 (sorted by suitability)
604.670|D|logFFBInterfaces|Found 1 FFBInterface candidates (unsorted)
604.670|D|logFFBInterfaces| * ffbinterface: ffbid 0, ptr 0x7f1a5587f670, enabled true, devName joystick0, axis 0 bindingAction steering, player 0
604.670|D|getFFBID|          Found 0 FFB binding candidates to be assigned for action "accelerate" in vehicle 'pickup', vehicle ID 43690 (sorted by suitability)
604.670|D|logFFBInterfaces|Found 1 FFBInterface candidates (unsorted)
604.670|D|logFFBInterfaces| * ffbinterface: ffbid 0, ptr 0x7f1a5587f670, enabled true, devName joystick0, axis 0 bindingAction steering, player 0
604.670|D|getFFBID|          Found 0 FFB binding candidates to be assigned for action "brake" in vehicle 'pickup', vehicle ID 43690 (sorted by suitability)
604.670|D|logFFBInterfaces|Found 1 FFBInterface candidates (unsorted)
604.670|D|logFFBInterfaces| * ffbinterface: ffbid 0, ptr 0x7f1a5587f670, enabled true, devName joystick0, axis 0 bindingAction steering, player 0
604.670|D|getFFBID|          Found 1 FFB binding candidates to be assigned for action "steering" in vehicle 'unicycle', vehicle ID 44930 (sorted by suitability)
604.670|D|getFFBID|           * playerBinding: Player 0, devName "joystick0", control "xaxis"
604.670|D|logFFBInterfaces|Found 1 FFBInterface candidates (unsorted)
604.670|D|logFFBInterfaces| * ffbinterface: ffbid 0, ptr 0x7f1a5587f670, enabled true, devName joystick0, axis 0 bindingAction steering, player 0
604.670|D|getFFBID|Step 1: Perfect match found for player 0, device 'joystick0', control 'xaxis', ffbAxisIndex 0, ffbAxisName 'xaxis'
604.670|D|getFFBID|          Found 2 FFB binding candidates to be assigned for action "accelerate" in vehicle 'unicycle', vehicle ID 44930 (sorted by suitability)
604.670|D|getFFBID|           * playerBinding: Player 0, devName "joystick0", control "zaxis"
604.670|D|getFFBID|           * playerBinding: Player 0, devName "keyboard0", control "up"
604.670|D|logFFBInterfaces|Found 1 FFBInterface candidates (unsorted)
604.670|D|logFFBInterfaces| * ffbinterface: ffbid 0, ptr 0x7f1a5587f670, enabled true, devName joystick0, axis 0 bindingAction steering, player 0
604.670|D|getFFBID|Step 1: Wrong match found for player 0, device 'joystick0', control 'zaxis', ffbAxisIndex 0, ffbAxisName 'xaxis' (has FFB disabled)
604.670|D|getFFBID|Step 1: Wrong match found for player 0, device 'joystick0', control 'zaxis', ffbAxisIndex 1, ffbAxisName 'yaxis' (has FFB disabled)
604.670|D|getFFBID|Step 1: No matches found for player 0, device 'joystick0', control 'zaxis' (abandoning search on this device)
604.670|D|getFFBID|Step 1: No matches found for player 0, device 'keyboard0', control 'up' (abandoning search on this device)
604.670|D|getFFBID|Step 2: Wrong match found for player 0, device 'joystick0', ffbAxisIndex 0, ffbAxisName 'xaxis' (has FFB disabled)
604.670|D|getFFBID|Step 2: Wrong match found for player 0, device 'joystick0', ffbAxisIndex 1, ffbAxisName 'yaxis' (has FFB disabled)
604.670|D|getFFBID|Step 2: No matches found for player 0, device 'joystick0' (abandoning search on this device)
604.670|D|getFFBID|Step 2: No matches found for player 0, device 'keyboard0' (abandoning search on this device)
604.670|D|getFFBID|          Found 2 FFB binding candidates to be assigned for action "brake" in vehicle 'unicycle', vehicle ID 44930 (sorted by suitability)
604.670|D|getFFBID|           * playerBinding: Player 0, devName "joystick0", control "rzaxis"
604.670|D|getFFBID|           * playerBinding: Player 0, devName "keyboard0", control "down"
604.670|D|logFFBInterfaces|Found 1 FFBInterface candidates (unsorted)
604.670|D|logFFBInterfaces| * ffbinterface: ffbid 0, ptr 0x7f1a5587f670, enabled true, devName joystick0, axis 0 bindingAction steering, player 0
604.670|D|getFFBID|Step 1: Wrong match found for player 0, device 'joystick0', control 'rzaxis', ffbAxisIndex 0, ffbAxisName 'xaxis' (has FFB disabled)
604.670|D|getFFBID|Step 1: Wrong match found for player 0, device 'joystick0', control 'rzaxis', ffbAxisIndex 1, ffbAxisName 'yaxis' (has FFB disabled)
604.670|D|getFFBID|Step 1: No matches found for player 0, device 'joystick0', control 'rzaxis' (abandoning search on this device)
604.670|D|getFFBID|Step 1: No matches found for player 0, device 'keyboard0', control 'down' (abandoning search on this device)
604.670|D|getFFBID|Step 2: Wrong match found for player 0, device 'joystick0', ffbAxisIndex 0, ffbAxisName 'xaxis' (has FFB disabled)
604.670|D|getFFBID|Step 2: Wrong match found for player 0, device 'joystick0', ffbAxisIndex 1, ffbAxisName 'yaxis' (has FFB disabled)
604.670|D|getFFBID|Step 2: No matches found for player 0, device 'joystick0' (abandoning search on this device)
604.670|D|getFFBID|Step 2: No matches found for player 0, device 'keyboard0' (abandoning search on this device)
618.973|D|GELua.util_richPresence.Rich Presence|Playing Freeroam on Gridmap V2 with Gavril D-Series
618.991|D|GELua.core_input_bindings.bindings|Loaded 31 bindings for device joystick0
618.993|E|addBinding|Could not create a description for binding keyboard0::*
618.994|D|GELua.core_input_bindings.bindings|Loaded 284 bindings for device keyboard0
618.994|D|GELua.core_input_bindings.bindings|Loaded 19 bindings for device mouse0
618.994|D|getFFBID|          Found 1 FFB binding candidates to be assigned for action "steering" in vehicle 'pickup', vehicle ID 43690 (sorted by suitability)
618.994|D|getFFBID|           * playerBinding: Player 0, devName "joystick0", control "xaxis"
618.994|D|logFFBInterfaces|Found 1 FFBInterface candidates (unsorted)
618.994|D|logFFBInterfaces| * ffbinterface: ffbid 0, ptr 0x7f1a5587f670, enabled true, devName joystick0, axis 0 bindingAction steering, player 0
618.994|D|getFFBID|Step 1: Perfect match found for player 0, device 'joystick0', control 'xaxis', ffbAxisIndex 0, ffbAxisName 'xaxis'
618.994|D|getFFBID|          Found 2 FFB binding candidates to be assigned for action "accelerate" in vehicle 'pickup', vehicle ID 43690 (sorted by suitability)
618.994|D|getFFBID|           * playerBinding: Player 0, devName "joystick0", control "zaxis"
618.994|D|getFFBID|           * playerBinding: Player 0, devName "keyboard0", control "up"
618.994|D|logFFBInterfaces|Found 1 FFBInterface candidates (unsorted)
618.994|D|logFFBInterfaces| * ffbinterface: ffbid 0, ptr 0x7f1a5587f670, enabled true, devName joystick0, axis 0 bindingAction steering, player 0
618.994|D|getFFBID|Step 1: Wrong match found for player 0, device 'joystick0', control 'zaxis', ffbAxisIndex 0, ffbAxisName 'xaxis' (has FFB disabled)
618.994|D|getFFBID|Step 1: Wrong match found for player 0, device 'joystick0', control 'zaxis', ffbAxisIndex 1, ffbAxisName 'yaxis' (has FFB disabled)
618.994|D|getFFBID|Step 1: No matches found for player 0, device 'joystick0', control 'zaxis' (abandoning search on this device)
618.994|D|getFFBID|Step 1: No matches found for player 0, device 'keyboard0', control 'up' (abandoning search on this device)
618.994|D|getFFBID|Step 2: Wrong match found for player 0, device 'joystick0', ffbAxisIndex 0, ffbAxisName 'xaxis' (has FFB disabled)
618.994|D|getFFBID|Step 2: Wrong match found for player 0, device 'joystick0', ffbAxisIndex 1, ffbAxisName 'yaxis' (has FFB disabled)
618.994|D|getFFBID|Step 2: No matches found for player 0, device 'joystick0' (abandoning search on this device)
618.994|D|getFFBID|Step 2: No matches found for player 0, device 'keyboard0' (abandoning search on this device)
618.994|D|getFFBID|          Found 2 FFB binding candidates to be assigned for action "brake" in vehicle 'pickup', vehicle ID 43690 (sorted by suitability)
618.994|D|getFFBID|           * playerBinding: Player 0, devName "joystick0", control "rzaxis"
618.994|D|getFFBID|           * playerBinding: Player 0, devName "keyboard0", control "down"
618.994|D|logFFBInterfaces|Found 1 FFBInterface candidates (unsorted)
618.994|D|logFFBInterfaces| * ffbinterface: ffbid 0, ptr 0x7f1a5587f670, enabled true, devName joystick0, axis 0 bindingAction steering, player 0
618.994|D|getFFBID|Step 1: Wrong match found for player 0, device 'joystick0', control 'rzaxis', ffbAxisIndex 0, ffbAxisName 'xaxis' (has FFB disabled)
618.994|D|getFFBID|Step 1: Wrong match found for player 0, device 'joystick0', control 'rzaxis', ffbAxisIndex 1, ffbAxisName 'yaxis' (has FFB disabled)
618.994|D|getFFBID|Step 1: No matches found for player 0, device 'joystick0', control 'rzaxis' (abandoning search on this device)
618.994|D|getFFBID|Step 1: No matches found for player 0, device 'keyboard0', control 'down' (abandoning search on this device)
618.994|D|getFFBID|Step 2: Wrong match found for player 0, device 'joystick0', ffbAxisIndex 0, ffbAxisName 'xaxis' (has FFB disabled)
618.994|D|getFFBID|Step 2: Wrong match found for player 0, device 'joystick0', ffbAxisIndex 1, ffbAxisName 'yaxis' (has FFB disabled)
618.994|D|getFFBID|Step 2: No matches found for player 0, device 'joystick0' (abandoning search on this device)
618.994|D|getFFBID|Step 2: No matches found for player 0, device 'keyboard0' (abandoning search on this device)
618.994|D|getFFBID|          Found 0 FFB binding candidates to be assigned for action "steering" in vehicle 'unicycle', vehicle ID 44930 (sorted by suitability)
618.994|D|logFFBInterfaces|Found 1 FFBInterface candidates (unsorted)
618.994|D|logFFBInterfaces| * ffbinterface: ffbid 0, ptr 0x7f1a5587f670, enabled true, devName joystick0, axis 0 bindingAction steering, player 0
618.994|D|getFFBID|          Found 0 FFB binding candidates to be assigned for action "accelerate" in vehicle 'unicycle', vehicle ID 44930 (sorted by suitability)
618.994|D|logFFBInterfaces|Found 1 FFBInterface candidates (unsorted)
618.994|D|logFFBInterfaces| * ffbinterface: ffbid 0, ptr 0x7f1a5587f670, enabled true, devName joystick0, axis 0 bindingAction steering, player 0
618.994|D|getFFBID|          Found 0 FFB binding candidates to be assigned for action "brake" in vehicle 'unicycle', vehicle ID 44930 (sorted by suitability)
618.994|D|logFFBInterfaces|Found 1 FFBInterface candidates (unsorted)
618.994|D|logFFBInterfaces| * ffbinterface: ffbid 0, ptr 0x7f1a5587f670, enabled true, devName joystick0, axis 0 bindingAction steering, player 0
618.996|D|libbeamng.hydros.init|Response to FFB config request: {
618.996|D|libbeamng.hydros.init|  steering = {
618.996|D|libbeamng.hydros.init|    FFBID = 0,
618.996|D|libbeamng.hydros.init|    ff_max_force = 10000,
618.996|D|libbeamng.hydros.init|    ff_res = 1,
618.996|D|libbeamng.hydros.init|    ffbParams = {
618.996|D|libbeamng.hydros.init|      forceCoef = 200,
618.996|D|libbeamng.hydros.init|      frequency = 0,
618.996|D|libbeamng.hydros.init|      gforceCoef = 0,
618.996|D|libbeamng.hydros.init|      lowspeedCoef = true,
618.996|D|libbeamng.hydros.init|      responseCorrected = false,
618.996|D|libbeamng.hydros.init|      responseCurve = { { 0, 0 }, { 1, 1 } },
618.996|D|libbeamng.hydros.init|      smoothing = 250,
618.996|D|libbeamng.hydros.init|      smoothing2 = 0,
618.996|D|libbeamng.hydros.init|      smoothing2automatic = true,
618.996|D|libbeamng.hydros.init|      smoothing2autostr = 340,
618.996|D|libbeamng.hydros.init|      softlockForce = 1,
618.996|D|libbeamng.hydros.init|      updateType = 0
618.996|D|libbeamng.hydros.init|    },
618.996|D|libbeamng.hydros.init|    ffbParamsJson = '{"frequency":0,"responseCurve":[[0,0],[1,1]],"responseCorrected":false,"smoothing2automatic":true,"gforceCoef":0,"lowspeedCoef":true,"smoothing":250,"smoothing2":0,"smoothing2autostr":340,"forceCoef":200,"softlockForce":1,"updateType":0}',
618.996|D|libbeamng.hydros.init|    ffbSendms = 0.0006152800006
618.996|D|libbeamng.hydros.init|  }
618.996|D|libbeamng.hydros.init|}
618.996|D|libbeamng.hydros.init|"/vehicles/pickup/": Force Feedback motor found for steering hydro. physicsID: 43690, FFBID: 0, ForceCoef 200, Smoothing 175, Update rate: 1625276Hz/0.0006152800006ms detected, 650110Hz safe, 0Hz selected, 2000Hz/0.5ms used (auto)

Is there a known workaround for this?

 

Having the same problem as https://www.beamng.com/threads/conn...blem-persists-please-take-a-look-here.100792/ after updating to 0.33

 

I was experiencing this for a while but it seems to have gone away. Does it still occur for you?

 

Hey I’m still having FFB delays on my g920 on arch Linux just reporting it again because it’s still happening on the latest patch

 

Randomly getting intermittent flashes of full application window black when I'm driving. The frequency of the flashes is low and random, but as the car's velocity increases, the frequency/probability seems to increase too?

Car: Ibishu Pessima Gen 1, Ibishu Diana Type LS
Map: Hirochi Raceway, spawned at Starting Line
BeamNG 0.33.3 Linux Build
Endeavour OS
KDE Plasma 6.2

 

Hi, I seem to be experiencing an issue with force feedback where I can feel steering lock before reaching the end of steering range. For instance in a roamer upon reaching 97% steering (according to the ffb ui app), force feedback starts increasing from 0.01% (or whatever it was on for dry steering) until it reaches 5% (which is the value of the steering lock strength as set in the controls menu) at full lock

Upon closer inspection this appears to be related to the previously-reported issue where steering lock is too strong, causing the steering lock strength slider to have no effect. Presumably there is supposed to be a gradual ramp up to full steering lock force but as regular ffb is being scaled differently from steering, even the 1% force commanded by this ramp is full force on my wheel.

 

Recently brought a Gamesir Nova Lite controller for PC and the right thumbstick doesn't get regonized at in BeamNG Linux, BeamNG (Windows) can see it since it's through steam/proton and other games work with it fine.

 

Recently switched to AMD experiencing this:
1. Flashing things:
- Map/Terrain quickly fades black in (guessing) .1 seconds or so, as if the light faded away
- The Skybox sometimes flashes white? Sometimes it's even the entire screen.
Both things seem to happen the more the camera moves but are still almost unpredictable.has something to do with evening/sunset sky

- occasional weird glichtes, geometry being stretched over the screen for a single frame perhaps?
- Fullscreen Blackflashing, seems to be affected by vsync, fpc, game pausing and mouse input?

I'm not too sensitive to flickering, but it is starting to mess with my head. i don't think it's healthy to paly like this.

 

Oyun içinde çoklu oyuncuya girmek istiyorum ama gmail hesabımı girerken sürekli hata veriyor şifre yanlış diyor nasıl çözebilirim

 

My GPU: RX6600
Distro: Arch Linux
DE: Plasma (kwin Wayland)
Sorry, I'm still a bit confused by the amd drivers, where do I find the driver versions relevant?
(I'm on arch, everything should ujst be the latest stable version)
--- Post updated ---

We seem to have the same issue(s)

 

I still can't get this game to run in nvidia and wayland. It will run in X11 tho. I've tried setting multiple backends, tried running in gamescope, anything i can think of, and still doesn't work. It definitely seems like some type of wayland/vulkan issue.

Every other game i have tested works in wayland with vulkan, but for some reason this one does not. I would use X11, but without hdr it looks dull and boring. Has anyone figured out why it's not working with nvidia latest drives and wayland? I'm also on arch linux.

RTX 4070 Video Card
Arch linux
nvidia 560 drivers
Wayland

i found this as well which seems similar to my issue -



also was able to discover this information -

Thank you for the additional information.

Based on your latest message:

• BeamNG.drive works under X11 but not under Wayland, regardless of whether you use Gamescope.
  
  
• You're repeatedly seeing messages about swapchain creation and DPI scaling failures:
  
  csharp

[Gamescope WSI] Created swapchain for xid: 0x400012 - imageCount: 4
123.25190|E|getMonitorDPI| Failed to get dpi scale for Monitor 0


Understanding the Issue
1. BeamNG.drive Compatibility with Wayland

BeamNG.drive may not be fully compatible with Wayland, especially on systems with NVIDIA GPUs. The repeated errors you're seeing suggest that the game is struggling to initialize its graphical context under Wayland.

2. NVIDIA Drivers and Wayland

Historically, NVIDIA's support for Wayland has lagged behind other GPU vendors like AMD and Intel. While recent drivers have improved support, there can still be issues, particularly with complex applications like games.

3. Swapchain and DPI Errors

The swapchain creation messages and DPI scaling errors indicate that the game is:

• Continuously attempting to create a swapchain (a series of images used for rendering), possibly failing and retrying.
• Unable to retrieve DPI scaling information from the monitor under Wayland, which may prevent proper window and UI scaling.

 

Have you tried the native version?
Also speaking of which, I could be wrong but I think the black flashing/flickering doesn't happen on x11 maybe?
--- Post updated ---

Does it occur on both x11 and wayland for you?

 

native version works, but is much slower than the linux version. I have to tune the settings much lower

 

You mean "the native version is much slkower than the windows version?" Right?

 

i'm on arch linux. I don't know how fast the windows version runs, but i imagine they are getting faster than 35-40 fps with 2-3 cars on screen. Also it runs flawless on vulkan on x11.
Plus i get lots of flickering if i try to play on 240hz, but no flickering when i play the linux version. I have to limit the windows version to 60hz

 

I really don't know how much I wil be abke to provide info, I just played like a few hours ago, barely had any flickering, even though it used to be unplayable just yesterday.
I switched to x11 just to try it out, got 10 instead of 100 fps somehow, but no flickering
switched back to wayland, no flickering at all for hours, changed the texture quality, ended up getting very little flickering, like once per 2 hours.
I have no idea how to track down when it happens more or less, best I can say is:
Camera movement speed and Italy, have some effect, afaict

 

Regarding flickering: it seems to be somehow related to Wayland or maybe XWayland. On X11, I could not make it flicker.
I'm running Fedora 41, KDE Plasma Wayland, AMD Radeon 6800XT. Single display, resolution 3440x1440@120Hz

Quick way to test it is to load the "Cliff" map. On wayland, it starts flickering immediately. On other maps, I might have to change the camera to "4" or "7".
Flickering happens on both native Linux version and Windows version (vulkan) with Proton Experimental.

Changing framerate limit to 60 or 30 (on 120Hz display mode) in the game's "Display-menu" stops the flickering but Vertical sync on/off does not seem to matter.

 

I wanted to check if I also get immediate flickering on the "Cliff" map.
I initially set my FPS limit to 100 (my monitor refresh rate).
Well, for me, Vsync does seem to make a huge difference.

I get:
Without Vsync or frame-Limit: Extreme constant flicker,
With Vsync, without frame-limit: Constant Flicker,
With Vsync and Frame-limit: Half-Extreme-speed Flicker
Without Vsync, but with Frame-limit: No flicker at all. (Correction: VERY rare short flickering)

However, with Frame-limit at 60 and Vsync enabled, There is also no flicker
Also pretty sure it only happens on wayland with Vulkan.
--- Post updated ---

(Edit nbr 500 or so)
It seems, the flickering has something to do ith the target framerate, (I'm not perfectly sure yet), but I think the black flickering occurs more when the target framerate/Monitor refresh rate is exceeded. Or at least somthing in that direction,

FPS limit isn't "perfect", so sometimes the framerate will exceed it's target.
For me, setting it to my monitors refresh rate may result in flickering, (limit 100)
But I get seemingly 0 flickering when setting it to something like 90 for example, where having 95 for a few frames doesn't seem to matter.

The actual issue might lie in Xwayland, but exceeding the monitor refresh rate makes it visible.
This issue is also only present in borderless or fullscreen, likely also because of the way Wayland renders fullscreen applications vs x11.

I'm assuming that it occasionally happens, that a "too long frame", is sometimes followed by a "too short frame", which will also make it look like it's flickering at lower framerates?

 

I think what zono50 is experiencing is the same problem that I already mentioned in this forum. On Wayland, BeamNG Linux native as well as Windows Vulkan version both crash upon launch, while the Windows DirectX Version (Which I think he is referring to as the "native version") launches fine. Although that configuration does work, the much lower performance compared to the other two versions makes it a dealbreaker for me. For reference, my system specs are:
GPU: Nvidia RTX 3060 12gb
CPU: R5 3600
OS: Fedora 40 KDE spin with Plasma Wayland 6.2.2, although it also crashes on different distros on wayland as well as different DEs
GPU Driver: 560
All three versions work fine on driver 550, but that driver has no support for explicit sync which makes it a dealbreaker for me, as that enables me to use Wayland on a daily basis at all on nvidia. It could be possible that the explicit sync stuff is causing the crashing, though.