Final Fantasy XIII input freezes on Save/Load menu with Windows 10 built Xbox Driver.

Anonymous
2015-09-18T08:59:03+00:00

Final Fantasy XIII and Final Fantasy XIII-2 is unplayable using built-in Windows 10 Xbox Drivers. Game stops receiving controller/keyboard input at Save/Load menu when using a Xbox Controller.

This has been an issue since the preview days of Windows 10.

It will work when switching to the downloadable Windows 7, 8 and 8.1 drivers but this breaks input in some WinRT games like Minecraft for Windows 10 and prevents accessing the Xbox DVR game bar.

I'm not an the only user who has this issue. It affects everyone playing these 2 Final Fantasy games on Windows 10 who plays with a Xbox 360 or Xbox One controller.

What can be done that doesn't involve playing around with drivers and breaking compatibility with certain games and Windows 10 features?

Windows Insider program | Windows Insider preview | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2016-12-30T07:43:23+00:00

FIXED FOR ME

Nathan gave me an idea with his arbitrary fix by holding down the two triggers and moving the left control stick.

I've tried all the fixes in this thread, injectors, drivers etc, but Nathan's mention of the triggers led me to try to check my calibration on a whim.

What I noticed was that my Z-axis (triggers) was off center and recallibrated to ensure that all my axis reset to normal and sure enough, for whatever reason, the problem is resolved for me.

You guys may as well try it:

  1. Navigate to and select "Set up USB Game Controller" in Control Panel
  2. Ensure your XBox One controller is connected and select it
  3. Select Properties
  4. Under the Test tab, double check to ensure your Z axis is centered when at rest (it was skewed max for me despite functioning normally in games)
  5. Recalibrate as necessary until everything is calibrated as should be.

Try it out by launching FFXIII

Hope this helps you guys as it did for me!

Windows 10

Up to date controller drivers

Tested using both Bluetooth and USB connection.

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2016-03-02T09:58:05+00:00

Just to let everyone know that the update is now live across Windows Update. Just tested with an Xbox One controller and everything works as it should.

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2016-01-07T17:36:55+00:00

Ok I got this to reproduce using an Xbox one Controller. I've opened a bug and assigned to the correct team to investigate. Thanks for reporting this issue and being a Windows insider.

Was this answer helpful?

0 comments No comments

56 additional answers

Sort by: Oldest
  1. Anonymous
    2015-12-20T17:34:58+00:00

    Hey All,

    I had the same issue running FF XIII on Windows 10 using an Xbox One Controller.

    A fix has been found (although by now i'm pretty sure you may have found it already).  But, for anyone else looking for a fix here is the link on Steam:

    http://steamcommunity.com/app/292140/discussions/0/535152276586110166/

    Here is the simple step by step that will fix the save menu freezing issue:

    Go to "device manager"

    scroll to the bottom and find the xbox peripherals 

    right click update driver software

    press browse my computer

    press let me pick

    UNtick show compatible hardware

    install the one that says "Microsoft Xbox One Controller" (NOT the original "Xbox Controller" drivers)

    once you've done that all I had to do was go into the game, it didn't work at all at first then I unplugged it and replugged it and it's worked 100% perfectly ever since

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-12-21T01:56:28+00:00

    As far as I recall, that fix actually breaks a bunch of other games. It might be the same solution the thread starter was using as well (reverting to win8 driver), just using different steps to get to same result.

    In any case, it also can't be done if you happen to be using the recently released wireless adapter, that thing has an entirely different driver.

    Was this answer helpful?

    0 comments No comments