All jetways edited by GSX level 2 are messed up

[Danielgarzag]

So I edited some airports which the jetways of GSX level 2 and replaced the default with the SODE jetways. But for some reason, GSX level 2 is screwed up and in all the airports where the jetways were placed are now messed up. The Jetways are out of place and are not the ones I installed and put. Some terminals don't even have jetways at all.

Any help??....

P.S. It can't be the AFCAD, all airports that had SODE are messed up..

[virtuali]

It's likely the AFCAD which is now active is not the same which was active when you customized the jetways, but for some reason GSX is not reading it, but the sim is.

The most common case of GSX not reading the active AFCAD, is if you (or a 3rd party utility ) renames the active AFCAD and, for efficiency reasons which would be a bit long to explain here, file renames are not always detected by GSX, so you need to use the "Restart and the rebuild the airport cache" option and be sure GSX is reading the correct AFCAD.

Of course, if the (now correct) AFCAD was never customized for GSX (for example, to add jetways), you will have to configure it again.

[Danielgarzag]

It's likely the AFCAD which is now active is not the same which was active when you customized the jetways, but for some reason GSX is not reading it, but the sim is.

The most common case of GSX not reading the active AFCAD, is if you (or a 3rd party utility ) renames the active AFCAD and, for efficiency reasons which would be a bit long to explain here, file renames are not always detected by GSX, so you need to use the "Restart and the rebuild the airport cache" option and be sure GSX is reading the correct AFCAD.

Of course, if the (now correct) AFCAD was never customized for GSX (for example, to add jetways), you will have to configure it again.

But no 3rd party utility has renamed the AFCAD.. and the Restart and Rebuild Airport Cache is useless in this situation, it reads the same wrong AFACD..

[virtuali]

and the Restart and Rebuild Airport Cache is useless in this situation, it reads the same wrong AFACD..

If this happens after a cache rebuild, there are many reasons why GSX is reading the "wrong" AFCAD:

- The "wrong" AFCAD has been installed with an higher layer priority. In this case, GSX is correct reading it, so you must either remove it or change the layer priority in the scenery area

- The "right" AFCAD is not self-contained, for example is a partial AFCAD that still requires the default AFCAD to operate. Since GSX doesn't support reading data from multiple AFCADs at the same time, it will only read the default AFCAD. Nothing to do about this.

- The "right" AFCAD is too large in size, and GSX skips files larger than 2MB by default, in order to speed up the search. This can be changed, as explained here:

http://www.fsdreamteam.com/forum/index.php/topic,13489.msg100092.html#msg100092

- The AFCAD might be related to a very close airport, or even a small airport inside the main one. This can be fixed as explained at Page 25 of the GSX manual, which discusses these cases.