🤑 Indie game store🙌 Free games😂 Fun games😨 Horror games
👷 Game development🎨 Assets📚 Comics
🎉 Sales🎁 Bundles

I bought and used your simulator on linux. It's a nice little piece of software and very handy for training! However I have the issue that it is not able to access my joystick/gamepad from '/dev/input/js2'. It is a generic standard 4 axis device that I built according to the instructions in RC Transmitter to USB Gamepad Using Arduino that allows me to connect my Spectrum DX6i Transmitter to my PC. As it is working with e.g. flightgear and other software I have to assume the joystick/gamepad handling in FPV Freerider is not able to recognize it. How can I fix that?

I'm not a Linux user myself and don't know how to configure joysticks in Linux. Hopefully someone who knows will be able to chime in.

At least on Windows, you want to make sure to not have any other joysticks or special input devices such as wacom tablets connected as that sometimes causes a conflict which makes Freerider unable to recognize your joystick.

I used a PS3 controller w/o any problem on the same system with same devices connected - that should be fine.

Is there any way to manually select the device used? Is there a way to output more info for debugging? (If the code would be available I could have a look and try to compile myself.)

(Edited 3 times)

After looking through several forums and playing around with python-uinput (allows to software emulate HID stuff like joysticks) I found that this framework needs a joystick that has at least 1 button in order to use it - having 4 axes only is not sufficient!

On top of what framework was this software written? Is this Source Engine? Or UNITY Engine? I noticed that this console text output pattern ("Using libudev for joystick management") is pretty common. If you could tell me that I would open a bug report there.

That's interesting info, thanks for sharing. Freerider is built with the Unity engine.

(+1)

Your welcome! I reported it on bugs@unity3d.com - hope that helps.

I'm not sure if you ever found a solution, but thanks to the information you provided about needing at least one button I was able to resolve the same issue for myself.

I used Wejoy (https://github.com/Vantskruv/wejoy) to create a "virtual" joystick with 1 button and 4 axes and just forward the necessary axes from the physical device to the virtual. Hopefully that's useful to you or some future Linux user in need of a fix.