Create a versioned controller baseline
Run center and sweep tests before changing multiple in-game sliders. Save left and right stick observations separately because movement and aim can require different practical margins.
If drift appears only in game, compare the game’s deadzone, response model and any platform calibration layer. A centered browser sample does not rule out every software cause.
Repeatable checklist
- Record game build and platform
- Sample each stick separately
- Change one in-game value at a time
Do not infer physical latency from browser clicks
Browser pointer timing includes operating-system delivery and page scheduling. It is useful for repeatability and event-drop clues, but it is not a switch-to-photon latency measurement.
Use the problem solver to compare connection, port, power mode and background load without changing everything at once.
Repeatable checklist
- Run a repeatable mouse event sample
- Compare one connection variable
- Keep raw observation separate from diagnosis
Game-specific boundary: Do not copy a deadzone scale until you confirm the current game label and range. Seasonal updates may revise menus or defaults.