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
Is your XBone pad wireless? Are you using it in the same USB slot as your old XB360 pad? I often swap between a standard corded XB360 pad and a Hori FC digital depending on the game that I play, and many games like FF12 will get confused as to whether I'm player 1 or player 2 if something happens that disconnects my pad while playing the game.
I've has one occurrence where changing FF12's gfx settings interrupted this input API check and locked my ability to control the game with keyboard AND gamepad until I restarted Steam, thus re-registering my active gamepad as "player 1".
It's possible that if your XBone pad is wireless, periods of inactivity in the signal, even if brief, OR moving too far away could be causing one of these situations to arise. A shoddy, unofficial pad or USB cable you got from Gamestop could cause the same problem (have had Dualshock 4s do just this). Something on your system could also be taking up resources or activating keyboard input, thus taking focus away from your pad long enough for it to bump to an unplayable "player 2" slot so far as Steam is concerned.
In theory, if you have some sort of gamepad wrapper like Xpadder acting as a shield to these sort of intermittent interruptions, that could possibly help you since unlike FF15, I dont think FF12 has any sort of fixer for gamepad inputs.
Regardless, the issue with my Dualshock 4 was only fixed by replacing the generic part with an official one. At the end of the day, you may be out of luck if the issue is related to your ~entire~ gamepad being generic.
Try making sure the Fullscreen Optimisations compat feature is disabled, try switching the Fullscreen mode you're in between Borderless and Exclusive and see if it helps stop interruptions... Otherwise the last thing I could think of to fix it is to try SpecialK's Suite of mods and see if there's an option within to adjust the way the input API fires like it can on FF15 (though, it's complicated to do if you've not tried it on FF15 before with the help of a guide).