Game: Switch prompts no longer match a PowerA pad after restart #84

New issue

Open

opened 2026-11-13 02:27:26 +00:00 by mooki · 0 comments

mooki commented

2026-11-13 02:27:26 +00:00

Longshot version

Carried from Hookshot v2.1.0. Longshot main 6b2dafefe was checked in source; this is not a fresh Longshot controller reproduction.

What kind of problem

Controls

What happened

tofujack reported that the controls still work and custom bindings remain saved, but the Switch prompts no longer match their PowerA Core (Plus) wired pad after restarting. The pad has no mode switch. This is their report, not a physical-controller failure I reproduced.

I took on the investigation and posted the findings. The saved positions are read correctly in the source checks: the reported A/B/X/Y values 0/2/1/3 produce the displayed B/Y/A/X permutation. An SDL classification shared with a GameCube-style PowerA model is a specific lead, not a confirmed identification of this pad.

My controller-diagnostics change is already inherited by Longshot as 3abfa0a0. It logs the GUID and active mapping; it does not change input or fix this mismatch. No matching repair is established on main.

The missing evidence is a current startup log with the pad connected, including the GUID, mapping name and mapping-string lines, plus which physical labels produce each action. Windows and this physical pad have not been tested here. Do not replace the mapping by controller name alone.

Where in the game

Controller prompts and the Controls screen after restarting; the reporter says anywhere.

How often

Every time in the original report. Not reproduced with a physical pad here.

Graphics card and driver version

Reporter: RTX 4070 SUPER 12 GB; driver version not supplied in the form.

CPU, RAM and operating system

Reporter: Core i7-10700K, 32 GB RAM, Windows 11 build 26300.9974.

Changes from the defaults

Explicit Switch prompts and Custom layout; reported A/B/X/Y bindings 0/2/1/3. The original report contains the settings and log links. My checks did not establish the pad's active SDL mapping.

Other software hooked into the game

Not established. The reporter said no internal files were changed; that does not prove no external remapper was active.

Reported on GitHub as NotRexed/Hookshot#2546; taken on there by mooki.

### Longshot version Carried from Hookshot v2.1.0. Longshot main `6b2dafefe` was checked in source; this is not a fresh Longshot controller reproduction. ### What kind of problem Controls ### What happened [tofujack reported](https://github.com/NotRexed/Hookshot/issues/2546) that the controls still work and custom bindings remain saved, but the Switch prompts no longer match their PowerA Core (Plus) wired pad after restarting. The pad has no mode switch. This is their report, not a physical-controller failure I reproduced. I took on the investigation and [posted the findings](https://github.com/NotRexed/Hookshot/issues/2546#issuecomment-6823981487). The saved positions are read correctly in the source checks: the reported A/B/X/Y values 0/2/1/3 produce the displayed B/Y/A/X permutation. An SDL classification shared with a GameCube-style PowerA model is a specific lead, not a confirmed identification of this pad. My [controller-diagnostics change](https://github.com/NotRexed/Hookshot/pull/2678) is already inherited by Longshot as [3abfa0a0](https://git.magicbean.dev/MagicBeanDev/Longshot/commit/3abfa0a0ee07d9c48361b61bc8424f6c5fb7bc1f). It logs the GUID and active mapping; it does not change input or fix this mismatch. No matching repair is established on main. The missing evidence is a current startup log with the pad connected, including the GUID, mapping name and mapping-string lines, plus which physical labels produce each action. Windows and this physical pad have not been tested here. Do not replace the mapping by controller name alone. ### Where in the game Controller prompts and the Controls screen after restarting; the reporter says anywhere. ### How often Every time in the original report. Not reproduced with a physical pad here. ### Graphics card and driver version Reporter: RTX 4070 SUPER 12 GB; driver version not supplied in the form. ### CPU, RAM and operating system Reporter: Core i7-10700K, 32 GB RAM, Windows 11 build 26300.9974. ### Changes from the defaults Explicit Switch prompts and Custom layout; reported A/B/X/Y bindings 0/2/1/3. The original report contains the settings and log links. My checks did not establish the pad's active SDL mapping. ### Other software hooked into the game Not established. The reporter said no internal files were changed; that does not prove no external remapper was active. Reported on GitHub as NotRexed/Hookshot#2546; taken on there by mooki.