Configure a PFC MCP with Project Magenta in FSX: choose the correct driver, connect FSUIPC or WideFS, test modes and fix common communication faults.
Configure a Precision Flight Controls MCP for FSX or FSX: Steam Edition by installing FSUIPC4, making the correct PFC driver the MCP’s sole owner, and selecting its Project Magenta output. Run the Project Magenta MCP application locally or through WideFS/WideClient, then test each mode; do not begin by assigning MCP buttons in FSX.
What software and connection path do I need?
FSX, the PFC hardware driver and Project Magenta must form one unbroken control path, with only one program reading the MCP. The usual arrangement is:
PFC MCP → PFC driver → FSUIPC4/WideFS → Project Magenta MCP → FSX
FSUIPC4 is the correct generation for both boxed FSX and FSX: Steam Edition. Do not substitute FSUIPC7, which is for newer Microsoft Flight Simulator releases. A local Project Magenta installation can communicate through FSUIPC4 directly; Project Magenta running on another computer requires the corresponding WideFS server connection and WideClient on that computer.
If the purpose of each software layer is unclear, our explanation of how connector software links an MCP panel to the simulator covers the underlying arrangement.
| Hardware arrangement | Interface to use | Do not use |
|---|---|---|
| Legacy serial PFC MCP | FSUIPC4 with the FSX-compatible PFC module, commonly PFCFSX.dll | A second PFC utility opening the same COM port |
| PFC USB MCP | The PFC-supplied interface intended for that exact model and FSX/Project Magenta | The legacy serial module unless the unit’s documentation explicitly requires it |
| Project Magenta on a networked PC | FSUIPC4/WideFS at the FSX end and WideClient at the Project Magenta end | Installing the FSX module on a computer that is not running FSX |
How do I configure the PFC MCP step by step?
The reliable setup order is to establish the hardware connection first, verify FSUIPC4, and add Project Magenta only after the PFC driver can see the MCP.
- Identify the MCP interface. Check whether the unit is a legacy serial device, a serial unit behind a USB adaptor, or a native USB model. In Windows Device Manager, note the assigned COM port for a serial connection. Older software may not enumerate unusually high COM-port numbers, so move it to a lower unused number if the correct port never appears.
- Install FSUIPC4 in the active FSX installation. Let its installer locate FSX rather than copying modules between installations. Start FSX and confirm that FSUIPC appears under the Add-ons menu. For a manual legacy installation, the relevant modules belong in
FSX\Modules. - Install one PFC interface. A legacy serial MCP normally uses the FSX-compatible PFC module. Open its configuration from the FSX Add-ons menu, select the detected COM port and choose the matching PFC hardware family. Close any diagnostic or vendor utility that might already have the port open.
- Select Project Magenta as the MCP target. Where the PFC driver offers native FS autopilot and Project Magenta or PM output modes, choose Project Magenta. Option names vary between PFC driver revisions, but the required result is that MCP controls are written to Project Magenta’s FSUIPC offsets rather than translated only into stock FSX keyboard commands.
- Start the Project Magenta MCP application. Run it on the FSX computer for a local installation. For a network installation, start FSX, establish the WideClient connection on the Project Magenta computer, and then launch the MCP application. A networked installation needs the appropriate WideFS activation, and firewalls must permit the connection.
- Match the aircraft family. Configure Project Magenta for the Boeing-style MCP or other supported family represented by the hardware and flight model. A Boeing MCP should not be treated as a generic Airbus FCU; speed, vertical and lateral modes use different logic.
- Test one control at a time. Turn the heading selector first. The selected heading should change on the physical MCP, in the Project Magenta MCP display and at the FSX end. Repeat with altitude, vertical speed and indicated airspeed before testing FD, CMD, HDG, ALT, V/S and autothrottle modes.
Values can be checked while parked, but test actual CMD engagement and aircraft response in a stable, trimmed flight. Some autopilot modes are correctly inhibited on the ground or when their engagement conditions have not been met.
Do I assign the MCP buttons in FSX?
No—dedicated PFC MCP controls should normally pass through the PFC and Project Magenta interface, not FSX’s Controls menu. Assigning the same switch as an FSX joystick button creates a second control path and can produce double increments, modes that immediately cancel, or displays that disagree.
If the USB model exposes ordinary joystick buttons, leave them unassigned unless its PFC interface specifically requires manual assignments. We see duplicate bindings constantly when a hardware utility, FSUIPC and FSX are all trying to process the same control.
Why is the PFC MCP not communicating with Project Magenta?
Most communication failures are caused by the wrong driver, an occupied COM port, a missing WideClient connection or two utilities controlling the MCP simultaneously.
| Symptom | Likely cause | Fix |
|---|---|---|
| FSX has no FSUIPC or PFC menu | The module is in the wrong FSX installation, failed to load or was blocked | Reinstall the FSX-compatible FSUIPC4 package into the installation actually being launched and approve trusted modules when prompted |
| PFC driver reports no unit or cannot open the port | Wrong COM port, cable problem or another program owns the port | Confirm the port in Device Manager, close every other PFC utility and reconnect the hardware before starting FSX |
| Hardware values change, but Project Magenta does not | The driver is using native FSX output or WideClient is disconnected | Select PM output and confirm that WideClient reports a live connection before starting the MCP application |
| One knob advances two or more steps | Duplicate input paths or encoder acceleration | Remove FSX button assignments and duplicate drivers first; adjust acceleration only after one control path remains |
| Project Magenta changes, but the aircraft ignores CMD or A/T | Engagement conditions are not met or the aircraft uses private autopilot logic | Test airborne in a trimmed default aircraft, then check compatibility with the intended flight model |
| Local programs cannot see each other | FSX and Project Magenta are running with different Windows privilege levels | Run them at the same privilege level and restart both applications |
Once communication is established, use our FSX autopilot mode and troubleshooting references to separate an MCP connection fault from normal HDG, NAV, ALT, V/S or approach behaviour.
Will the PFC MCP work with every FSX aircraft?
No—Project Magenta works best with a compatible flight model and panel arrangement that allows it to own the autopilot logic. Complex third-party aircraft often use private variables and custom autopilot code, so standard FSUIPC or FSX controls may not operate their CMD, LNAV, VNAV or autothrottle systems correctly.
A default Boeing aircraft is useful for proving the basic heading, altitude and vertical-speed path. Our Boeing 747 MCP mode walkthrough provides a baseline for testing FD, CMD, A/T, HDG, ALT and V/S. Passing that test confirms the connector path; it does not guarantee compatibility with an add-on aircraft’s custom systems.
For a full Project Magenta installation, avoid leaving another functional autopilot panel in control behind the external displays. Choose a Project Magenta-compatible flight model or disable conflicting panel logic, then add CDU-driven modes only after the basic MCP modes operate correctly.