Fix: Xbox One controller in menus + Framerate pacer

[d.B.]

Hello everyone,

I've developed a utility that includes a fix for the Xbox One controller bug in menus and the well known patch that disables the framerate pacer. Since some people have mentioned experiencing problems with cutscenes after disabling the framerate pacer, I have included the option to disable the patch if desired (it cannot be disabled once the game has been launched).

The utility uses an "injection" style patching method and therefore does not modify the game on disk. This means that there is no need to worry about Steam updating the game and removing the patch. Simply run the utility and then launch the game.

For the moment I'm providing a binary only release. However, if there is enough interest in the source code I may release that as well.

Here it is https://github.com/d-b/final-fantasy-fixer/archive/v1.2.zip

The utility requires Windows Vista or later. I have only tested it on my own system, running Windows 10 Pro (x64).

Please post any bugs you experience here.

EDIT: I've added an updated version, v1.2, with support for big picture mode.

[Rabbit]

hi, thanks for this. Does this need to be run everytime i start the game or just once?

[d.B.]

As it uses an "injection" style patching method, or in other words it patches the game in memory, it must be run every time before the game is launched.

[MaverickHL]

Out of curiosity what caused the controller to act that way? Is it because of the two separate Z-Axis controls or is it the way it is being mapped? I know that FF does not really use the LT and RT buttons.

[d.B.]

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.

[MaverickHL]

Ahh I see that makes sense. Mind you FF is not the only games that can't handle the XBOX One controller due to the poor implementation of the latest XInput API. Do you know if you plan to develop a more generic method similiar to GeDoSaTo where you can add games to help make them work with the XBOX One controller via your "injector" method? I know a few games in my library having this issue.

I already got a Steam Controller for Christmas anyways but it would benefit those who want to still use the XBOX One controller.

[d.B.]

It is possible some of these games are broken for a different reason than FF XIII-2. I can provide a generic utility that will apply the trigger button fix, but it would help to have a list of broken games to test with. Of course, I will only be willing to test games already in my library.

[MaverickHL]

From the top of my head I know FF13, FF13-2, Azure Strike Gunvolt, Broforce and Absolute Drift.

[Roadrunner01]

I can not give it a Path to my FF13-2 exe. I even tried running as Admin.

[d.B.]

It is just there for informational purposes. It should be filled in with the path when the game is launched. It will be automatically detected. If it is not, that's a bug. If that's the case, please paste your OS version.

[Roadrunner01]

Windows 7 64Bit. It could just be me, but No path is automatically detected it is still blank.

[MaverickHL]

Try running it as an administrator and see if that helps.

[Racerprose]

Since I doubt XIII or XIII-2 will be updated again, it would be nice if this fix could be applied as a one-time fix patch rather than having to do it every time you want to play.

Is that possible?

[Cheesecake]

thank you very much. this fix is just what i needed as a xbox one controller holder!!

[Parsnip]

Thanks for the Xbone controller fix.

[Ca$hMonkey84]

merci beaucoup ça a marché super bien pour moi !