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
https://i.imgur.com/jNPieWO.png
Yeah, I've done that, and I can map the controller and everything (again, the game recgonizes that it's there), but there is no option visible to switch to the controller primarily. The game still expects input from a mouse and keyboard.
Really a shame, this controller has waaaaaay more features than Xinput, and yet games are now only supporting Xinput. I feel bad for people trying to rock six button pads. I don't know why Microsoft wanted to dumb down controllers for everyone.
Thanks for your help, Ladez. You resolved my problem.
There's a short post here with some perspective from a small indie studio: http://zeppelinstudio.net/directinput-vs-xinput/
And it doesn't just affect indies. Whether it's an upstart indie studio or a AAA giant like Bethesda, time spent pandering to differing standards is time that could be better spent refining a single, standardized control layout. DirectInput and Xinput are not competing standards, the latter is intended as a replacement of the former, so it doesn't make sense to include support for the former in a new game.
It's not like KBM has 102 buttons or anything. And the mouse is totally not way more precise than analog sticks.