Controller lab
Controller vibration check
Send a short, low-intensity vibration request only when the browser and controller provide an actuator.
How to use this check
Connect a controller, press one of its buttons, then start. Available mappings and features depend on your browser, OS and device.
What the browser measures
Axes 0/1 and 2/3 are shown when exposed. The green circle is your preview threshold, not a hardware diagnosis. Numeric axis values appear above.
Reading the result
Start and explicitly request vibration. A completed API response describes the request, not proof you felt both motors. An unsupported or rejected response is recorded without declaring the controller faulty.
Why results can differ
A browser observes events exposed by your operating system. One test cannot establish whether a device is faulty. Connection, settings, focus and browser behavior can change the results.
Related checks
- Controller button and trigger test
- Controller stick drift observation
- Controller deadzone preview
- Methodology