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

XPUIPC 2.0.5.9 is the latest public maintenance release of this legacy Windows-only FSUIPC compatibility plug-in. One 64-bit build supports both X-Plane 11 and X-Plane 12; no separate XP11 or XP12 build is required. macOS and Linux are unsupported because the archive contains only the Windows plug-in binary.

What XPUIPC does in X-Plane

XPUIPC exposes FSUIPC-style offsets to compatible X-Plane applications. It is useful for older flight-planning, hardware and cockpit software that expects an FSUIPC interface rather than native X-Plane datarefs.

XPUIPC is not the Microsoft Flight Simulator FSUIPC module, and copying FSUIPC files into X-Plane will not work. Use an application's native X-Plane connector when one is available; choose XPUIPC when the application specifically asks for XPUIPC or FSUIPC offsets. Searches for XUIPC or XPUIC usually refer to the same plug-in under a misspelt name.

The project is maintained as a legacy compatibility tool rather than an actively expanding implementation of every FSUIPC function. Basic offsets are widely supported, but Microsoft Flight Simulator-specific facilities and aircraft-specific custom systems may not be available.

Does XPUIPC work with X-Plane 11, X-Plane 12, macOS and Linux?

XPUIPC 2.0.5.9 supports 64-bit X-Plane 11 and X-Plane 12 on Windows only.

Operating systems and simulator versions outside those named by the release documentation should be treated as untested rather than assumed compatible.

XPUIPC download: which file should I use?

The verified public release is XPUIPC 2.0.5.9, distributed through the developer's official XPUIPC release and support thread as XPUIPC_2.0.5.9.zip.

Check both the version and complete archive name before extracting it. Avoid generic DLL sites, repackaged downloads and pages offering a loose win.xpl file: they may supply an older binary, omit the offset configuration or bundle an unrelated dependency. A filename alone does not prove that a repost is authentic.

The matching remote package is XPWideClient 2.0.0.3, supplied as XPWideClient_2.0.0.3.zip. It is needed only when the FSUIPC-dependent application runs on another Windows computer.

How do I install XPUIPC?

Extract the archive and place its inner XPUIPC folder directly under the active simulator's Resources/plugins directory.

The installed layout should include these paths:

• X-Plane 11/Resources/plugins/XPUIPC/64/win.xpl, or
• X-Plane 12/Resources/plugins/XPUIPC/64/win.xpl.

The same XPUIPC folder also contains its supplied configuration files, including XPUIPC.ini and XPUIPCOffsets.cfg. Keep those files beside the package's 64 directory.

1. Close X-Plane and any connected application. Do not replace the plug-in while the simulator is running.
2. Locate the active X-Plane root. This is the directory containing the X-Plane executable and folders such as Aircraft and Resources. Multiple simulator copies are common, so use our guidance for finding the X-Plane installation that is actually being launched if necessary.
3. Extract the ZIP completely. Do not copy XPUIPC_2.0.5.9.zip itself into the simulator.
4. Copy the inner XPUIPC folder. The final binary must be at Resources/plugins/XPUIPC/64/win.xpl.
5. Check for an extra folder level. A path such as Resources/plugins/XPUIPC_2.0.5.9/XPUIPC/64/win.xpl or Resources/plugins/XPUIPC/XPUIPC/64/win.xpl is wrong. Our X-Plane plug-in folder checklist explains how to spot archive-wrapper and double-folder errors.
6. Launch X-Plane and load an aircraft. Open Plugins > Plugin Admin and confirm that XPUIPC appears and is enabled.
7. Inspect the log if it is absent. Close X-Plane, open Log.txt in the simulator root and search for XPUIPC, win.xpl, error or failed.
8. Start the external application. Select its XPUIPC or FSUIPC connection mode and test with a default X-Plane aircraft first.

A local application does not require X-Plane's general network-data output or XPWideClient. XPUIPC reads simulator data through X-Plane's plug-in interface.

XPUIPC X-Plane 12 install and upgrade notes

X-Plane 12 uses the same XPUIPC 2.0.5.9 package as X-Plane 11, but older XPUIPC builds should not be carried forward merely because they appear to load.

XP12 changed or removed some simulator datarefs, so an old build can remain visible in Plugin Admin while returning blank, stale or incorrect offset values. Install 2.0.5.9 cleanly, test a default XP12 aircraft and only then restore any documented custom mappings.

For a safe update or rollback:

1. Close both simulators.
2. Move the existing XPUIPC folder outside Resources/plugins. Do not leave a renamed backup containing win.xpl inside the plug-ins directory, because X-Plane may still scan and load it.
3. Install a clean 2.0.5.9 folder. Confirm that it loads before changing its configuration.
4. Merge only required custom offset entries. Do not overwrite the new configuration with an entire file from an older release.
5. Roll back by removing the new folder and restoring the saved folder. Keep the backup outside X-Plane until needed.

What if I keep X-Plane 11 and X-Plane 12 installed?

Give XP11 and XP12 their own complete XPUIPC folders and configuration files.

Do not point both simulators at a shared plug-in directory, and do not copy an edited XP11 offset file over the XP12 file without comparing the entries. Updating the XP12 copy does not require changing a stable XP11 installation; this also makes rollback independent for each simulator.

How do I connect XPWideClient from another PC?

XPWideClient 2.0.0.3 connects a remote Windows application to XPUIPC 2.0.5.9 running on the simulator computer.

1. Assign the simulator PC a stable private IPv4 address. A router DHCP reservation is preferable to an address that can change after a restart.
2. Configure the XPUIPC server address. In the plug-in's supplied XPUIPC.ini, use the simulator PC's LAN IPv4 address for the server-address setting when enabling remote access. Do not enter the remote computer's address.
3. Extract XPWideClient on the remote PC. Keep XPWideClient.exe with its supplied XPWideClient.ini; it does not belong in X-Plane's plug-ins folder.
4. Configure XPWideClient. In XPWideClient.ini, set the server address to the same LAN IPv4 address used by the simulator PC. The matching packages communicate on port 49000; the server and client port values must agree.
5. Allow both applications through Windows Firewall. Limit the permission to the private network and the XPUIPC/XPWideClient traffic on port 49000.
6. Start the software in order. Launch X-Plane and load a flight, start XPWideClient.exe on the remote PC, then open the dependent application.

Do not set the remote client to 127.0.0.1; that address means the remote computer itself, not the X-Plane PC. Do not forward port 49000 through the internet-facing router, and do not change X-Plane's unrelated UDP data settings to repair an XPWideClient connection.

If the connection stops working after a router or PC restart, compare the configured server address with the simulator PC's actual IPv4 address. Also confirm that the remote package is XPWideClient 2.0.0.3 rather than a client copied from a different XPUIPC release.

Do I need to edit XPUIPC offset mappings?

Standard supported offsets normally work without manual changes to XPUIPCOffsets.cfg.

Edit mappings only when the application or aircraft documentation identifies a specific X-Plane dataref, offset and data type. Back up the working file first, avoid duplicate offset definitions and merge custom entries into the configuration supplied with 2.0.5.9.

If 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; an aircraft-specific mapping or native connector may be required.

Why is XPUIPC not loading or connecting?

Log.txt and the exact installed path usually reveal why XPUIPC is not working.