Assign axes, buttons and switches with FSUIPC, prevent duplicate inputs, calibrate controls and build reliable aircraft-specific profiles.
To assign flight simulator controls with FSUIPC, install the FSUIPC edition that matches your PC simulator, remove competing in-sim bindings, then map axes on the axis-assignment page and buttons on the button-and-switch page. Calibrate primary axes, save aircraft-specific profiles where needed, and test every press, release and detent.
FSUIPC is a Windows control and add-on interface for supported editions of Microsoft Flight Simulator and Prepar3D. It cannot provide control assignments on Xbox or PlayStation, and it is not a universal mapper for simulators such as X-Plane or DCS.
What do you need before assigning controls?
You need the correct FSUIPC generation, an activated licence for its user-assignment facilities and a controller that Windows recognises properly.
- Matching FSUIPC edition: use FSUIPC7 for Microsoft Flight Simulator 2020 or 2024, and the FSUIPC generation specified for your exact FSX or Prepar3D installation.
- Stable hardware connection: connect the yoke, joystick, throttle and pedals before starting the simulator. Avoid changing USB ports after building the profile.
- Clean input signal: verify that every axis moves smoothly in the Windows Game Controllers panel before asking FSUIPC to process it.
- No competing assignment: clear the corresponding simulator binding from every connected device, not just the controller being configured.
FSUIPC calibration cannot repair a noisy potentiometer or a device that Windows detects incorrectly. MSFS users can use our controller calibration and duplicate-binding checks to establish a clean starting point.
How do you map axes and buttons in FSUIPC?
Build the assignment one control at a time so that duplicate axes, reversed inputs and unsuitable events are easy to identify.
- Remove duplicate simulator bindings. Create a blank or reduced controller profile in the simulator and delete only the functions that FSUIPC will handle. Camera, menu and interface commands can remain assigned natively.
- Open the FSUIPC options. In FSX and supported Prepar3D versions, this is normally available through the simulator's add-ons menu. FSUIPC7 runs as a separate Windows application, so open its own assignment window while MSFS is running.
- Select profile-specific mode if required. Enable the profile option and create or select an aircraft profile before making assignments. Leave it disabled when the control should apply globally.
- Detect an axis. Open the axis-assignment page, move one lever through a substantial part of its travel and use the rescan function if FSUIPC does not identify it immediately. Confirm that the displayed joystick and axis values correspond to the control you moved.
- Choose the axis event. Assign aileron, elevator, rudder, throttle or brake axes either directly to FSUIPC calibration or as a normal simulator axis. Do not assign a continuous lever to increment, decrement or toggle commands intended for buttons.
- Assign buttons and switches. Open the button-and-switch page, operate the control and select the required simulator event. A maintained switch may need one event when pressed and another when released. Enable repeat only for commands that should continue while held, such as trim adjustments.
- Calibrate the primary axes. On the joystick-calibration page, set the full minimum and maximum travel. Centred controls such as aileron, elevator and rudder should have a small centre zone; throttles and toe brakes usually need endpoint calibration instead.
- Save and test. Accept the settings, return to the cockpit and move each control slowly. Check the flight-control animation or cockpit indication, then test buttons in both their press and release states.
Should you send an axis directly to FSUIPC or to the simulator?
Use direct FSUIPC calibration for conventional flight controls, but prefer a normal simulator axis when an aircraft provides its own calibration or throttle-detent system.
| Assignment mode | Best use | Main caution |
|---|---|---|
| Direct to FSUIPC calibration | Aileron, elevator, rudder, conventional throttles and brakes that need FSUIPC dead zones, reversal or response shaping | The aircraft must support the standard control path, and the same axis must not remain assigned in the simulator |
| Send to the simulator as a normal axis | Aircraft that expect a native simulator event or provide their own throttle and detent calibration | Avoid applying conflicting curves, dead zones or reversal in several configuration layers |
High-fidelity aircraft sometimes bypass standard simulator events. If an axis works in a default aircraft but not in a particular add-on, use the input method that aircraft supports rather than forcing the generic FSUIPC event. For an airliner with cockpit-tablet detent calibration, a native throttle axis calibrated inside the aircraft is often the cleaner choice.
How do aircraft-specific FSUIPC profiles work?
An FSUIPC profile stores assignments and calibration for a particular aircraft or group of aircraft without changing the global configuration.
Create the profile before assigning controls, then load the relevant aircraft and confirm that FSUIPC selects it. Aircraft titles can differ between variants and liveries, so a profile may fail to activate even when the cockpit appears identical. Check the aircraft-name match if the expected assignments disappear after changing livery.
Profiles are especially useful when a single throttle quadrant serves a piston twin, a turboprop and a four-engine jet. Keep genuinely universal commands global, then place engine axes, propeller levers, mixture controls and specialised switches in the aircraft profile.
Why is an FSUIPC control assignment not working?
Most FSUIPC assignment failures come from duplicate bindings, the wrong event, a profile mismatch or calibration being applied in more than one place.
- The aircraft responds twice or the axis jitters: another controller or the simulator's default profile still owns the same function. Search every connected device for that assignment.
- The axis moves backwards: reverse it in one layer only. Reversing it in both FSUIPC and the simulator returns it to the original direction; our reversed-control troubleshooting steps cover the common causes.
- A button fires repeatedly: disable the repeat option unless the selected event is meant to repeat while held. Never send a toggle event on both press and release.
- FSUIPC does not detect an axis: move it through its full range, rescan, verify it in Windows and restart FSUIPC after reconnecting the device.
- Assignments change after a USB move: Windows may have given the controller a different joystick number. Keep devices on stable ports or use FSUIPC's joystick-letter facility to preserve their identities.
- A complex aircraft ignores the command: it may require an aircraft-specific input event rather than a standard simulator control.
- Nothing works in MSFS: confirm that the external FSUIPC7 process is still running and connected to the simulator.
Should you use FSUIPC or the simulator's control settings?
Use native simulator assignments for a simple single-simulator setup; choose FSUIPC when you need aircraft profiles, press-and-release switch logic, consistent calibration or shared hardware across several supported simulators.
A mixed setup is valid. Many simmers keep camera and menu commands in the simulator while assigning primary flight controls through FSUIPC. The rule is simply that one physical input should not control the same function through both systems. For a setup that does not require FSUIPC's advanced features, our guide to native joystick axis and button mapping covers the simpler route.