acroFPV
Troubleshooting
FPV radio not detected in the simulator?
Most detection issues come down to cable, radio USB mode, browser focus, or calibration timing. Work through this list before changing your rates or controls.
Fast checklist
- Use desktop Chrome or Edge, or Android Chrome after confirming four moving axes in Gamepad Tester.
- Use a USB cable that supports data, not only charging.
- Select USB joystick, HID joystick, gamepad, or simulator mode on the radio.
- Turn off RF modules if your radio recommends that for joystick mode.
- Open acroFPV after the radio is connected.
- Move a stick or switch once so the browser receives input.
- Reload the page if the controller panel still says no controller detected.
What the browser needs
Browser games generally see controllers through gamepad-style APIs. That means your radio needs to appear to the operating system as a joystick, HID joystick, gamepad, or simulator controller. If the operating system never sees it, acroFPV cannot calibrate it.
Symptom table
| Symptom | Likely cause | Try this |
|---|---|---|
| Nothing appears after plugging in | Charge-only cable or wrong USB mode | Try a known data cable and choose joystick/simulator mode on the radio. |
| Radio appears in the OS, not in the browser | Browser has not received input yet | Focus the page, move a stick or switch, then reload. |
| Axes are swapped | Wrong channel captured during wizard | Run the wizard again and move only the requested axis. |
| Throttle reads backward | Axis direction mismatch | Redo calibration carefully and confirm low throttle before flying. |
| Android Chrome shows axes 0-2 but yaw never moves | EdgeTX classic joystick axis is not exposed by Android Chrome | Use Advanced USB Joystick, Gamepad interface mode, and map yaw to rotZ/RZ. |
Android Chrome missing yaw
If desktop Chrome works but Android Chrome does not show yaw in Gamepad Tester, do not recalibrate acroFPV yet. First make Android expose four moving axes. EdgeTX radios may need Advanced USB Joystick with yaw mapped to rotZ or RZ.
Still stuck?
Email support with your browser, operating system, radio model, USB mode, and what the controller panel says after moving a stick.
FAQ
Why is my FPV radio not detected by the simulator?
The most common causes are charge-only USB cables, the radio not being in USB joystick or simulator mode, the browser not seeing the controller until a stick is moved, or platform-specific controller support.
Should I use Chrome or Edge for browser FPV controller input?
Chrome and Edge are the safest desktop browser choices for browser-based controller and gamepad input. Android Chrome can work when Gamepad Tester sees four stable axes first.
Why does Android Chrome miss yaw from an EdgeTX radio?
Android Chrome may not expose the classic joystick axis used for yaw. Use EdgeTX Advanced USB Joystick, Interface mode Gamepad, and map yaw to rotZ or RZ.