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)
