How to use: Gaming Input Problem Solver
Choose the device and the closest observable symptom.
Complete each comparison without changing additional variables.
Open the recommended lab, then export the reproduction note with unresolved conditions clearly marked.
What the result actually measures
The solver collects the symptom, device, scope and controlled comparisons you complete. It narrows the next step based on whether the issue appears in Keymap, another browser, another port/connection and the target game.
Measurement boundary: The tree structures evidence but cannot inspect firmware, electrical signals, game code or physical components. It never replaces manufacturer support or a qualified repair decision.
How to interpret the output
Browser-wide
The symptom repeats across browsers or tools, increasing the value of connection, driver or hardware comparisons.
Game-only
The browser signal looks stable while the symptom stays in one game, so configuration or game-specific behavior deserves priority.
Intermittent
The next useful action is a longer controlled reproduction, not a premature definitive cause.
Troubleshooting unexpected results
No option describes the symptom
Choose the device and “intermittent/other,” then use the notes field to record the exact observable behavior without guessing a cause.
Several changes fixed it
Restore the previous state if safe and change one variable per pass; otherwise the causal clue is lost.
Frequently asked questions
Will the solver repair a device?
No. It produces a safer troubleshooting order and a clearer reproduction record.
Why test another browser?
It changes one software layer while keeping most hardware and operating-system conditions constant.
Can I send the result to support?
Yes. Export or copy the local text report after removing any notes you do not want to share.