Default profile folder — click the file dialog's address bar (or press Ctrl+L) and paste this path, then Enter to jump straight there:

Checks whether the browser sees the same physical stick(s) your actionmaps.xml refers to, matched by USB vendor/product ID (not by SC's js1/js2 numbering — those can differ from browser enumeration order). Load the same actionmaps.xml above first, then press a button or wiggle each stick — browsers only reveal a device to the page after it sees input from it.

vJoy (virtual joystick) support:
• Chrome / Edge — important: if vJoy is installed, Chromium can fail to detect some of your real devices (not just vJoy — a physical stick may not appear either), and vJoy's own axes read as zero. To use a real stick in Chrome you may need to uninstall or disable vJoy. Otherwise use Firefox, which is unaffected.
• Firefox: works, including vJoy. Note that each vJoy device only appears in the list above after you move one of its axes or press one of its buttons — the browser hides it until then.
• To bind two vJoy devices to different controls, give each a different number of axes/buttons in the vJoy config — that's how they're told apart (they share one USB vendor/product ID).

If an axis moves the wrong way, use the Invert checkbox next to it in the Bindings table below. The axis-letter-to-index mapping (which [N] is X vs Y vs twist) is a best-effort default — use the live per-device axis readout above to confirm it matches your hardware.

Click the game view to enable.