GTAFPV

CONTROLLER SETUP

Your sticks work, but the drone flies like a switch.

Full throttle or nothing, hard left or hard right, no smooth middle. This happens to some radios, DJI FPV controllers most often, because of how the game reads them, not because anything is broken. It takes about five minutes to fix.

TRY THIS FIRST: 30 SECONDS

You may not need to install anything

Many radios appear to the game twice: once as a raw interface that reads on/off, and once as a normal controller that reads perfectly. If yours does, you just have to pick the right one.

In game, type /fpvinput and sweep every stick through its full range. The report lists each device it can see and marks the sticks ANALOG or BINARY.

If any device is listed as ANALOG, open /setup, choose that device in the Controller tab, and run the setup wizard. You are done, so close this page.

If every device reads BINARY, carry on below.

Bridging the radio

Two free, open-source pieces. ViGEmBus lets Windows create a virtual controller; XOutput reads your radio and drives that virtual controller with it. The game then sees an ordinary gamepad with smooth sticks.

  1. Install ViGEmBus

    Download the latest installer from the ViGEmBus releases page and run it. It is a driver, so Windows will ask for permission and may want a restart. There is nothing to configure and no window to keep open.

  2. Download XOutput

    Grab the latest zip from the XOutput releases page and extract it somewhere permanent. Your Documents folder is fine, but not your Downloads folder, because you will want to run it again. There is no installer; you run the program directly from that folder.

  3. Plug in your radio, then power it on

    Order matters on DJI hardware: connect the USB cable first, then switch the controller on. Now start XOutput. Your radio should be listed among the input devices it can see.

  4. Map the four gimbals

    Open the configuration for your radio and bind the four axes to the left and right sticks. Move one gimbal at a time and let it detect the movement rather than picking axes from a list, because radios rarely number their axes the way you would guess.

    Mode 2, which is what most pilots fly: left stick is throttle (vertical) and yaw (horizontal), right stick is pitch (vertical) and roll (horizontal). If you fly Mode 1, map to taste, since GTAFPV can swap the sticks for you later either way.

  5. Start the virtual controller

    Press start in XOutput. Windows now has an extra Xbox 360 controller that mirrors your radio. Leave XOutput running whenever you fly. If you close it, the virtual controller disappears with it.

  6. Point GTAFPV at it

    Back in game, type /setup, open the Controller tab and pick the new Xbox 360 Controller from the list. Press a button on your radio first if it does not appear, because controllers stay hidden until they send something.

    Your radio will still be listed a second time under its own name, and that entry still reads BINARY. That is expected and not a failure, it is the raw view XOutput is reading from. Pick the Xbox 360 Controller and ignore the other one.

    Run the setup wizard and sweep each stick slowly and fully when it asks. Then run /fpvinput once more: every stick should now read ANALOG.

Still fighting it?

Run /fpvinput, screenshot the report and bring it to the Discord. It names every device the game can see and exactly where the resolution is being lost, which is usually enough to spot the problem in one message.