[Enhanced Bug]: Incorrect mapping of L2/R2 triggers ?

[lctrr]

Issue Summary:

Hello, I installed today the GOG game + this mod on a portable thinkpad with Aeon Desktop (immutable Tumbleweed), stock install from lutris, direct download from the website.
Everything works like magic ! I couldn't imagine just booting it up and everything works perfectly including the controllers !
Everything, except for the L2/R2 triggers unfortunately :( They just don't do anything in game, which is weird considering the rest of the triggers are 100% correct.
I tried to look up in wine's control panel and the two triggers appear in the xinput panel and react to me pressing them.
I tried to look up in the game's config files but couldn't find any string to try and remap controls unfortunately.
My controller is a Stadia, connected via BT (via USB makes no difference).
I'll be happy to test something if it can help solve the mystery !

Log Files:

Now loading: DPadKeybinds::Initialize() ----------

[2026-01-15 19:14:07.672] [info] Checking for DPad Keybinds...

[2026-01-15 19:14:07.673] [info] No changes needed - DPAD keybinds already set.

[2026-01-15 19:14:07.673] [info] ---------- DPadKeybinds::Initialize() loaded in: 1 ms.	Now loading: ControllerRumble::Fix() ----------

[2026-01-15 19:14:07.677] [info] Intercept APlayerController::UpdateRumble(float strength): Pattern scan found. Address: SplinterCell.exe+ffafd14b

[2026-01-15 19:14:07.677] [info] Intercept APlayerController::UpdateRumble(float strength): Hook installed.

[2026-01-15 19:14:07.678] [info] ---------- ControllerRumble::Fix() loaded in: 4 ms.

Reproduction:

Connect a Stadia controller via bluetooth, launch Splinter Cell from Lutris flatpak version, stock parameters. At the loading screen (press shoot to continue), no button on the controller works

[Joshhhuaaa]

I'm not sure what to suggest but it sounds like the controller isn't getting converted from Xinput to DirectInput by Xidi. The patch uses Xidi in order to make Xinput devices have working triggers on Xbox controllers. Also on the loading screen, the A button should also work, if you want to confirm it's just the triggers not working.

[lctrr]

Thank you for the answer !

I took some more time to experiment, and the triggers seem to work in-game, I can put guards to sleep and shoot the lights with the shoot trigger.
I still can't advance past the loading screens though, I have to press the spacebar on my laptop. No button (or combination) that I could try made me go past that. The A button doesn't work.
Do you have any other idea ? Can i remap it via the gamefiles ?

[Joshhhuaaa]

We use Xidi profiles to detect when we are on a loading screen or cutscene and, as a temporary hack, have the controller simulate keyboard presses on that screen. This is necessary because that screen is hardcoded to only accept Enter, Space, and Escape.

It sounds like Xidi is not properly switching into the Video profile when you are in a cutscene or loading screen for some reason. How did you fix your triggers? I am assuming you fixed Xidi itself to get the triggers working, but maybe not.

You cannot really remap this for this particular case because we do not want it to affect gameplay, only this specific loading screen. The buttons are assigned in System\Xidi.ini. When a cutscene or loading screen is playing, it should be using the binds from [CustomMapper:Video], and all other parts of the game should use [CustomMapper:EnhancedMain]. The other sections in the file do not matter, they were originally for the vanilla game.

Maybe try changing some button mappings in Xidi.ini under [CustomMapper:EnhancedMain] and see whether the buttons change in-game. If nothing changes, then Xidi is not being hooked.