MobiFlight Community Support

I'm new to Mobiflight. Was wondering does Mobiflight work with Steam FSX? I''m asking, because I have been unable to get the FSUIPC status symbol to turn green from yellow. The Arduino symbol does turn green and firmware update seems to work fine. I'm using Arduino Mega 2560 r3 (Tried two different boards with same results). I'm using Windows 10 and I have tried launching both FSX and Mobiflight with admin rights. Both FSX and Mobiflight are setup under C:\ location and not under c:\Program Files. I have a registered copy of FSUIPC, using version 4.974 and see it as an add-on in FSX. How does Mobiflight detect FSUIPC is running? Was wondering if you had any suggestions what to try next?

Thanks you

Below is example from log window in Mobiflight with FSX running first and then start Mobiflight

5/19/2020 11:46:52 PM(809): ExecutionManager.TestModeStop:Stopped test timer
5/19/2020 11:46:50 PM(744): MobiflightModule.connect: Connected to Default at COM17 of Type MobiFlight Mega (DTR=>True)
5/19/2020 11:46:50 PM(704): No updates necessary. Your version: 7.8.2.0, Latest version: 7.8.2
5/19/2020 11:46:38 PM(223): Checking for updates
5/19/2020 11:46:38 PM(8): MobiflightModule.disconnect: Disconnected MobiFlight Mega at COM17
5/19/2020 11:46:35 PM(839): MobiflightModule.connect: Connected to Default at COM17 of Type Arduino Mega 2560 (DTR=>True)
5/19/2020 11:46:35 PM(543): MainForm() : Logger initialized Info

Hi Welcome !!

In theory this should work. Also other users here use FSX/SE without problems.

For mobiflight it is no difference whatever you use FSX, FSX_SE, P3d v1-v5 ior Xplane.
Mobiflight just need a correct working FSUIPC in the right Version ( or XPUIPC for Xplane)

Please check if FSUIPC work fine.... Maybe reinstall it.... Check if Tab is available and you can open FSUIPC in the Sim.
Another idea is to run Sim and Mobiflight in ADMIN Mode (Not know if this effected the situation but lots of times this solve other problems)

Please report experience !

Hello Pizman,

The FSUIPC tab is available in drop down in FSX and works fine for setting up joysticks and buttons. I also went ahead for due diligence and redownloaded the FSUIPC from site and cleared and reinstalled and still works in FSX, but still no joy in mobiflight, still yellow warning. I also tried running as administrator for both apps, still not sensing, getting yellow warning in mobiflight. Are you able to help me understand how mobiflight detects FSUIPC? Is there any other programs that can cause similar issue, that conflicts?

Hi again.

Badly i not know the code part and how mobiflight handle it. In theory it is no process cause its a part (DLL) of the e.g. FSX.EXE .
Whatever.... If other users work with it, it should also work for you.

Another idea for testing is to disable your firewall for a short test run.
If it work then you can create a entry to "open" the needed parts.

Just a idea.... I don´t know if thats the solution !

Hello Pizman,
I think I found the solution, but not sure exactly why it was an issue. I had named the folder where I saved Mobiflight that same name when I setup the program. I decided tonight to change that name to MobiflightComm and after I made that change the FSUIPC status started working? I tried changing back and broke again so seems to be the issue. Not sure why, but will give it a few days and see how it goes. Thanks for your help and taking time to answer my post.

Just to confirm..... The problem is if the folder you install Mobiflight got a special name ?? That would be crazy.

If yes please tell us exactly the folder struckture when the issue occures.....
So for example you install it in c:/mobiflight or maby in c:/blabla/lala/lulu/Mobiflight.

Please give me a exact guide to reproduce the issue.
Then i will check it !

Hi,

Yes that seems to be my issue. I originally had Mobiflight setup in the following path:

C:\FSX_Add\MobiFlight

When I changed it to the following path it started to work:

C:\FSX_Add\MobiFlightComm

I tested again today switching it back to the original name and it again would not see FSUIPC in the status window (Yellow indicator) and would only turn green after I switched it back. Tested one other name, again seems to work fine, just does not like using MobiFlight.

Oneaokguy

Strange Thing !

I could not reproduce. Whatever I use P3Dv4 ( and in the past FSX) . I not remember how i call the folder in the past. today it called "Mobiflight" and work.
I also renamed it to "MobiFlight" (Big "F") and it work.

So the main Problem is not reproduceable whatever i belive in you it happen on your system.

@ ALL
If there is a user here with FSX STEAM ( Or FSX) ..... Can somebody confirm the issue or much better can somebody confirm its not a issue and only happen for "oneaokguy"

Hi,

filenames in Windows are not case sensitive.
The entries in the registry should not be neglected. In this respect, you should not simply rename a directory or move the files to a new directory, but reinstall MF there and delete old directories after they have been backed up.

Hi StephanHo,

Thank you for taking the time to reply to my post. I honestly had not considered this, and in retrospect, might agree that I have not been handling this aspect of the install correctly. When you say registry, are you referring to the PC registry or a config file in the directory where the Mobiflight exe is ran? I'm trying to figure out if my registry on my PC might need some clean-up since this revelation. Is there a spot on your site that discuss the install method so I can review to make sure I follow the proper procedure? I looked and was unable to locate like a blind bat and I also looked for a Readme file in the install?

Thanks again

Hi Oneaokguy,

no, there is no information file for a correct installation. This is also not necessary. You download the MobiFlight.exe and run it. Please make sure that the execution takes place under admin rights if the simulator program or the addons have been installed with it. The .exe unpacks itself in the directory in which it is started, which means that MobiFlight is installed in this directory. MF should not be installed in a directory in which the access rights are managed restrictively by Windows.
Basically, only system operating system software belongs to the system partition (C:\). The software for the simulator and the addons should be installed on a different partition (d:\, e:\ etc) so that there are no conflicts here. For PC systems that only have one partition (C:\), a separate folder for the simulator and the add-ons should be created in the root directory (e.g. C:\ Flightsim \).
If you install MF again, the entries in the system registry will be rewritten to the new installation. External intervention is therefore not necessary and cleaning up the registry is also not necessary because of MF.