Support

Get flying faster.

Controller setup, Android Chrome radio setup, first-flight troubleshooting, performance tips, and bug reports for acroFPV.

Email support Return to sim Compatibility Radio not detected? Android setup

Quick fixes

Radio not detected

Use desktop Chrome or Edge, or Android Chrome after confirming all four axes in Gamepad Tester.
Put the radio in USB joystick, HID joystick, or simulator mode before calibration.
Use a data-capable USB cable, then move a stick or switch once after plugging in.
Reload acroFPV after reconnecting the radio.
Open the radio troubleshooting guide.

Controls feel wrong

Run the controller wizard again from the Controller panel.
Center sticks before each capture step, especially throttle.
Move only the requested axis during calibration.
If roll, pitch, yaw, or throttle are swapped, restart the wizard and remap each channel.
If Android Chrome cannot see yaw, fix the EdgeTX axis mapping first.

Low FPS or stutters

Close heavy tabs, screen recording tools, and other 3D apps.
Try a smaller indoor map first, then move up to larger cruise maps.
Keep the browser window visible and avoid battery-saver mode while flying.
Update your browser and GPU drivers when possible.

Clips or Parts missing

Saved clips and Parts live in local browser storage.
Private windows, cleared site data, or a different browser profile can hide previous clips.
Exports create files through your browser download/share flow.
If download/share is blocked, check browser permissions and try again in Chrome or Edge.

First-flight checklist

Open acroFPV in desktop Chrome or Edge, or Android Chrome after the four-axis test passes.
Connect your radio in USB joystick, HID joystick, or simulator mode.
Move a stick or switch once so the browser can see it.
Run the controller wizard and map throttle, roll, pitch, and yaw.
Pick a map from the Map panel.
Fly a short line, set Clip Start and Clip End, then Save Clip.

Controller setup details

Recommended setup

Use a real radio/controller over USB. Desktop Chrome or Edge are the safest path; Android Chrome can work when the radio exposes throttle, roll, pitch, and yaw as gamepad axes.

If the OS cannot see it

Try another USB port, another cable, and a full browser restart. Charge-only USB cables are a common cause of controller detection issues.

If the browser cannot see it

Open acroFPV after the radio is connected, move a stick once, and check whether any browser permission prompt is waiting for input.

If calibration is noisy

Keep sticks still during center steps, avoid resting pressure on the gimbals, and redo the wizard after changing radio output modes.

If Android misses yaw

On EdgeTX, use Advanced USB Joystick, Interface mode Gamepad, and map yaw/rudder to rotZ or RZ. Then unplug and reconnect USB.

Clips and Parts

Saving a clip

Fly a line, use Clip Start and Clip End to mark the best section, then Save Clip. Short clips usually make stronger social edits than long raw flights.

Building a Part

Create a new Part in the Clip panel, add your strongest clips, then export or share it as a bundled Part file.

Report a bug

Send reports to support@acrofpv.com. The best bug reports include enough detail to reproduce the issue.

Browser and operating system.
Controller/radio model and connection mode.
Map name and what you were doing when it happened.
Steps to reproduce, expected result, and actual result.
Screenshot, screen recording, or exported Part if it helps explain the issue.

Known limits

Android Chrome controller input depends on phone, browser, cable, and radio HID mapping. Confirm all four axes before calibrating.
Browser and operating-system controller support varies by device.
There is no cloud account sync yet. Local browser data can be cleared by private browsing or site-data cleanup.
acroFPV is a browser simulator, not real-world flight training, legal advice, or a substitute for local drone rules.