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: Most helpful
  1. Anonymous
    2015-12-30T02:40:41+00:00

    An update on this, a kind user on Steam forums has written a little injector that fixes this for at least XIII-2.

    Here's the link to the thread. http://steamcommunity.com/app/292140/discussions/0/487877107138721625/

    Additionally, this is what he says is at the core of this issue.

    "It is indeed how the LT & RT are being mapped. With the Xbox 360 controller LT and RT are mapped to a single parameter: DIJOYSTATE::lZ. However, with the Xbox One wireless controller the triggers are mapped separately to DIJOYSTATE::lZ and DIJOYSTATE::lRz. I wrote the fix as follows:

    joystate->lZ = (BYTE)(128 + (joystate->lZ / 255.0)*127.0 - (joystate->lRz / 255.0)*128.0);

    Unfortunately if the fix is not applied the default state would be for lZ to have the value 0. This would correspond to RT being pressed. This seems to lead to trouble."

    Hope this helps anyone who happens by this thread.

    I have to wonder why the triggers on Xbox One controller are mapped differently though. Is there a benefit to changing that behavior? Could Microsoft release a driver that would have the triggers mapped the old way instead of this new way? And I bet I'll never get an answer to any of these questions.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-12-22T05:32:21+00:00

    @Major Parsnip

    You're absolutely right.  I tested it with Fallout 4 and the controller is very glitchy.  It stutters when trying to crouch/sneak by pressing in the RS joystick and when selecting items/weapons within a menu, it skips around.

    I wish Microsoft would fix this.  It just seems like such an easy fix, but they seem to want to ignore the problem.

    Was this answer helpful?

    0 comments No comments