Testador de Controle Genérico

Guia Completo: Testando Controles de Terceiros e Genéricos

A HTML5 Gamepad API é projetada para funcionar com qualquer controle que o sistema operacional reconheça como um dispositivo de entrada gamepad padrão. Isso significa que nosso testador funciona com uma enorme gama de controles de terceiros, gamepads especiais, fight sticks, volantes de corrida e até adaptadores de console retrô.

Marcas de Controle Suportadas

• 8BitDo: Ultimate, Pro 2, SN30 Pro+, e todos os modelos com/sem fio. Controles 8BitDo são totalmente compatíveis via Bluetooth, USB-C ou o adaptador sem fio 2.4GHz incluído (apenas modo USB para detecção no navegador).
• Logitech: F310, F710, Logitech Gamepad F510 e controles especiais. O F310/F710 tem um interruptor de hardware (XInput vs DirectInput) — certifique-se de que está no modo XInput (posição X) para detecção adequada no navegador.
• Razer: Wolverine V2, Raion e modelos Kishi conectados via USB. Os protocolos sem fio proprietários da Razer podem não ser detectados pelo navegador.
• SteelSeries: Stratus Duo, Nimbus+ e outros modelos habilitados para Bluetooth.
• SCUF: Reflex, Instinct, Prestige — estes são controles de primeira linha modificados e funcionam de forma idêntica aos gamepads padrão Sony/Microsoft. PowerA, HORI, PDP: Controles de terceiros licenciados e econômicos. Estes frequentemente usam o protocolo XInput ou HID e são totalmente compatíveis.

Solução de Problemas com Controles Genéricos

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.

Se seu controle não está aparecendo no testador, tente estas etapas:

Problemas de Mapeamento de Botões

Ferramentas Relacionadas

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.

Testador de Controle Xbox

Teste recursos de controles Xbox One, Series X|S e Elite.

Testador de PS5 DualSense

Testador de PS4 DualShock 4

Teste botões, sticks, touchpad e barra de luz no seu DualShock 4.

Testador de Nintendo Switch

Diagnostique drift dos Joy-Con, Pro Controle e HD Rumble. A razão mais comum pela qual um controle não é detectado por um navegador é o protocolo de entrada que ele usa. O Windows suporta dois protocolos de gamepad: Se seu controle tem um interruptor físico (comum nos Logitech F310, F710 e alguns modelos 8BitDo), coloque-o no modo "X" (XInput) em vez do modo "D" (DirectInput) para a melhor compatibilidade com o navegador. Além dos gamepads padrão, a Gamepad API também detecta muitos controles especiais:

PS4 DualShock 4 Tester

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

Testador de Nintendo Switch

Diagnose Joy-Con drift, Pro Controle, 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 Teste de Botões 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 Teste de Zona Morta 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 Controle 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 Controles: 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 Teste de Botões 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 Teste de Zona Morta 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 Controles