How do I set up FSUIPC for FSX controls and add-ons?

For FSX and FSX: Steam Edition, install the compatible FSUIPC4 module, let FSX trust and load it, then configure axes, buttons and aircraft profiles from the Add-ons menu. Add-ons that only use FSUIPC as a data interface normally need no control mapping and usually work without a registered user licence.

Correct FSUIPC version and licence for FSX

FSX and FSX: Steam Edition need FSUIPC4, the version built for the simulator's 32-bit architecture. FSUIPC6 and FSUIPC7 target different simulators and cannot replace FSUIPC4 in FSX.

Use a compatible FSUIPC4 build from our FSUIPC download and FSX installation page. FSUIPC is a module, so it belongs in FSX's Modules folder rather than SimObjects, the Scenery Library or an aircraft folder.

Running an FSUIPC client on another computer is a separate case and requires the matching WideFS components and licence. A registered FSUIPC licence alone does not turn local add-ons into network clients.

Install FSUIPC4 in FSX or Steam Edition

Install FSUIPC4 while FSX is closed, using its installer rather than copying files from another simulator installation.

1. Protect an existing setup. If FSUIPC is already installed, copy Modules\FSUIPC4.ini and any licence file before updating. Our instructions for backing up FSX configuration and add-on files cover the other files worth preserving.
2. Extract the downloaded archive. Run the installer from a normal folder, not from inside the compressed archive. Use administrator privileges if Windows blocks changes to an FSX installation under a protected system folder.
3. Select the correct FSX installation. The installer will usually detect it. If prompted, choose the folder containing fsx.exe. With boxed FSX and Steam Edition installed together, confirm that the installer has targeted the edition you actually launch.
4. Complete or skip registration. Enter a valid FSUIPC4 key if you own one. Otherwise leave registration blank; the module can still provide its data interface to compatible add-ons.
5. Allow the module to run. Start FSX and approve its software and publisher trust prompts. Load a flight, press Alt if the menu bar is hidden, then look for Add-ons > FSUIPC.
6. Close FSX normally once. This allows FSUIPC to create or update FSUIPC4.ini in the Modules folder.

Do not copy a boxed-FSX DLL.xml file over the Steam Edition version. Their application-data locations can differ, particularly when both editions are installed, and replacing the whole file may disable other modules.

How do I assign FSX controls through FSUIPC?

Registered FSUIPC4 can handle axes and buttons instead of FSX, but each physical control should have only one owner.

1. Check the hardware first. Confirm that Windows sees the full movement of every axis. If it does not, complete the basic joystick detection and calibration steps before changing FSUIPC.
2. Remove duplicate FSX bindings. In FSX's control settings, delete the axis or button assignment that FSUIPC will handle. If every joystick input will be assigned through FSUIPC, disabling FSX controller processing is another clean option.
3. Open Axis Assignment. Enter Add-ons > FSUIPC, select the axis-assignment tab and move one control at a time. Use Rescan when necessary, then move the intended axis through a clear portion of its travel.
4. Choose the routing method. Send ordinary primary controls directly to FSUIPC calibration, or send a normal FSX axis event when an aircraft's documentation specifically requires one. Do not assign both routes to the same lever.
5. Calibrate the axis. Open the appropriate joystick-calibration page, enable calibration, sweep the control through its full travel and set its centre or idle region. Test the cockpit control after applying the change.
6. Assign buttons and switches. On the Buttons and Switches page, press the hardware control and select the required FSX event. A maintained two-position switch often needs one action for the press and another for the release.
7. Create aircraft profiles. Use profile-specific assignments when a yoke aircraft, helicopter and multi-engine jet need different axes or buttons. Add related liveries to the same profile so a different aircraft title does not appear to lose the assignments.

Axis routing: direct to FSUIPC or through FSX

The correct route depends on how the aircraft receives control input.

If an axis passes through FSX before FSUIPC calibration, use full FSX sensitivity and a minimal null zone unless the aircraft documentation says otherwise. Direct FSUIPC axes bypass those FSX sensitivity settings.

Calibration for throttles, pedals and brakes

Set endpoints slightly inside the stable physical limits rather than relying on the exact mechanical stops. Give self-centring axes a small centre zone, but do not use a large dead zone to conceal a noisy potentiometer.

• Throttles: use a combined throttle for one lever, or per-engine axes when the hardware has separate levers. Configure a reverse zone only when the lever has a repeatable detent.
• Rudder: establish a narrow centre region so minor sensor noise does not move the pedals in the simulator.
• Toe brakes: check that released pedals produce zero braking. If braking increases in the wrong direction, use the calibration page's reverse option rather than assigning a second brake axis.
• Filtering and response slopes: add these only after the endpoints and centre are correct. Filtering cannot repair a failing sensor or a duplicate assignment.

Do FSX add-ons need a registered FSUIPC licence?

No. An add-on that lists FSUIPC as a communications requirement will normally connect through an unregistered FSUIPC4 installation.

No axis, button or key mapping is required merely to establish that connection. Start FSX, load a flight and then launch or activate the add-on according to its own instructions.

• An aircraft may still require specific standard events, custom controls or its own configuration utility. Use only the control names or identifiers supplied with that aircraft.
• An external utility displaying “waiting for simulator” may be starting before a flight is loaded, or FSUIPC may not have loaded at all.
• FSUIPC does not make an incompatible aircraft, gauge or module work in FSX. It only provides the interfaces and control facilities that the add-on was designed to use.

Why is FSUIPC missing from the FSX Add-ons menu?

A missing FSUIPC menu means the module was installed in the wrong place, blocked, rejected at the trust prompt or omitted from FSX's module-loading configuration.

1. Load an actual flight. Reveal the menu bar with Alt and check the Add-ons menu again.
2. Verify the module file. Confirm that FSUIPC4.dll is inside the active installation's Modules folder. If it is absent, rerun the installer and check its detected FSX path.
3. Read the installation and runtime logs. FSUIPC's logs normally identify the FSX path, configuration file and reason a module failed to load.
4. Reset a rejected trust decision. Back up fsx.cfg, remove only the entry referring to FSUIPC4.dll from its trusted-software section, then restart FSX and approve the prompt. Do not delete unrelated trusted entries.
5. Check security software. Restore the DLL if it was quarantined, then exclude only the verified FSUIPC file or FSX module folder rather than weakening protection globally.
6. Inspect DLL.xml only if the logs point there. A malformed file can prevent several add-ons from loading. Back it up and repair the FSUIPC entry instead of replacing the complete file.

How do I fix duplicate or dead controls?

Duplicate movement, oscillating throttles and controls that snap back are usually caused by the same input being assigned in FSX, FSUIPC and sometimes the aircraft itself.

• Control moves twice or flickers: remove its duplicate FSX or aircraft-utility assignment. Our guide to reviewing and removing FSX control assignments helps locate overlooked bindings.
• Axis appears in Windows but not FSUIPC: reconnect the device, keep it on the same USB port and use Rescan. USB changes can alter joystick numbering.
• Control works in a default aircraft only: the add-on probably intercepts that control or expects a different event. Follow its assignment method rather than increasing sensitivity.
• Assignments work with one livery only: check whether that aircraft variation has been included in the intended FSUIPC profile.
• Full deflection occurs too early: recalibrate the minimum, centre and maximum values. If the axis is routed through FSX, also check FSX sensitivity and null-zone settings.

For a clean test, close FSX and rename Modules\FSUIPC4.ini after making a backup. FSUIPC will create a fresh configuration at the next launch. This removes the existing mappings and profiles without uninstalling the module; preserve the old file and any separate licence file until the replacement setup is proven.