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
Hope it helps mate.
You can probably use Steams internal controller tool to map it like a Xboner controller instead of trying directly, the game clearly doesn't know what to do with it.
It is mapped correctly. I really don't know what to do here. I guess I need to refund the game. I really can't justify spending money on a new controller just to play this. There isn't even a guarantee the new controller will work anyway. Might be refund time.
Tried that. Thanks for the advice though. I am willing to try anything.
360 is the first Xinput-native controller
Original Xbox controllers can also use both Xinput and DirectInput depending on which driver is used.
Whatever problem is happening here isn't strictly because of the controller API.
Apparently this is still an issue in 3+4, oddly enough I didn't have the issue in 1+2
Thanks for the help.