Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
If I'm still stuck after setting up the Steam controller, I'll just forgest about it and move on.
ps. between coders, yeah, the Linux joystick API works just like that even without SDL2's controller API. it's just an array of buttons and axes, like I stated. If you use the normal SDL2 joystick API you will get the same result, you don't even need the special controller API, it's just convience for Steam releases. ds.
If you use the normal Linux joystick device or SDL's general joystick API you still get button and axes changes registered. If the issue was a controller button/axes mismatch and all I had to do was rebind, I would not have cared about that. I usually rebind anyway.
You're only half right here, so you're missing soeb's point a bit. The SDL2 "GameController" api is built on top of the Joystick API. So, while it's true that SDL2 can see all joysticks, it doesn't recognise all of them as "GameControllers". This is why you need to configure it outside of the game (or use BPM) and feed the game a string.
Why is this the case? Joystick re-mapping is hard. Really hard to get right, especially with the large variety of analog stick and trigger joysticks that we have these days. The GameController API makes all joysticks look like a 360 controller internally, so that the game doesn't have to support re-mapping at all. It's easier for game developers, and you don't see a bunch of games with half-assed joystick mapping that doesn't always work right.
Ethan Lee, a prominant Linux/Mac porter, has an excellent blog post about exactly this subject.
https://plus.google.com/102593483001615978126/posts/6YshLR6pJMW
Whether or not you think it's better to have each game have thier own remapping ability, or the system-wide SDL2 GameController API way is better, is another topic.
K wow, this thread is about Linux. I don't think BMP will work in your case, so you're best off trying to get x360ce working.
Everyone else manage to make proper Linux joystick support, Steam big picture mode and games, both in and out of Steam. In fact, there are many open source games you can use for reference. It's just not hard enough to warrant this limitation, speaking from experience.
You can rest your case though, I'm giving up. I will make sure that the next game I buy has full support for my hardware. It's still a let down for this game and this limitation shouldn't exist.
My controller worked fine in big picture mode. If it's so hard, why does my controller work in every other game and in big picture mode without any change of settings? In any case, consider the thread closed since the bpm settings solved the issue.
Thx @steev and @Benjamin, mapping the controls in BPM makes the controller work for me :-)
Thx to @Spongie for bringing up the issue and keeping at it.