Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

Tip: let participants check their gamepad before an online (OSWeb/JATOS) experiment

Hi all,


Following up on my earlier question about gamepad responses in OSWeb. One problem with controller-based online studies is that you can't see the participant's hardware. A worn controller with stick drift, a dead button, or a pad the browser never detected can quietly ruin a session.


One easy fix is to add a short "controller check" page before the experiment starts, for example on the JATOS study start page or a page in front of the OSWeb part. Participants press each button and move the sticks, and only continue when everything responds.


You don't have to build that check yourself. GamepadTesters.net has a free embeddable widget for this (gamepad tester and stick drift checker). You copy one line of HTML (an iframe) and it runs entirely in the participant's browser, with no sign-up:

https://gamepadtesters.net/


A few practical notes:


1. Keep allow="gamepad" on the iframe, otherwise some browsers block controller access inside embedded frames.

2. Tell participants to press a button first. Browsers only expose the controller after the first press on the page.

3. Ask them to let go of the sticks and check that the values stay near zero. Anything clearly above about 0.15 at rest suggests drift, so you may want to raise your deadzone or exclude that session.

4. Use the same browser for the check and the experiment, because button mapping can differ between browsers.


It doesn't replace proper timing validation, but it catches the "controller isn't working" problems before they cost you data. Has anyone else added a hardware check step like this to their online studies?

Free online controller tester: https://gamepadtesters.net/

Sign In or Register to comment.