[Tracking] Controllers and input: button icons, gyro, drift, dead zones, mappings #2504
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
2 participants
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#2504
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Button icons follow the controller connected when the game starts (turn it on before launching).
Reports
These reports were collected here so one fix closes them all and the open list stays readable. Add new details as a comment here (version, card and driver, where in the game, and the hookshot_log.txt from the game folder).
Another report collected here: #2514: Buttons remap not working
More reports of this, collected here:
hookshot_log.txt
Controller works in Insert menu and when backgrounded, but not when the game window is focused
Version:2.1.0
Controller: Wired Gulikit King Kong Pro 2
OS: Windows
GPU: Nividia Geforce Rtx 4060
Driver: 32.0.16.1088
Where it happens:Main menu
The controller is detected and works correctly in the Insert menu.
With the “Controller in background” setting enabled, the controller also works when the game window is in the background (e.g. after alt-tabbing).
As soon as I alt-tab back into the game, the controller stops working entirely. The game no longer responds to it.
Keyboard and mouse continue to work normally.
Temporary workaround:
I have to mash the Windows key and the Start button on the controller very quickly, then restart the game (usually takes two restarts). After that the controller is detected and works until I close and reopen the game, at which point the problem returns.It seems like the controller is being seen by the system, but the focus check that decides whether to send controller input to the game itself is getting stuck in the wrong state when the window regains focus.