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
Here are the steps:
1) Before starting the game make sure NO CONTROLLER IS ACTIVE when the game starts.
2) Navigate all the way to the main menu WITH THE KEYBOARD.
3) ONLY plug in or turn on your controller after the game reaches this point.
The controllers should now behave as normal.
I also confirm this issue still exists on the Xbox One Elite controller.
Helped me with my xbox one controller, many thanks!
search for "xpadder" 5.3 (last free version)
Battlestation works now fine on its own, but this prog is really useful and easy to use!
hm - weird that the wireless behaves on its own and not like the cabled...
a) maybe try my mentioned "xpadder" prog, worth a try
b) ask microsoft support what yould be the difference to the cable-link
c)...i.P.