The game picks up my controller seven times and tries to use all of them at once.

I recently moved to a new version of Proton, and that made the controller settings in BeamNG act up. This is most likely an issue with the Steam Controller settings, but I think this might require a local change anyway.

Most noticeably, my DualShock 4 which i've used with the game for years suddenly shows up multiple times in the Options > Controls > Hardware screen. Specifically, it shows up under these names:

• "Microsoft X-Box 360 pad (event)" (11FF28DE)
• "Sony Computer Entertainment Wireless Controller (js)" (05C4054C)
• "Microsoft X-Box 360 pad (js)" (11FF28DE)
• "Wireless Controller" (05C4054C)
• "Steam Virtual Gamepad" (11FF28DE)
• "XBox Controller 1" (XIDevice)
• "XBox Controller 2" (XIDevice)

It's obvious from the device IDs that the game is only picking up two controllers here, where one is the XInput device that the dualshock presents itself as, and one is the virtual gamepad that Steam presents. The problems start when the game tries to automap these seven controllers; I now have five separate bindings for most actions. Throttle is mapped to RYAxis, RYAxis, Up, RT, and RT. When I use my Logitech G29, the dualshock also randomly steals control away from the wheel and starts spinning the camera, since the bindings for the virtual controller clashes with the real one and they sort of "fight" for priority.

Is there a way to tell the game "ignore this controller" or "use only this controller"? Because as far as I can tell there is no way to tell steam which controllers to expose to games.

 

Unfortunately, your support tool doesn't work properly under Proton. It instantly times out when trying to upload and I can't get an ID from your support system. I'm not sure it even creates the zip file correctly as I can't find it in the user folder after running the tool. What does the game name it?

If you can tell me what files you want, I can upload them manually.

In fact, your whole launcher seems unstable when running under wine; in some views, clicking "Cancel" crashes it. I added the dump for that (the logfile was unfortunately empty).