Why doesn't MSFS 2020 recognise FSUIPC control inputs?

MSFS 2020 does not list FSUIPC7 as a controller in Controls Options. FSUIPC7 is an external Windows program that reads your hardware and sends commands through SimConnect. If those commands have no effect, the usual cause is a failed connection, wrong FSUIPC profile, duplicate MSFS binding, or aircraft-specific control event.

Is MSFS supposed to show FSUIPC7 in Controls Options?

No. Your physical joystick, yoke or throttle may appear there, but FSUIPC7 itself will not. It runs alongside Microsoft Flight Simulator 2020 and passes control events to the simulator rather than presenting itself as an ordinary controller.

This applies to the Windows PC version. FSUIPC7 cannot be installed on Xbox, and older FSUIPC editions intended for previous simulators cannot replace FSUIPC7 in MSFS 2020.

How do I find where the FSUIPC input stops?

Trace one simple control from Windows to FSUIPC7 and then into a default aircraft.

1. Test the controller in Windows. Press Windows+R, enter joy.cpl and confirm that its axes and buttons respond. If Windows cannot see the device, neither can FSUIPC. For applicable hardware, work through our hardware-detection checks for Saitek yokes before changing FSUIPC settings.
2. Confirm the FSUIPC7 connection. Load a flight in MSFS 2020, start FSUIPC7 and check its window or log for a successful SimConnect connection. Run MSFS and FSUIPC at the same privilege level; standard-user mode is preferable unless another add-on specifically requires elevation.
3. Watch the raw input. Open the relevant axis or button assignment page in FSUIPC7 and operate the control. Changing axis values or button states prove that FSUIPC can read the device. No movement points to device detection, a changed USB identity or a stale joystick assignment.
4. Check the active assignment and profile. Verify that the control is assigned to the intended event and that the loaded aircraft belongs to the correct FSUIPC profile. A profile-specific assignment from another aircraft will not automatically apply.
5. Test a conventional event. Assign one basic function, such as elevator, throttle or parking brake, using a standard MSFS control. If an axis is routed through FSUIPC calibration, set its minimum, centre and maximum correctly before judging the result.
6. Remove the competing MSFS binding. The same physical axis should not control the same function through both MSFS and FSUIPC. Use a blank MSFS profile or follow our instructions for clearing conflicting controller bindings.
7. Try a default aircraft. If the assignment works there but not in a complex add-on, the connection is healthy and the add-on probably requires a custom event rather than the standard MSFS command.
8. Inspect the FSUIPC log. Enable the relevant input and control-event logging temporarily. An input with no outgoing event indicates an assignment or profile problem; a transmitted event with no cockpit response points towards an unsupported aircraft control.

Why does FSUIPC see the axis or button but the aircraft ignores it?

When the raw value moves in FSUIPC7, the hardware is working; concentrate on the selected profile, outgoing event and any competing assignment.

The wrong aircraft profile is active

Profile-specific controls apply only to aircraft associated with that profile. Check the loaded aircraft after changing liveries, variants or add-on versions, because it may have been treated as a different aircraft. Also confirm that FSUIPC can write its configuration file; otherwise assignments can appear to save but disappear after a restart.

The aircraft uses custom cockpit events

Many advanced aircraft do not operate every switch through standard simulator events. Throttles, autopilot functions and guarded switches may instead use custom input events, local variables or calculator code. Use the aircraft's documented FSUIPC preset or supported custom event rather than repeatedly assigning the stock command.

A default aircraft is the quickest control test. If the same FSUIPC assignment works there, reinstalling FSUIPC is unlikely to fix the add-on aircraft.

Another input keeps overriding FSUIPC

Duplicate axes commonly cause jumping controls, a throttle that returns to its previous position, or brakes that remain partly applied. Search the MSFS controller profile by input and remove every competing assignment for that function. Buttons can also collide with keyboard shortcuts, so compare them with our reference to MSFS 2020's built-in keyboard controls.

Do I need the FSUIPC WASM module?

The FSUIPC WASM module is not normally required for basic joystick axes, buttons or standard SimConnect controls. It becomes relevant when an aircraft integration depends on local variables, custom calculator code or other advanced functions.

If only custom add-on controls fail, verify that the module supplied by the FSUIPC7 installer is installed, enabled and reported ready. If every standard control is dead, troubleshoot SimConnect, profiles and assignments first.

Should controls be assigned in MSFS or FSUIPC?

Give each flight-control function one owner; using both systems for the same axis creates conflicts.

What if no FSUIPC assignment works?

If even a standard control fails in a default aircraft, test with a clean FSUIPC configuration before reinstalling the program.

• Close FSUIPC7 and back up FSUIPC7.ini.
• Rename it to FSUIPC7.ini.bak, restart FSUIPC7 and create one basic test assignment.
• Use a supported FSUIPC7 build and let its installer repair the required components.
• Check the new log for SimConnect errors before restoring any old profiles.

A clean configuration that works confirms that the original file contained a stale device identity, profile error or conflicting assignment. Restore settings selectively rather than copying the entire faulty configuration back.