
If you’re having an issue, don’t worry. Many problems are easy to fix, and we're here to help if you're still stuck!
Support cases usually involve a few common issues. We've covered these below, so please take a look.

Sometimes a glitch may be temporary. Try the following:
Failing that:

This indicates:
A good connection to the device
Aircraft Profile is loaded
The data is not coming through from Flight Simulator

Communication with the simulator is provided by a file called a WASM module.
This file is supposed to be located in the Community folder of either FS2020 or FS2024.


If the installation fails (simulator not detected, etc.), you can manually copy the module from your MobiFlight installation folder into your MSFS Community folder.
X-Plane is automatically detected by MobiFlight when it is running. We have not had any reports of failed connections to X-Plane.
Communication is provided by FSUIPC.
FSUIPC.exe must be running while the simulator is running. By default, this happens automatically, but in case of a corrupted xml file, FSUIPC must be started manually. You can see it running in the system tray.

A display will flicker when it is being fed two inputs simultaneously. It tries to display both numbers, and switches rapidly between them.
This occurs when conflicting aircraft profiles have been loaded into MobiFlight, most commonly through the use of the "Merge" command.
"Merge" should only be used where the pilot has multiple devices which all use MobiFlight. Further information is given at Managing Multiple Devices.
This issue can be resolved by either of the following options:
The guaranteed way to correct a problem with an Aircraft Profile is to clear it and start again.
Users who are familiar with MobiFlight can scroll down the Output tab on MobiFlight and look for duplicate entries. It is usually an entire Aircraft Profile which bas been merged (appended) onto an existing one

This occurs when duplicate aircraft profiles have been loaded into MobiFlight, most commonly through the use of the "Merge" command.
This is the same cause as Flickering Displays, follow those steps to resolve it.

If you have clicked the "AutoRun" option (the light bulb goes yellow) then when you run MobiFlight it will automatically minimise itself to the system tray.

There are two ways to prevent this behaviour

Or
In settings, untick the "Minimize to system try on AutoRun" option


By default, the V/S display only comes alive when the V/S mode active. Pushing the V/S button will activate the display.

On the MobiFlight settings menu, deselect Automatically perform retrigger-action with "Run".
(We have opened a issue https://github.com/MobiFlight/MobiFlight-Connector/issues/1856 to fix this on GitHub)

On the MobiFlight settings menu, deselect Automatically perform retrigger-action with "Run".
(We have opened a issue https://github.com/MobiFlight/MobiFlight-Connector/issues/1856 to fix this on GitHub)


If you're still unable to use your hardware, the problem is likely related to the Aircraft Profile, not the hardware connection.
This indicates the firmware on the device has been overwritten.
Visit Troubleshooting Compatible Devices to solve this issue.

If you're still having a problem, please contact Support and we can help you solve it.
It would be helpful to know: