Reach us at:

hello@tolerence.net

To help us reproduce what you’re seeing, mention:

• The controller — model as the pad itself reports it (the “Name” cell in the tester shows the raw ID string).
• Browser + OS — e.g. “Edge 141, Windows 11” or “Safari, macOS 15”. Gamepad behavior varies by engine more than most things.
• What the tester did vs. expected — a button that doesn’t light, a stick reading frozen, rumble reported “not exposed”, a drift number that contradicts what a game shows.
• Guide fixes — deadzone numbers that didn’t hold, a fix step that changed with an OS update, a compatibility row that’s wrong. Screenshots of the current menu path are always appreciated.

If the pad shows nothing at all, say what the OS sees — whether it appears in Windows’ joy.cpl or an OS-level gamepad viewer narrows it to pairing vs. browser layer instantly.