Hello Guys,
I am not asking for any help now, I just want to tell you the end of the story. I made another remote control session yesterday and still couldn't find any explanation, I was turning crazy...
Initial conditions:
- FSX-SE clean new install. Only FSUIPC and my EasyFMC Mobile add-on installed on top of FSX-SE installation.
- I provided my friend a small software I wrote that uses FSUIPC to indicate the FS location and information about the currently loaded aircraft: title, atc flight number, atc tail number, atc airline.
- UAC set to the lowest level (less secure, but less potential problems)
- All traffic set to 0% in FSX settings.
Test conditions:
- Each modification of aircraft.cfg/panel.cfg was made when FSX was stopped
- The text editor was closed each time a modification was mde
- FSX was restarted each time to see the effect of any change
Tests:
1) I checked the registry to make sure the install path in the registry was the path I was using to run FSX. I also created a desktop shortcut myself to be 100% sure the FSX I was launching was the right one. Anyway, there was no other...
2) I did my usual test: remove the [VCockpit] section (Yes Rob, no s, there is only 1

) from panel.cfg and launch FSX.
First bad surprise, even if the [VCockpit] section was removed, all the VC gauges were there, alive and operational.
3) Frustrated, I changed the aircraft.cfg.
From memory, the [fltsim.0] aircraft title is "Boeing 737-800 Paint1" and it is "Boeing 737-800 Paint2" for the second variant [fltsim.1]. I changed the second variant title to "Boeing 737-800 Paint1" to intentionally cause a dupliate title error in FSX. I restarted FSX and... no error message.
Not only I had no error message, but I selected the second variant in FSX, my utility was showing the aircraft title: Boeing 737-800 Paint2
Where could FSX find this?!? FSX was using an aircraft that didn't exist any more !!!
I pushed the test by searching in SimObjects and all subfolders for any file that contains "Boeing 737-800 Paint2", I didn't find any !!
I started to believe the text editor I was using was saving the modified files at the wrong place, so I checked the file date and opened aircraft.cfg with Notepad, everything was ok.
4) The only test that worked was when I renamed the "panel" folder into "panel.eric", then I changed the panel line in aircraft.cfg from "panel=" to "panel=eric".
This time, the VCockpit gauge removal finally appeared, but this worked only once. Any subsequent change to the panel.cfg file was ignored.
5) My friend moved the Texture.3 to texture.6 to a trash folder. When restarting FSX, the variants that were using these textures were not listed any more. This shows FSX ignores the aircraft.cfg modifications but doe not ignore the presence of texture files. I don't know what it means...
6) After I gave up and stopped any test, I asked my friend to do the same test with fs9. He reinstalled fs9, made a change in a panel.cfg, and same thing happened: the change was ignored.
The PC behaves as if there was a big disk caching that uses the files in cache instead of using the ones on disk. Any change on the file on disk is ignored (as if it was read from the cache instead) until a folder structure change occurs. I know we probably all use disk caching, but when a file is written, the cache is updated. Even if it was a possible explanation, how to explain the file appears correctly modified in the text editor and not in FSX.
After all these test, I really have no explanation. My friend plans to totally reformat his PC and reinstall a fresh Windows 10. I couldn't help him more...
Eric