Problem After Installing GSX Level 2 Expansion

[DLGA]

I'm not sure that this is the correct place to be posting this problem, but I should add that I did NOT have this problem until AFTER I purchased, downloaded and installed GSX Level 2 Expansion. So perhaps this is the correct spot.

The problem being that at ALL my airports and not JUST the FSDreamTeam airports, the scenery is either 1) missing, 2) blacked out or 3) miss-aligned.

Here is a shot taken at PHNL: (https://bit.ly/2EIHo5j)
Here is another shot taken at PHNL Gate 20 (https://bit.ly/2ReavyF)
Here is a shot taken at KIAH (https://bit.ly/2z2G4Eo
Here is another shot taken at KIAH (https://bit.ly/2yuXABy)
Here is a shot taken at KMEM (https://bit.ly/2JfgLTZ)

As I said, I did not have these problems before I installed the new GSX and this is happening with EVERY airport that I have installed and it makes no difference which developer it is.

If anyone can provide some type of crisis control I might be able to perform I sure would be grateful!

Thank you
DLGA

[virtuali]

As I said, I did not have these problems before I installed the new GSX and this is happening with EVERY airport that I have installed and it makes no difference which developer it is.

No, you already had this same problem before installing GSX, it's just that you noticed it now, because misplaced jetways are easier to notice.

The problem doesn't have anything to do with GSX. The clear proof of this is the screenshot with misplaced AI airplanes, which of course are not handled or affected by GSX in any way.

The most common source of conflicting AFCAD are files supplied with AI Traffic products, like MyTraffic or Traffic X, which are supposed to be used only as an enhancement of default airports, but must be removed if you have an addon airport.

You can use the free Simple Airport Scanner utility to search for duplicates AFCAD:

http://www.scruffyduck.org/simple-airport-scanner/4584282795

Of course, a conflicting AFCAD would also cause the misplaced jetways, since GSX reads their position from the AFCAD that has the highest layering priority, so you are mislead thinking this is a GSX problem but, the fact that your AI are also misplaced, clearly indicates the real problem is the conflicting files.

[DLGA]

I appreciate your reply Umberto but as I stated, everything WAS working correctly the day before I made this update and I had just completed a flight to KMEM from KIAH and there was absolutely nothing wrong with either the airports or the AI traffic (Traffic 360), which by the way I have been using for the last 4 years with no problems.

That is the reason why I decided to check and see if this were an isolated problem or something else so I guess that I will continue trying to find out what happened.

My first step will be to uninstall the Level 2 Expansion and see if this makes any changes.

It seems mighty strange that everything is working perfectly and then with one update everything starts to fall apart.

Thank you
DLGA

[virtuali]

as I stated, everything WAS working correctly the day before I made this update

There are only two possible explanations for this:

- You haven't noticed it before

OR

- Something else happened/was installed and, since it happened roughly at the same time as your GSX installation update, you think it was caused by GSX.

The ONLY thing the GSX Installer does to a default scenery, is to disable the default jetway model from the library file that contains it. The most catastrophic thing that MIGHT theoretically happen (which never happened so far), is the GSX installer might corrupt that file, maybe because it crashed while doing it. And, even in that case, the worse it would happen, is that you would lose some library objects of the default scenery, that's it.

The ONLY way to cause misplaced parking positions on an airport, is with a conflicting AFCAD for the same airport. There are no other ways to do that, and GSX doesn't touch or install ANY of such files.

My first step will be to uninstall the Level 2 Expansion and see if this makes any changes.

It won't change anything but, if it's useful for you to convince this couldn't possibly caused by GSX, then by all means do it...