Controller not detected

[LocalHero]

I am running the latest version of SteamOS. I have a Nyko AirFlo PC that I use for all of the other games I play, and I have only ever had one other game not detect/use the controller. When I start the game, I have no control at all. I had to plug in a keyboard to check the settings and see that my controller is not detected.

I know this controller is working. I am able to navigate through the SteamOS interface, and play every other game with ease. I'm really excited to play this game, but I will have to wait until I can get this resolved. Any help would be appreciated. Thanks!

[AlenL]

Can you please post the Talos.log file? (Use pastebin.com, if it is too large.)

[daniel.mantione]

The game only detects gamepads that have a corresponding XML file in <gamedir>/Content/Config/Input/Linux. If there is no .xml file for your gamepad, the game will not detect it. It will write a complaint in Talos.log, but otherwise the game behaves like there is no gamepad at all.

Because there are only .xml files for a few Xbox and Logitech gamepads, so unless you are the lucky owner of one of these devices, your gamepads will be (almost) silently ignored. I express my doubts about this behaviour of the game.

I have a Gravis Xterminator Force here, which for fun I tried to connect and (of course) there was no .xml file for this gamepad. So I tried to create one, and it actually worked. The game now did detect the gamepad and it worked in the game.

Because the Xterminator Force has only a single pad, I did still need the mouse, but with the gamepad on the desk, right hand on gamepad, left hand on mouse, if found the game surprisingly playable and had a few good hours where I didn't touch my keyboard.

@AlenL what is your position towards the .xml files? Is it intentional that there are only a few files for Xbox and Logitiech gamepads, or can we perhaps contribute files for other gamepads?

[AlenL]

You can always contribute, and we will happily include them in the next update. Though we are planning on making a more generic system that will map all xinput-compatible controllers to the same default xml. We just didn't get around to that problem on the TODO list yet.

[daniel.mantione]

I have sent my file to [e-mail]. It should be possible to retrieve a lot of information in the .xml file from the driver. For example, if axis 2 generates ABS_RUDDER events, it is very likely a rudder control on the gamepad and you could do an automatic mapping based on that, doing an educated guess for for example the deadzone value in the .xml. For well known joysticks and gamepads an xml could then override them with better values.

[AlenL]

For general joysticks, that's an exercise in futility. :) We'd support the "Standard" gamepads that way only.
There's another way, and it would be to read settings from Steam Big Picture, but that's a bit weird, since we support multiple inputs, and Steam only exposes one gamepad.

[Bleep]

I also have a Logitech F310 that works with Portal. I am eagerly awaiting non-Zork play. I am new to the community, and I'm not sure how to get this done. Running on Dell inspiron laptop, win 10, 40 Ghz free

[AlenL]

F310 should work great, once you flip that little switch on the bottom of the device:
http://gaming.logitech.com/assets/47832/13/f310-gaming-gamepad-images.png
from D to X setting.

[Bleep]

I never knew! Thank you, for your prompt reply.

[Tatsuo]

So that you can use 🎮 Ps4 controller