FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: vc-10man on October 17, 2014, 03:01:49 pm
-
For some inexplicable reason, my GSX has gone pear-shaped. Tried deleting the Virtuali folders from relevant directories; tried deleting the Scenery Index and Facilities, and then re-installed but I keep getting an error message something about patched vehicles_airport restoring from backup,and then when I attempt to ask for GSX Services, back to same error about no Afcad at every single airport even though Addon Manager and Couatl is showing in the drop-down menu except the Customise option for airport
-
Again, be sure you remove THESE folders, when FSX is not running, of course, maybe after a Windows restart:
C:\ProgramData\Virtuali\Couatl ( NOT %APPDATA%\Virtuali!! )
C:\ProgramData\Microsoft\FSX\SceneryIndexes
restart FSX, wait for both FSX and GSX caches to regenerate and, if it's still giving you errors, enable Logging in the Troubleshooting section of the GSX Settings menu, and post your Couatl.LOG file.
-
Tried those fixes. Still same error red banner at the top; still do not see an option from the drop-down to 'Customise this parking place'.
Trying to attach the Couatl. Log file but annoyingly keep getting flagged that cannot attach even when it is a txt file. This gets dafter and dafter. So, cannot attach.
-
Trying to attach the Couatl. Log file but annoyingly keep getting flagged that cannot attach even when it is a txt file. This gets dafter and dafter. So, cannot attach.
ZIP it
-
Here it is.
-
Do you have the Addon Manager menu under the FSX "Addons" menu ? The look seems to indicate it's not running, possibly because the antivirus has blocked it. If this is the case, do the following:
- Go into Control Panel, Uninstall GSX and reply YES to the questions "Do you want to remove the Addon Manager ?" and reply YES to the question "Do you want to remove the Couatl script engine ?"
- TURN YOUR ANTIVIRUS OFF.
With the antivirus still disabled, reinstall GSX
- BEFORE launching FSX, configure the antivirus to exclude the following files from scanning:
YourFSXFolder\bglmanx.dll
YourFSXFolder\fsdreamteam\Couatl\Couatl.exe
- Now you can turn your Antivirus on, and launch FSX
- Note if FSX asks permission to run the Addon Manager and the Couatl programs, reply YES to both
- When FSX loads, check if you have BOTH the "Addon Manager" and the "Couatl powered products" under the "Addons" menu.
-
Thanks for that, Umberto. Will attempt that and report back.
-
Did exactly as instructed, AV turned off, etc, etc
But did not get that permissions flag up. And in the drop-down menu Add-ons Menu, I see the 'Add-on Manager' and 'Couatl powered products', but no option to 'Customise This Parking Position' and when I ask for GSX services, Ctrl+Shift+12, I still get that red error about the Afcad.
-
Consider this now closed as I have managed to resolve it myself.
QED!
EDIT: Thought it had been resolved. Only resolved for FSDT airports only, anything else, same old red error flagged message about Afcad.........
Back to Square One!
-
Can you provide with an updated Log file, after your first fix ?
-
Here you are, as requested. Sincerely hope this can be resolved.
-
The log file shows that your scenery.cfg under C:\ProgramData\Microsoft\FSX contains just some FSDT and some FlyTampa airports, and nothing else.
It's possible you are running FSX under some Compatibility mode ? This would change the location of the scenery.cfg file. Even another add-on running in Compatibility mode might cause this.
Also, if your scenery.cfg has an error, perhaps only part of it is read.
-
Thank you for that explanation.
Which explains why when I tried to install FlightSim Commander, it would not read the Scenery.cfg.
Is there a way to restore/repair it?
-
Which explains why when I tried to install FlightSim Commander, it would not read the Scenery.cfg.
You would have made my work easier if you said something like this:
"why BOTH GSX AND FlightSim Commander can't read my scenery.cfg anymore ??"
Were you worried that, since it's would have been clear your question didn't have anything to do with GSX, and it's just a generic question about fixing a problem with the scenery.cfg, you wouldn't get any help ?
First, you must understand if the problem is the scenery.cfg itself being corrupted, or it's just your system using the wrong one, this can only be checked by looking at it.
-
Yes, in a way, as FlightSim Commander is not related to FSDT products, I saw no point in broaching it here.
However, if my scenery.cfg is corrupted, how is it that (a)I do not get a scenery error flag when FSX loads, and(b) how come I can select any or all the airports including all my non-FSDT add-ons without any problems? Surely, logic dictates if the scenery.cfg is corrupted, then I would not see any of those airports. Or maybe I have this concept wrong?
-
However, if my scenery.cfg is corrupted, how is it that (a)I do not get a scenery error flag when FSX loads, and(b) how come I can select any or all the airports including all my non-FSDT add-ons without any problems?
There might be two possible explanations for this:
1) FSX doesn't use the standard Windows routine to read .INI files, but has its own parsing routine, which has been made more robust against syntax errors, so it's able to just skip the problematic area, instead of refusing the read the file or, probably, the sections after the corrupted one.
Both GSX and (likely) Flightsim commander, use standard (provided either by Windows or by some standard library) .INI parsing routines, that are more formally correct, so they treat as errors what FSX is able to accept.
OR
2) BECAUSE of FSX is running in Compatibility mode, it's reading from another scenery.cfg file, instead of the one running under C:\ProgramData\Microsoft\FSX
Again, not possible to know without having a look at your scenery.cfg and checking if it's really corrupted.
-
Thanks for that explanation.
Here's the Scenery,cfg attached.
-
Your scenery.cfg is fine, so I think your FSX is looking at it in a different folder than normal. As you can see in your scenery.cfg, the layer number and the sceneries don't match the layer numbers in the Couatl.LOG
Do you have perhaps ANOTHER scenery.cfg file in this folder ?
C:\Users\YOURNAME\AppData\Local\VirtualStore\ProgramData\Microsoft\FSX
That would indicate a permission problem with your user account, like changing permission before/after installing FSX or installing some addons.
-
Thanks, Umberto. You may have found the problem for me as I looked in C:\Users\MyNAME\AppData\Local\...............but no VirtualStore folder. Wonder where that disappeared to?
-
Well, not having the Virtualstore folder it's not really a problem, it's only used by programs that TRY to write into C:\ProgramData but, for some reason, don't have permission to do that, so the OS redirects writes into C:\ProgramData to C:\Users\YOURNAME\AppData\Local\VirtualStore\ProgramData\
Have your tried searching the WHOLE hard drive for another scenery.cfg ? Be sure to include all files and folders, even the hidden ones, in the search.
-
Oddly enough, just after I had posted my last reply, I did find a Scenery,cfg, which I did not delete but re-named so as not to lose it, sitting in :
C\:Users\MyNAME\AppData\Roaming\Microsoft\FSX folder
Thinking it was indeed odd, I then fired up FSX expecting to see an error flag about missing sceneries. Instead, I got a message that eSellerate had detected a hardware change and had to go though some Activation screens, and the FSX loaded to the default Trike. But I still do not see the 'Customise airport positions' option from the drop-down Addons menu that I get only at FSDT airports, e. LSZH.
-
Finally, finally, managed to sort this out.
All up and running and working as should be.
QED #2