Confusing gate issues at PHNL

[Briskf16]

First off, thank you for great sceneries! I recently uninstalled and reinstalled PHNL scenery and have multiple gate issues.

System info: P3Dv4+, ORBX Honolulu (BGL/CVX .oFF), GSX v2, FSDT PHNL.

the west gates (52-59) are the GSX gates and the rest of the gates are populated (scenery gates) yet they don't move with cntrl-J. The gates that are populated are DOUBLE gates with scenery gates plus GSX gates.

Please help. Thank you.

[virtuali]

We recently added support for GSX/SODE jetways at PHNL but, in order for them to work correctly, you must be sure:

- GSX is using the FSDT AFCAD, this can be checked in the airport customization page

- You allowed the AFCAD to be updated when asked by the Live Update, because the new one is required ( that doesn't use CTRL+J jetways anymore )

- You must remove every GSX customization you made with the previous version, so the new one that comes with the scenery will be used. You can check if your own configuration is active in the airport customization page. If it is, remove your .INI file and Restart Couatl from the menu.

[airbadger]

We recently added support for GSX/SODE jetways at PHNL but, in order for them to work correctly, you must be sure:

- GSX is using the FSDT AFCAD, this can be checked in the airport customization page

- You allowed the AFCAD to be updated when asked by the Live Update, because the new one is required ( that doesn't use CTRL+J jetways anymore )

- You must remove every GSX customization you made with the previous version, so the new one that comes with the scenery will be used. You can check if your own configuration is active in the airport customization page. If it is, remove your .INI file and Restart Couatl from the menu.

You also have to go into the PHNL scenery folder and disable any .BGLs related to the jetways.

[virtuali]

You also have to go into the PHNL scenery folder and disable any .BGLs related to the jetways.

No, you don't. You only have to allow the Live Updater to update the AFCAD to the latest version, because jetways are called by the AFCAD and if there are none in the AFCAD ( the new version doesn't have any jetways in the AFCAD anymore ), that file won't do anything.

If you need to remove the jetway library .BGL on your system, it's because you either have another AFCAD active, or you haven't allowed the Live Updater to download the new AFCAD but, in a normal situation, removing the jetway library .BGL is not required. If it was, we would have the updater removing it automatically but, we *intentionally* decided to leave it there, for people that know exactly what they are doing, and prefer to use their own modified AFCAD with default jetways.

[airbadger]

You also have to go into the PHNL scenery folder and disable any .BGLs related to the jetways.

No, you don't. You only have to allow the Live Updater to update the AFCAD to the latest version, because jetways are called by the AFCAD and if there are none in the AFCAD ( the new version doesn't have any jetways in the AFCAD anymore ), that file won't do anything.

If you need to remove the jetway library .BGL on your system, it's because you either have another AFCAD active, or you haven't allowed the Live Updater to download the new AFCAD but, in a normal situation, removing the jetway library .BGL is not required. If it was, we would have the updater removing it automatically but, we *intentionally* decided to leave it there, for people that know exactly what they are doing, and prefer to use their own modified AFCAD with default jetways.

Ok, but what if I completely uninstalled PHNL, deleted its folder and contents, checked for extra GSX ini files and old AFCADs, re-downloaded the exe from FSDT.com, installed, ran Live Update, and still see both GSX jetways and default jetways? Oh, and the Addon Manager folder is excluded from virus scanning.

[virtuali]

Ok, but what if I completely uninstalled PHNL, deleted its folder and contents, checked for extra GSX ini files and old AFCADs, re-downloaded the exe from FSDT.com, installed, ran Live Update, and still see both GSX jetways and default jetways?

On SOME gate you are supposed to see them both, because there was a static jetway which we left in place, and the GSX/SODE jetway should have replaced the previously animated one.

Gate 8, for example, is like this, and it's normal.

Gate 14, instead, it's an example where you are only supposed to see a single GSX/SODE jetway.

[abueren]

I don't understand why you leave some static jetways. After all, that's the big strength of SODE, that you can have more than one jetway per gate. So could you please provide double moving jetways for these gates? In real live, theses gates also have double jetways

Best regards
Adrian

[Dave_YVR]

 You can always just use GSX and edit the airport yourself.

[BrianThePilot]

Yes, however if there's going to be sode for the airport, it would be nice if it could be correct with correct double and single jetways.

[virtuali]

I don't understand why you leave some static jetways.

Because we wanted to release an usable update as soon as possible, and removing static jetways would require more time to edit the terminal buildings.

[Dave_YVR]

Yes, however if there's going to be sode for the airport, it would be nice if it could be correct with correct double and single jetways.

 Exactly why you edit it yourself, then you have the jetways the way you want them to be.