Skip to content
X-Plane 5 min read

Does MobiFlight work with X-Plane 12, and how do I set it up?

Ian Stephens
In short

MobiFlight X-Plane 12 setup explained: install the plugin, connect a controller, map datarefs and commands, and fix common connection faults.

Yes. MobiFlight works with X-Plane 12 through MobiFlight's X-Plane plugin, which passes datarefs and commands between the simulator and MobiFlight Connector. For the simplest setup, run both on Windows, install the plugin in the active X-Plane copy, flash a supported controller, then map and test each input or output.

What does a MobiFlight X-Plane 12 setup require?

MobiFlight Connector is a Windows application, so a single Windows PC running both programs is the least troublesome arrangement. X-Plane running on macOS or Linux does not provide a native MobiFlight Connector application; a split-computer configuration introduces networking and should be attempted only after the hardware and plugin have been tested locally.

ComponentPurpose
MobiFlight ConnectorCreates configurations, flashes supported controller firmware and sends or receives simulator values.
X-Plane pluginProvides the communication bridge between Connector and X-Plane 12.
Supported controllerConnects switches, encoders, LEDs, displays, servos or other supported cockpit hardware.
Datarefs and commandsIdentify the aircraft systems that each input controls or each output displays.

Use a controller listed as supported by the MobiFlight Connector release you install. Conventional yoke, pedal and throttle axes are usually easier to configure directly through X-Plane's joystick settings; MobiFlight is particularly useful for cockpit switches, annunciators, encoders and instrument outputs.

How do I set up MobiFlight in X-Plane 12?

  1. Find the active X-Plane installation. If you have more than one copy, confirm which executable you actually launch. Our instructions for locating the active X-Plane 12 installation help avoid installing the plugin into an unused copy.
  2. Install MobiFlight Connector. Keep Connector in its own writable location rather than placing the application inside X-Plane's plugin directory.
  3. Connect and prepare the controller. Add the board in Connector, flash the MobiFlight firmware when prompted, and define the attached buttons, encoders or output devices. Flashing replaces the existing controller program, so preserve any unrelated project first.
  4. Install the X-Plane plugin. Use MobiFlight's plugin installation control when provided and point it at the correct X-Plane root folder. For a manual installation, copy the complete supplied plugin directory beneath X-Plane 12/Resources/plugins/; do not copy only an individual binary or create an extra nested folder.
  5. Restart X-Plane. Plugins are loaded when the simulator starts. Load an aircraft and inspect X-Plane's Log.txt if the MobiFlight plugin is absent or reports a loading error. Our guide to plugin placement, loading and Log.txt troubleshooting covers this part in detail.
  6. Connect MobiFlight to X-Plane. Select the X-Plane integration in Connector and confirm that it detects the running simulator. The MSFS WASM module and SimConnect events are not used for X-Plane.
  7. Create one test mapping. Assign a simple button to an X-Plane command, or assign a readable dataref to an LED or display. Run the configuration and verify this single item before wiring the rest of the panel.
  8. Save an aircraft-specific configuration. Label mappings clearly and keep separate configurations where aircraft expose different custom systems.

Which X-Plane datarefs and commands should I use?

Use commands for actions and datarefs for values or states. A push-button, encoder detent or switch action is usually best mapped to an X-Plane command because the aircraft can then process the action normally. Use a writable dataref only when the aircraft expects that value to be written directly.

  • Momentary input: use a command with press and release behaviour where applicable.
  • Rotary encoder: use separate increase and decrease commands when the aircraft provides them.
  • LED or display output: read a dataref representing the actual system state, not merely the physical switch position.
  • Selector or analogue value: use a writable dataref only after confirming its range, units and array index.

Commands do not contain a persistent value, so they cannot directly drive a display. Datarefs may also be read-only, and writing to one can appear to work briefly before the aircraft's own systems overwrite it. Our explanation of how X-Plane datarefs and commands behave covers those distinctions.

Default aircraft often use standard sim/ references, while complex add-ons commonly publish custom ones. Load the intended aircraft before searching because custom references may not exist otherwise. You can find and monitor aircraft-specific references with DataRefTool, then watch the value while operating the control in the virtual cockpit.

Does MobiFlight need XPUIPC in X-Plane 12?

No. With MobiFlight's supported X-Plane plugin, XPUIPC is not part of the normal setup. Retain an additional interface only when importing a legacy configuration explicitly designed around its offsets; installing multiple bridges without a specific need makes connection and mapping faults harder to isolate.

Why is MobiFlight not connecting to X-Plane 12?

SymptomLikely cause and fix
Connector cannot see X-PlaneConfirm the simulator is running, the MobiFlight plugin is installed in the active X-Plane copy and local security software is not blocking communication.
Plugin is missing from X-PlaneCheck for an extra folder level, an incomplete extraction or an incompatible plugin binary. Read Log.txt after a fresh simulator start.
Input does nothingMake sure the configuration is running and the reference exists for the loaded aircraft. Try a standard X-Plane command to separate a connection problem from an add-on mapping problem.
Control moves and immediately returnsThe dataref may be read-only or continuously managed by the aircraft. Use the corresponding command or the aircraft's documented writable reference.
Display stays at zero or freezesCheck the dataref name, data type, array index and any MobiFlight transformation. Monitor the raw value before formatting it.
A button acts twiceThe same control may be assigned in both X-Plane and MobiFlight, or both press and release may trigger the action. Remove the duplicate binding.
Controller disconnects under loadCheck the USB cable and power arrangement. Do not drive high-current lamps, motors or numerous outputs directly from a controller pin; use suitable drivers and external power where required.

A useful diagnostic sequence is to test one standard command in a default aircraft, then one readable output dataref, and only then move to custom add-on systems. If the standard tests work, the plugin and controller connection are sound and the remaining fault is in the aircraft-specific mapping.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members