Weird behavior with Alone in the Dark: The New Nightmare

[instinctualjealousy]

I'm able to get Xidi to hook and log, and I have a valid Xidi.ini I made that gets no complaint prompt. It is worth noting I use a manifest workaround to convince games to load DLLs when they refuse to, this game is one of those games that would need Hookshot otherwise.

From what I can tell, the mapping changes I've applied within Xidi are not getting used (triggers won't assign as if they're axes still, keyboard mappings don't function/real keyboard does)- the log is very dead as well, as seen here:
Xidi_DInput8_alone4.exe_14092.log

This is after going to the controller configuration menu, configuring controls and the like, and closing the game. Looking at the alone4.exe process, it does weird stuff like load dinput.dll and dinput8.dll (I'm hooking with 8), I can confirm leading the game with dinput.dll as an entrypoint doesn't change anything. I can also confirm another dinput8 wrapper I have does hook and achieve its purpose with this game (with the same manifest workaround to get it to load, of course).

[Mapper]
Type		= AITDTNT

[CustomMapper:AITDTNT]
Template	= StandardGamepad

DpadUp		= Keyboard(Up)
DpadDown	= Keyboard(Down)
DpadLeft	= Keyboard(Left)
DpadRight	= Keyboard(Right)

ButtonBack	= Keyboard(Escape)
ButtonStart	= Keyboard(Enter)

[Log]
Enabled		= yes
Level		= 4

[Workarounds]
ActiveVirtualControllerMask = 0x01

I've even tried the ActiveVirtualControllerMask as seen here, in case it was that. I do seem to remember the game cared about which controller was set to default when used wrapperless?

[samuelgr]

Have you tried the winmm form of Xidi? If memory serves, some games use DirectInput for keyboard/mouse but winmm for joysticks and gamepads.