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
Problem is, the in-game Steam overlay is broken in XCOM2 even though it works in other stuff.
Haven't played in a while and I forgot how to correct this.
edit: Confirmed. The controller support on an Xbox pad is really bizarre if you have Steam configured to recongize it as a Steam controller. To get the game working as it always did, right-click the game in your Steam games list, click on Edit Steam Controller Configuration, and change to the Controller template in the window that appears.
This forces XCOM2 to treat your controller as a regular 360/Xbox One controller.
I cant see this option when I right click Xcom 2. This has been driving me nuts as it seems to be random if it wants to treat my 360 controller as a steam controller or not and I just want it to recognize it as a 360 gamepad in the interface menu like usual
try disconnecting controller from pc and reconnecting while in game.
Issue:
Steam is configured to know about the xb360 controller, but then inside xcom2 menu settings, I can't select the 360 controller instead of mouse, which means the in-game interface is still using mouse+keyboard ui instead of xb360 ui, and I'm stuck using steam-controller config instead of the xcom2 native controller support.
This worked for me to solve it:
(1) Choose from the Steam Window Menu: Steam->Settings.
(2) In the Settings window, from the left options choose 'Controller'
(3) Click on the button for 'General Controller Settings'
(4) A new Steam window should pop-open for 'Controller Settings', where you can see your 360 controller is detected, and 'Xbox Configuration Support' option is currently checked ON.
(5) Uncheck that option for 'Xbox Configuration Support'.
NOTE: Unchecking that option now means steam doesn't know about your 360 controller anymore for other games!
(6) Now launch xcom2, go to the 'Options', then go to 'Interface', and now you should be able to choose the xb360 controller instead of the mouse.
(7) When done playing xcom2, don't forget to go back in there and re-enable the 'Xbox Configuration Support' if you want to use your xb360 controller with steam again for other games.
Go into Big Picture Mode.
Click into Library and click XCOM2.
On the left, click on Manage Game.
Click on Controller Options.
For the Steam-Controller setting for this game, change it to "Force Off".
That means, steam won't try to use steam controller when you launch XCOM2. Instead, you can now launch XCOM2, go into XCOM2 options and change it over to 'Controller'.
Hope that helps someone with this annoying issue. The built-in XCOM2 xbox controller support is great, once you get it working!
I did what you did on MacOS but xcom2 still couldn't detect my Xbox one controller
If you can't get it to work, may I suggest the following:
From the game launch page in big picture mode, select controller configuration, then browse the configurations for one which is based on an actual gamepad. Then try launching the game.
If this doesn't work, then please access your settings and reset your controller (via big picture mode) and try the above again. Hopefully this will work!
Don't forget to go to options!
when did you try this?
I did what you did on MacOS but xcom2 still couldn't detect my Xbox one controller
>
Hey Physiology, sorry it didn't work for you. I am on a Win PC, not sure if that has something to do with it. I used my method earlier in April about the time I posted, so not very long ago. Seems like some people here were able to get it to work properly with other solutions. Hopefully ArkAngel's approach might work for you or others.