How do I set up XPUIPC in X-Plane 11 or 12?

To set up XPUIPC in X-Plane 11 or 12, install a compatible 64-bit XPUIPC build as a native plugin under Resources/plugins, launch X-Plane and confirm that it loads, then start the FSUIPC-dependent application. Use the matching network client only when that application runs on another Windows PC.

What XPUIPC does

XPUIPC is an FSUIPC compatibility layer for X-Plane, not the Microsoft Flight Simulator FSUIPC module itself. It exposes many familiar FSUIPC offsets so compatible flight-planning, hardware and cockpit applications can exchange data with X-Plane.

Use an application's native X-Plane connection when one is available; it usually understands X-Plane datarefs and aircraft-specific behaviour better. Choose XPUIPC when the application specifically requires FSUIPC-style offsets. Do not copy Microsoft Flight Simulator FSUIPC files into X-Plane.

XPUIPC is a native plugin, not a Lua script. Our explanation of the different FlyWithLua folders and script-loading process helps distinguish the two installation methods.

Which XPUIPC build should I use?

Use a 64-bit build that explicitly supports your X-Plane version and operating system. Treat XPUIPC as Windows-only unless the selected release specifically contains a plugin binary for another platform; a Windows plugin cannot load in macOS or Linux.

• X-Plane 11: use a 64-bit XPUIPC release intended for X-Plane 11 or confirmed compatible with it.
• X-Plane 12: prefer a release that explicitly lists X-Plane 12 support. An older plugin may load yet return missing or incorrect values because some underlying datarefs or mappings have changed.
• Client application: check that it uses offsets implemented by XPUIPC. An application being “FSUIPC compatible” does not guarantee that every feature, write command or Microsoft Flight Simulator-specific function will work.

If you keep both simulators installed, give each X-Plane installation its own plugin copy and configuration. Do not make X-Plane 11 and 12 share one plugin folder.

How do I install XPUIPC?

Install the extracted XPUIPC folder directly beneath the active simulator's Resources/plugins directory while X-Plane is closed.

1. Close X-Plane and the client application. This prevents files remaining locked while the plugin is replaced or updated.
2. Find the correct X-Plane root folder. It is the folder containing the X-Plane executable and directories such as Aircraft and Resources. If you have multiple copies, use our guidance on identifying the active X-Plane installation directory.
3. Extract the download fully. Do not place the ZIP archive itself in the simulator.
4. Copy the XPUIPC plugin folder into Resources/plugins. Preserve the package's internal files and subdirectories. The common mistake is an extra wrapper level such as Resources/plugins/XPUIPC/XPUIPC/; the actual plugin folder must be directly under plugins. Our X-Plane plugin installation and folder-nesting checklist covers this in more detail.
5. Launch X-Plane and load an aircraft. Open Plugins > Plugin Admin and check for XPUIPC. If it is absent, close the simulator and inspect Log.txt in the X-Plane root folder for lines containing XPUIPC.
6. Start the external application. Select its XPUIPC or FSUIPC connection mode if it offers one. Test first with a default X-Plane aircraft before introducing a complex add-on aircraft.

You do not normally need to enable X-Plane's general network data output. XPUIPC runs inside the simulator and obtains data through the plugin system.

How do I connect XPUIPC from another PC?

A same-computer application connects directly through XPUIPC, while a remote application needs the matching network client supported by that XPUIPC release, commonly called XPWideClient.

For a networked setup, give the simulator PC a stable local address or DHCP reservation, permit X-Plane and the remote client through the firewall on the private network, and start them in this order: X-Plane, the remote client, then the application. Do not forward XPUIPC's port to the public internet.

If the remote client cannot find X-Plane, check that both PCs are on the same subnet and that its configured address has not changed. Use the port documented for the installed XPUIPC release rather than guessing or changing X-Plane's unrelated UDP settings.

Do I need to edit XPUIPC offset mappings?

Most applications using standard supported offsets require no manual mapping changes. Edit the configuration only when the application or aircraft documentation supplies a specific mapping, or when you know which X-Plane dataref must be assigned to an unused offset.

Back up the existing configuration before editing it, and merge custom entries into the file supplied with the installed release rather than replacing that file with an old X-Plane 11 copy. Duplicate offsets, invalid datarefs and incorrect data types can produce frozen values or corrupt data.

If basic values work with a default aircraft but fail in a complex airliner, the aircraft probably uses custom datarefs. XPUIPC cannot automatically translate every custom autopilot, fuel, electrical or flight-management function into an FSUIPC offset; an aircraft-specific mapping or native connector may be required.

XPUIPC troubleshooting

The X-Plane Log.txt file is the first place to diagnose an XPUIPC installation that does not load or connect.

If Log.txt reports a missing Windows runtime or library, install the dependency specified by the XPUIPC release documentation. Avoid downloading individual DLL files from unrelated sources, as that can hide the real version mismatch and create a security risk.