GameInput fails to update Gamepad State for Xbox 360 Controller
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.7k
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
I encountered an issue with GameInput while using an Xbox 360 Controller connected via a Wireless Receiver Dongle (I haven't tested it with a cable). The problem is that GameInput correctly detects that the gamepad is connected, but it fails to update the gamepad state, resulting in no input being registered. The vibration feature still works properly.
Furthermore, on one of my PCs, after connecting the Xbox 360 Controller just once, GameInput continuously displays that the gamepad is connected, even when it's physically disconnected and the Wireless Receiver Dongle is unplugged from the computer. I have to restart the GameInput Service to start working normally. It's worth noting that the Xbox Series X controller works flawlessly with GameInput.
Any assistance or suggestions on resolving this issue would be greatly appreciated.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the Xbox 360 Controller and Wireless Receiver Dongle, then inspect GameInput Service behavior for state updates and disconnect handling. Compare the results with the Xbox Series X controller, which reportedly works correctly. Done means controller input updates reliably and the device is no longer reported as connected after removal.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100