FSDreamTeam forum
FS9 support => Chicago O'Hare for FS9 => Topic started by: hlm65 on December 29, 2008, 03:15:38 pm
-
Just updated AES to last 1.99 release and got a red window "AES Deactivated-Scenery protection active" at KORD...
Any idea ?
Many thanks in advance.
-
You don't have the latest version of KORD. Download and install it.
-
So, do you guys - FSDreamTeam - have to update your software and installer everytime Aerosoft comes out with a new release of AES? If so, that's gotta be a pain in the butt. Thanks for putting up with it and providing us with timely support.
Bob
-
No, he had an old version. I installed KORD months ago, and AES 1.99 works great.
-
So, do you guys - FSDreamTeam - have to update your software and installer everytime Aerosoft comes out with a new release of AES?
We only had ONE update, which happened several months ago. All the subsequent version were all compatible. The original poster probably had the very first KORD release.
-
OK thanks, now AES 1.99 works and FSDT too...pity that its seems overlayed to the default O'Hare ! Note that I did not do any change other than installing AES and reinstalling KORD...
See the results in the attached screenshot...
Any help again appreciated and Happy New Year!
[attachment deleted by admin]
-
OK thanks, now AES 1.99 works and FSDT too...pity that its seems overlayed to the default O'Hare !
Yes, your screenshot shows there's a default scenery popping out. Which might not be the MS default scenery, but an AFCAD that came with a traffic package, which is only good for the default O'Hare.
Try to use the AFCAD program, search for all AFCAD at KORD, and check there are only two: the MS default, which is named something like AP*xxxxx.BGL and should reside into the scenery\world\name, and ours, which is located in the fsdreamteam\ohare folder.
If you find other AFCADs, delete them all.
-
This is a FAST reply !
Checked: and I have AF2_KORD.bgl (dated 12/06/2008, 75 KB)and APPR_KORD.bgl in FSDreamteam/Ohare folder then the stock one (check with AFCAD2 and with AFDScan).
So it seems that i don't have any other conflicting AFCAD for ORD...The active BGL from AFCAD seems the AF2_KORD...
Any further hints ?
Thx in advance.
-
It's strange, because something that looks like AFCAD lines in default style IS popping out in your screenshots.
Could be you once had the Simflyers scenery, and haven't uninstalled properly, so some stray .BGL is still somewhere ?
-
I had the Simflyers old scenery but deleted it completely when first installed your scenery...always worked well till this reinstall...
-
i'm sorry, but other than confirming that, from your screenshot, the problem is clearly caused by another scenery (see the double hold-short zones, for example), so it doesn't have anything to do with any of our products.
Just as a quick check, what happens if you delete the AES Base layer ?
-
Hmm, deleting the BASE AES Layer doesn't change anything, but I tried to change the season (eg, from winter to spring) and I don't get any longer the deafult hold lines. If changing back to winter...I get them again. this is VERY strange because this never happened before !
-
Further checks have revealed that this "surfacing" of a default texture affects also the ILS location of Rwy 14L (it applies the default one) even if the current AFCAD is correct. This strange thinh happens near the 14L threshold only.
Any cue ?
-
Nothing to add, is surely caused by another scenery.
-
Interesting, I have NO other scenery for the Chicago area, only FSDT.
So, probably there's something in FSDT causing this...
-
Interesting, I have NO other scenery for the Chicago area, only FSDT.
From the screenshot you posted, you obviously have, it's just you haven't found it yet.
Usually, this is a result of removing a scenery which places stray bgl in several places, that is easy to miss if the scenery doesn't come with a proper uninstaller.
A scenery might come also not as a "scenery", but also as an AFCAD support file for a traffic package, so it's not immediately obvious were it is.
So, probably there's something in FSDT causing this...
Obiously it's not, otherwise everybody would have it.
-
What kind of "stray" bgl could be, name some, if not it is impossible to check !
And I never installed any other AFCAD for ORD, exceèpt the old Simflyers whcih was completely deleted.
-
Could it be this one the culprit :
dem38_usap_chicago.bgl ?
-
It might, I don't have it in my FS9 folder, so it's not part of the default scenery. From the name, it looks like it's a mesh file, and meshes don't follow the layer priorities, meaning they'll always show up if there are no higher res meshes for that area. You can try renaming the bgl to another extension, and restart FS9.
-
OK, it seems (at lesat from a couple fo tries) that this was the cause for the strange "surfacing" of the default AFCAD around 14L. Changing season to winter will not have the default hold lines appearing, which seems OK. The only thing is that the GS for 14L still seems misplaced (a touchdown will occur before the displaced threshold), but this may be easily cured moving the GS "antenna" in the proper place with AFCAD2. Thk for the help !