FSDreamTeam forum

Products Support => Louisville KSDF Support FSX/P3D => Topic started by: chasensfo on November 26, 2020, 04:05:32 am

Title: Did the last update do somehow place FSDT sceneries below default?
Post by: chasensfo on November 26, 2020, 04:05:32 am
Hey guys,

I was having no problems with my FSDT scenery until the last large update I did after putting off updates for a while. Now, SDF, HNL, and all my FSDT sceneries (except IAH\LAX) for some reason have default scenery showing over them, with the AI traffic following the default ADEX, custom ground textures covered, and of course all the default buildings. I'm very familiar with ADEX and the usual causes for this issue and have fixed it many times in the past, however, this issue happening all of a sudden to most of my products is very frustrating as it can't be a coincidence that after a large update suddenly my scenery is all being bled over. Now, I have tried the usual ways to fix this, creating exclusion boxes for default objects and double checking ORBX and other directories for conflicting scenery, but nothing is working. This is very bizarre, as I've never been stumped trying to delete default scenery bleed-overs. I even went as far as to delete the stock SDF\HNL\OGG\KOA\LAS ADEXs to test, and somehow, the default scenery is still bleeding over! Even with the "APX" default ADEX file deleted from the root scenery folder! How is that even possible LOL, I thought that was the default airport's data? I ran the ORBX vector tool just in case, obviously didn't make a difference.

Any idea why this might be happening? As I said, I did NOT install any files that had anything to do with any of these airports, nor did I update my ORBX products, so I do not understand how so many airports would corrupt at once. GSX is also on the fritz when I use these airports. The ground crews about 50%+ of the time (on any aircraft) connect and get all the way to the point of asking what pushback I'd like, then they just sit there and nothing happens once I've dropped the brake. Reloading again and again doesn't fix it. This doesn't happen at airports outside of the FSDT airports with the bleed overs, GSX works fine at FlightBeam, ORBX, default, ect airports. But then the steering pin will be removed even though GSX is reset and I have to go and figure out with each model how to simulate fixing that issue so I can taxi after giving up on a GSX pushback LOL.

Did ignoring several months of updates just mess up the sim? Seems improbable.

https://i.postimg.cc/1tgbDZdn/2020-11-25-18-30-45-159.jpg (https://i.postimg.cc/1tgbDZdn/2020-11-25-18-30-45-159.jpg)

https://i.postimg.cc/mgXdj5CQ/2020-6-18-6-7-31-175.jpg (https://i.postimg.cc/mgXdj5CQ/2020-6-18-6-7-31-175.jpg)

https://i.postimg.cc/jjDMF44B/2020-6-18-6-15-41-222.jpg (https://i.postimg.cc/jjDMF44B/2020-6-18-6-15-41-222.jpg)

https://i.postimg.cc/264Fscb9/2020-6-30-22-34-26-445.jpg (https://i.postimg.cc/264Fscb9/2020-6-30-22-34-26-445.jpg)

Title: Re: Did the last update do somehow place FSDT sceneries below default?
Post by: virtuali on November 26, 2020, 04:56:13 pm
You are omitting leaving out the most important information, which was:

- Which simulator you are using.

If you used to have P3D V4, but now use V5, all AFCAD files made for V4 will show bleed through, if not updated, because they were designed for a default scenery that has changed. We obviously updated them all, as soon as P3D V5 came out but, you MUST allow the FSDT Live Update to overwrite the AFCAD files, to get the new versions, which work with both sims.

If you refused to let the updater overwrite the AFCAD files, maybe because you made changes to them, you'll get the bleed of default objects, because your modified files are not compatible with V5 default scenery so, either you fix them yourself, or you must do your changes again, based on our latest version.
Title: Re: Did the last update do somehow place FSDT sceneries below default?
Post by: chasensfo on December 06, 2020, 04:01:58 am
I am using P3Dv4, so that shouldn't be the issue.
Title: Re: Did the last update do somehow place FSDT sceneries below default?
Post by: Dave_YVR on December 06, 2020, 09:45:34 am
Are you using an AI pack that adds its own airport files?
Title: Re: Did the last update do somehow place FSDT sceneries below default?
Post by: virtuali on December 07, 2020, 08:39:30 am
I am using P3Dv4, so that shouldn't be the issue.

Then it's just a matter of other sceneries in conflict. We don't change the Scenery Library order, but if you install other stuff, or use 3rd party utilities to manage the Scenery Library, anything can happen.

The most common cause of conflicting sceneries are the AFCAD that comes with AI Traffic products, which are supposed to enhance the default airport, but should be removed if you had an add-on airport.
Title: Re: Did the last update do somehow place FSDT sceneries below default?
Post by: chasensfo on December 10, 2020, 08:18:27 am
No, I'm actually an AI traffic developer and all my AI is manually installed, I don't use any packages including AIG OCI, just traffic.bgls I compile myself, no ADEX files. I have even searched my whole P3Dv4 directory for KSDF, KORD, ect and come up with nothing outside of the FSDT files.

Well I'm not sure, because I hadn't installed anything new. My FSDT sceneries were all working fine, then I ran a big update as I had skipped for a while, then all of a sudden all my airports except LAX have bleed over that creating an exclude box for default objects doesn't fix. Elevation issues also at some of them. Ran ORBX vector, deleted the stock airports, no change. There was not a single file installed between the update and me finding this issue.

No issues with Flightbeam, ORBX, ect, just my FSDT airports. And almost all of them! LOL. I've been using your products for about a decade, maybe more, whenever they first started coming out. Never had this happen.

https://i.postimg.cc/K8qd4R6p/2020-12-8-21-32-41-98.jpg (https://i.postimg.cc/K8qd4R6p/2020-12-8-21-32-41-98.jpg)
Title: Re: Did the last update do somehow place FSDT sceneries below default?
Post by: virtuali on December 10, 2020, 11:08:53 am
I'm sorry but, I can only repeat and confirm this can ONLY happen when there's another scenery in conflict OR by a wrong order in the Scenery Library, which wouldn't matter much if you don't have any potentially conflicting sceneries, but if you have, the order might be important, although it's always best ( either to fix potential conflict but ALSO for performance reasons ) to remove the potentially conflicting sceneries anyway, and not rely just on the layering order.

As I've said, we don't set *any* order in our installer and we don't try to change it either.

When NO 3rd party utility to manage the order is used ( meaning there are NO <Layer> Command in ANY of the add-on.xml files of any scenery, which is how we DEFAULT TO, since we don't use it ), a scenery gets on top automatically if it's the last thing you install.

Instead, if you DO use a 3rd party utility to manage the Scenery Library, the order will then become controlled by you and that utility so, if you used one, just be sure our sceneries are on Top of everything else.

But as I've said, it's not always guaranteed that "just" having the scenery on top of the Scenery Library will fix ANY possible conflict. Some conflicts *require* the offending scenery to be removed so, if you have the scenery on top, and you still have conflicting objects, then you DO have a conflicting scenery somewhere, no doubt about this.

The only thing I can guarantee is we haven't changed anything that would affect the loading order.
Title: Re: Did the last update do somehow place FSDT sceneries below default?
Post by: Dave_YVR on December 10, 2020, 06:16:57 pm
What are your ORBX library insertion points set to?