Allgemeiner Regler-Tester

Vollständiger Leitfaden: Testen von Drittanbieter- und generischen Reglern

Die HTML5-Gamepad-API ist so konzipiert, dass sie mit jedem Regler funktioniert, den das Betriebssystem als standardmäßiges Gamepad-Eingabegerät erkennt. Das bedeutet, dass unser Tester mit einer enormen Bandbreite an Drittanbieter-Reglern, Spezial-Gamepads, Fight Sticks, Rennlenkrädern und sogar Retro-Konsolen-Adaptern funktioniert.

Unterstützte Reglermarken

• 8BitDo: Ultimate, Pro 2, SN30 Pro+ und alle kabelgebundenen/kabellosen Modelle. 8BitDo-Regler sind voll kompatibel über Bluetooth, USB-C oder den mitgelieferten 2,4-GHz-Funkadapter (nur USB-Modus für Browsererkennung).
• Logitech: F310, F710, Logitech Gamepad F510 und Spezialcontroller. Die F310/F710 haben einen Hardware-Schalter (XInput vs DirectInput) – stelle sicher, dass er für die ordnungsgemäße Browsererkennung auf XInput-Modus (X-Position) eingestellt ist.
• Razer: Wolverine V2, Raion und Kishi-Modelle, die per USB angeschlossen werden. Razers proprietäre Funkprotokolle werden möglicherweise nicht vom Browser erkannt.
• SteelSeries: Stratus Duo, Nimbus+ und andere Bluetooth-fähige Modelle.
• SCUF: Reflex, Instinct, Prestige – dies sind modifizierte First-Party-Regler und funktionieren identisch zu Standard-Sony/Microsoft-Gamepads. PowerA, HORI, PDP: Günstige und lizenzierte Drittanbieter-Regler. Diese verwenden oft das XInput- oder HID-Protokoll und sind voll kompatibel.

Fehlerbehebung bei generischen Reglern

The joystick drift epidemic has driven a new wave of "drift-free" controllers using <strong>Hall Effect sensors</strong>. Understanding the difference between the two technologies is crucial when evaluating your controller's health:

• <strong>Potentiometer (Standard):</strong> Uses physical carbon tracks and metal wipers to measure resistance. As the carbon wears away from friction over time, the resistance changes unpredictably, creating the phantom inputs known as "stick drift". Found in almost all standard controllers (DualSense, Xbox Series, Joy-Cons, DualShock 4).
• <strong>Hall Effect (Modern):</strong> Uses magnets attached to the stick and magnetic sensors (Hall Effect sensors) on the circuit board. The sensors detect the position of the magnets without any physical contact. Zero contact = zero wear = zero drift. Used in: DualSense Edge, 8BitDo Ultimate, GuliKit KingKong 2 Pro, Flydigi Vader 3 Pro.

Wenn dein Regler nicht im Tester erscheint, versuche diese Schritte:

Probleme mit der Tastenzuordnung

Ähnliche Werkzeuge

If your controller isn't appearing in the tester, try these steps:

• Ensure Chrome or Edge is fully updated (Gamepad-API requires a modern browser).
• Press any button on the controller first — the Gamepad-API only activates after a user interaction.
• Check if the controller has a mode switch (DirectInput vs XInput). Set it to XInput mode.
• Try a different USB port, ideally a rear motherboard port.
• On Windows, check Device Manager → "Human Interface Devices" to verify the OS recognizes the controller.

Xbox-Regler-Tester

Teste Xbox One, Series X|S und Elite-Regler-Funktionen.

PS5 DualSense-Tester

PS4 DualShock 4-Tester

Teste Tasten, Sticks, Touchpad und Lichtleiste an deinem DualShock 4.

Nintendo Switch-Tester

Diagnostiziere Joy-Con-Drift, Pro Regler und HD Rumble. Der häufigste Grund, warum ein Regler nicht von einem Browser erkannt wird, ist das von ihm verwendete Eingabeprotokoll. Windows unterstützt zwei Gamepad-Protokolle: Wenn dein Regler einen physischen Schalter hat (üblich bei Logitech F310, F710 und einigen 8BitDo-Modellen), stelle ihn für die beste Browser-Kompatibilität auf den "X"-Modus (XInput) anstelle des "D"-Modus (DirectInput). Über Standard-Gamepads hinaus erkennt die Gamepad-API auch viele Spezialcontroller:

PS4 DualShock 4 Tester

Test buttons, sticks, touchpad, and light bar on your DualShock 4.

Nintendo Switch-Test

Diagnose Joy-Con drift, Pro Regler, and HD Rumble.

The single most common reason a controller isn't detected by a browser is the input protocol it uses. Windows supports two gamepad protocols:

If your controller has a physical switch (common on Logitech F310, F710, and some 8BitDo models), set it to "X" mode (XInput) rather than "D" mode (DirectInput) for the best browser compatibility.

Beyond standard gamepads, the Gamepad-API also detects many specialty controllers:

• XInput (Modern): Microsoft's protocol, designed for Xbox controllers. It provides a standardized 16-button layout with two analog sticks and two analog triggers. The browser Gamepad-API works best with XInput controllers. Xbox, modern 8BitDo, and most new third-party controllers use XInput by default.
• DirectInput (Legacy): The older Windows protocol that supports up to 128 buttons and 8 axes, but with no standardized layout. Some older or specialty controllers (some Logitech models, certain HOTAS controllers) only support DirectInput and may appear with incorrect button mapping or not at all.
• Fight Sticks / Arcade Sticks: Hori Fight Stick Alpha, Qanba Obsidian, Mayflash F500, and Victrix Pro FS all work via USB. They report 8-12 buttons and directional inputs. Use the Tastentest to map every button.
• Racing Wheels: Logitech G29/G920, Thrustmaster T300RS, and Fanatec wheels are detected as gamepad devices. The steering axis, accelerator, and brake pedals map to analog axes. Force feedback cannot be triggered through the browser.
• Flight Sticks / HOTAS: Thrustmaster T.16000M, Logitech Extreme 3D Pro, and similar joysticks are partially compatible. Multiple axes (pitch, yaw, roll, throttle) are reported. Use the Deadzone-Test to calibrate each axis.
• Retro Adapters: USB adapters for SNES, N64, GameCube, and Genesis controllers typically use DirectInput and may need XInput wrapper software (like x360ce) for full browser compatibility.

Understanding XInput vs DirectInput: Why Your Regler Might Not Work

The single most common reason a controller isn't detected by a browser is the input protocol it uses. Windows supports two gamepad protocols:

• XInput (Modern): Microsoft's protocol, designed for Xbox controllers. It provides a standardized 16-button layout with two analog sticks and two analog triggers. The browser Gamepad-API works best with XInput controllers. Xbox, modern 8BitDo, and most new third-party controllers use XInput by default.
• DirectInput (Legacy): The older Windows protocol that supports up to 128 buttons and 8 axes, but with no standardized layout. Some older or specialty controllers (some Logitech models, certain HOTAS controllers) only support DirectInput and may appear with incorrect button mapping or not at all.

If your controller has a physical switch (common on Logitech F310, F710, and some 8BitDo models), set it to "X" mode (XInput) rather than "D" mode (DirectInput) for the best browser compatibility.

Testing Specialty Reglers: Fight Sticks, Racing Wheels & Flight Sticks

Beyond standard gamepads, the Gamepad-API also detects many specialty controllers:

• Fight Sticks / Arcade Sticks: Hori Fight Stick Alpha, Qanba Obsidian, Mayflash F500, and Victrix Pro FS all work via USB. They report 8-12 buttons and directional inputs. Use the Tastentest to map every button.
• Racing Wheels: Logitech G29/G920, Thrustmaster T300RS, and Fanatec wheels are detected as gamepad devices. The steering axis, accelerator, and brake pedals map to analog axes. Force feedback cannot be triggered through the browser.
• Flight Sticks / HOTAS: Thrustmaster T.16000M, Logitech Extreme 3D Pro, and similar joysticks are partially compatible. Multiple axes (pitch, yaw, roll, throttle) are reported. Use the Deadzone-Test to calibrate each axis.
• Retro Adapters: USB adapters for SNES, N64, GameCube, and Genesis controllers typically use DirectInput and may need XInput wrapper software (like x360ce) for full browser compatibility.

❓ Frequently Asked Questions: Generic & Third-Party Reglers