InputFusion doesn't work on some games

[syah0910]

There are a few games below that InputFusion does not work with :

• KINGDOM HEARTS 1.5 + 2.5 HD ReMix
• Hollow Knight
• Overcooked! All You Can Eat
• Batman: Arkham City GotY
• Resident Evil 2 Remake (2019) (Dinput8)
• King's Quest (2015)
• Lightning Returns: FINAL FANTASY XIII
• Fable Anniversary
• Dragon Age Inquisition
• FINAL FANTASY X/X-2 HD Remaster (Dinput8)
• Tiny Thor
• Iconoclasts
• Yonder: The Cloud Catcher Chronicles

meaning without InputFusion those games won't detect input from non-xinput controllers, like e.g. Switch Pro Controller.

[xan105]

Thanks for the testing. Appreciate it.

I originally thought that implementing XInput would be enough for most games.
But they are a lot of games that rely on DInput device enumeration to decide if they should use XInput.

I've been working on partially implementing DInput8 to solve this and later on DInput8-only games with a more thorough implementation.
However it is still a work in progress as of this writing.

Hopefully this should improve game compatibility.

I'll be sure to have a look at the aforementioned games. FFX was already on my list of DInput shenanigans.

[syah0910]

@xan105 a few more games that does not work with InputFusion :

• Cult of the Lamb
• Greedfall (Dinput8)
• Gunbrella

[xan105]

I thought I'd write a quick update on the situation for future reference.
ℹ️ Note that I'm no expert on the matter, and that this is still an ongoing research, so take my findings with a grain of salt.

Games that support more than one input API usually, but not always, do a lot of Win32 APIs sniffing behind the scenes to determine which input API to use and/or the kind of controller (Xbox, Playstation, ...).

The more I research this the more shenanigans I found.

Non-exhaustive list:

• DInput8 Device enumeration
• COM PNP Device enumeration (device ID contains "IG_" or not)
• Matching values from HID or RAW API

Honestly I had no idea the situation was so messy. I originally simply thought that games were using XInput with fallbacks 🙃.

Looking back I guess now I kinda understand why a lot of tools went the ViGem bus driver way (too bad it's now EOL). And why Steam Input ended up hooking HID and RAW APIs system wide when Steam is running.

I still hope to improve game compatibility but the focus of this project is on API translation first and foremost.

[AL2009man]

I can add Sonic X Shadow Generations (xinput9_1_0) to the list as "partially supported", but I might need to elaborate a bit. Do note that Sonic X Shadow Generation's Steam version does not provide PlayStation nor Nintendo Switch gamepad support, instead: they both rely on Steam Virtual Gamepad for basic button prompt detection. similar to Sonic Frontiers. I have no idea how the Epic Games Store version handles it.

I've ensured that Steam Input is disabled for Sonic X Shadow Generations. (not using the fancy -nojoy for this one, as i got lazy)

...You might need to replug the controller, as InputFusion may not initiate properly.

anyway, SonicXShadowGenerations.exe is both Shadow Generations and an In-Game Launcher at the same time. While the game does work as intended, if you were to select Sonic Generations, the game will close itself and open a separate .exe, but it may cause a game crash with a Denuvo Anti-Tamper bug report link. Relaunch the game and do the same steps as before and it'll work just fine.

The weird thing is that Sonic Generations Remaster correctly detects my PlayStation Controller and provides the correct button prompts, but not Shadow Generations (and the in-game launcher), as it gives you Xbox prompts instead. oddities, huh? I can deduce that Sonic Generations Remaster is somehow able to communicate with SDL_GamepadGetType and will provide the correct button prompts. It seems great that we can have a make-shift native gamepad support using InputFusion

And then I use a Nintendo Switch Pro Controller, and everything goes downhill.

On Sonic Generations Remastered using InputFusion: I spotted two major issues that will cause disruption:

1. USB Mode will made the Switch Pro controller get stuck on the A button. Bluetooth mode will be needed.
2. The Nintendo face button layout has become literal button labels, as opposed to a Positional Face button layout for consistency. this becomes a problem as Sonic Generation Remaster follows the Xbox layout when using Nintendo Switch controller unlike Shadow Generations

it does not affect Shadow Generations nor the in-game launcher. The first part is something I've witnessed before in selected Unity-based games.

[AL2009man]

@xan105, add Dead Rising 2 (and potentially Dead Rising 2: Off The Record) to the list of games that do not work with InputFusion.

oh boy, this one is a doozy. Dead Rising 2 seems to only detect a literal Xbox 360 Controller. it does not enumerate it, READS a X360 Controller Input.

Edit: this doesn't affect Proton compatibility layer, but for future reference: https://github.com/ValveSoftware/Proton/blob/proton_10.0/docs/CONTROLLERS.md