MobiFlight Community Support

Welcome to the forum for MobiFlight! Feel free to reach out to the community in case you have questions, issues or just want to share great ideas or details about your latest home cockpit project.

You like MobiFlight? Donate via PayPal and support the MobiFlight development. Thanks! 

05/03/2024 - This forum is read-only

The community support for MobiFlight has moved exclusively over to our Discord server. Register for free and enjoy more interactive functions like image and video upload, voice chat. More than 7,000 registered users around the world make it a great experience!

See you on our MobiFlight Community Discord server.

A HUGE Thank You to everyone who participated in the forum, especially obviously to Pizman and Stephan who did an outstanding job over so many years providing an incredible service to the MobiFlight community.

The forum is still providing a lot of good content, hence we keep this information accessible.

icon
Avatar
fazli
Posts: 91
hi,
i was almost 3year setup my home cockpit b737 pmdg using mobiflight. last night the problem come out after i configer gleare wing fire warn captain side. mobifliht can't open .i try control alt del. i cant see the software mobiflight run. any suggestions solved this problem. many many configure i create. i worried
mcp efis thorttle mip gone or lost

1.how to save or backup configure
2.how to install and uninstall correctly
3.how to fine file mcc

my setup pc
main pc
p3dv4
pmdg b737
fsuipc wide fs

second pc
wide client
fd guage
air manager
mobiflight.

tq.
regard,
fazli
2019-07-13 07:28
Avatar
StephanHo
From: EDDG, Germany
Posts: 1867
Supporter
Hi fazli,

do not despair!

The most important thing you should have is a backup copy of the MobiFlight .mcc file that was still working properly BEFORE you made any changes.

The .mcc file that MF now wants to load, you should rename and then start MF. MF then starts without the configuration file. Via the menu FILE you get the last working .mcc-file.
Now MF should run as before, so before you made any changes.

If you do not have a backup, it gets more complicated.
Make a copy of your last active .mcc file (the one MF does NOT start with).
Rename the last active file.

To edit the .mcc file you should use an editor like Notepad ++.

You have to deal with the structure of the .mcc file. The structure is strictly logical and distinctive.

It is structured like this:
<? xml version = "1.0" encoding = "UTF-8" standalone = "yes"?>
<Mobi Flight Connector>
<Outputs>
...
</ Outputs>

<Inputs>
...
</ Inputs>
</ Mobi Flight Connector>


As a reminder: Outputs are all data read by the simulator, ie instruments, annunciators and displays. Inputs are all inputs for the simulator, ie switches, buttons, rotary switches, encoders etc.

Now you should know what you have changed in the file. Were it inputs, outputs or both?
If you have changed only inputs, you search the entries under Inputs, which you have installed afterwards and remove these entries.
An input entry looks like this:

<config guid = "d7885b02-85fe-40ef-9730-en7e9a6be611">
<Active> true </ active>
<description> AUTOBRAKE RTO </ description>
<settings msdata: InstanceType = "MobiFlight.InputConfigItem, MFConnector, Version = 7.5.2.0, Culture = neutral, PublicKeyToken = null" serial = "FSX 01 / SN-b59-4d4" name = "AUTOBRAKE RT0" type = "Button" xmlns: msdata = "urn: schemas-microsoft-com: xml-msdata">
<Button>
<onPress type = "EventIdInputAction" eventId = "70092" param = "0" />
<onRelease />
</ Button>
<preconditions />
</ Settings>
</ Config>

An entry is removed if everything between <Config guid ...> to </ Config> has been removed. The structure of the outputs is similar. If you made changes here too, then remove these entries as well.

After removing the entries you save the file under a new name.
Now MF should start.
So start MF without a file and manually load the file from which you removed the entries.
If MF can load the file without error message, it is without error. You should then save it under a new name.
Now you get yourself from the original file again the entries that you have previously deleted, builds them into your working file (on input and output pay attention), store them and load them into MF. If MF displays an error message, this entry has an error. Write down the error or the entry, delete it from the file and take the next entry.

Now the game repeats itself. Error message no, then ok, next entry. Error message yes, delete entry and note, save, next entry.
So you find all errors in the entries of the configurations.

If you have a backup, you start with it and get from the non-working file, the individual entries that you have added later. Make sure that you do not overwrite your original files.

Although everything is a bit cumbersome, but unfortunately it is not.
I wish you success!
Grüße,
Stephan (Time: UTC+2)
2019-07-13 11:22
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Short Hint....

As Stephan said... the most profitable way is to have always backup files.... Not only ONE .... Simply create a backup History ... so every building Step got a own old Backup File.

For research (if no backup is there and you must repair the file) i use a little other system like Stephan.
If you can locate the issue ( for example in the last 10 Configs you add last seasson then its more easy..... If you have no indication then do the follow)


I work with the "half-life" Logic .... So i split the File over and over divide through 2..... One Test eleminate 50% of possible issues

Example:
Edit the File and delete ALL Input Config Lines .... "Save AS" a new file and test it ! .....
If no Error occure then the issue is in the Input section ( You still removed.)

If a Error happen then there is a issue in Output Section garanteed.... BUT It can Also another one in Input section we still removed.
In THAT Case you should open original file again and recheck the other Side.... So you now remove all Outputs and Save AS again to another file.
Test Again : No Issue --> confirm that Problem is Only in Output Part .... Another Issue tell us Problem is in BOTH Parts. ( So minimum 2 issues or more)

Normaly you have only one Problem.... So this test show you the location ( Input or Output) with just less then 5 Mins of testing .....

THEN you do the same logic again.....
Example: You find out with first testing the issue is in INPUT Section (e.g) ...
Now spllit all your Inputs into 2 Halfs.... For example 60 Inputs overall .... So remove the upper 30 configs.
Test Again : No Error say problem is in other half .... Error say Problem is in the current half garanteed ( and also maby in the other)
In that case again test the other half to confirm issue is in both parts or only in one .

***************
Summary....
With this logic you need in perfect situation only 1 testrun (Or two if you unlucky) to eliminate 50% of configs....
So In example a Full Cockpit File with 1000 Config Lines....
Test 1: 500
Test 2: 250
Test 3: 125
Test 4: 64
Test 5: 32
Test 6 16
Test 7: 8

Thats Much more Faster as testing every single line ...... In whorst case with line by line test you need 999 Tests to find out the problematic config was the last one :-)

Hope you understand what i try to explane !
Good Luck !
2019-07-13 14:42
icon