Very confused - SODE jetways appearing in GSX Level 1

[VHOJT]

Hi there!

Thanks for all the wonderful work and updates you do in GSX, Umberto.

I am very confused - I only have GSX Level 1.

Since an update recently - the usual option of saying the scenery has a jetway has gone, and now I seem to be able to add SODE jetways.

Is there a way I can tell GSX still that I have a scenery CTRL+J jetway still?

I thought this was only for GSX Level 2, which I don't have.  This picture is at FlyTampa YSSY.

Any help you can offer would be appreciated!

Cheers,
Rudy

[virtuali]

As explained on the manual ( Page 4, "Trial Limitations" ) regardless if you bought GSX L2 or not, SODE jetways will still be added, but they will work only in Trial airports so, it's entirely normal you will see them. If you are outside a Trial airport or an FSDT airport, a message will say they won't move when you will try to use them.

Fact you see SODE jetways at a FlyTampa scenery, it's because you have a scenery in conflict, one that comes with default jetways, so they have been replaced. The most common source of conflicting scenery are AFCAD files that came with AI Traffic products, which you must remove if you have an add-on scenery for the same airport.

[VHOJT]

I just had a look at that page, thanks.

So - how I can I just tell GSX that the parking has jetway already?

The manual mentions something - the Control Panel to restore them?  I don't know what that is.

As far as I know, the only AFCAD is the FlyTampa one.  ORBX might have installed something underneath with the Australia v2, but I disabled all those BGLs?

Cheers,
Rudy

[virtuali]

So - how I can I just tell GSX that the parking has jetway already?

GSX knows the scenery has a jetway, and it has found a default jetway, because it doesn't know you are on a FlyTampa scenery (one that it's not supposed to replace jetways automatically), it thinks you are on a different scenery, because the AFCAD loaded is not the one from FlyTampa.

If you open the airport customization page, you'll see the name of the AFCAD loaded by GSX, which might give you an idea of which file is in conflict.

[VHOJT]

Okay thank-you, I will check that.

[VHOJT]

Hi Umberto,

The AFCAD given is D:\Programs\Prepr3D v4\FlyTampa\Sydney\scenery\ADEX_YSSY_GL_2015.bgl

This would seem to be the correct FlyTampa BGL?

[virtuali]

Yes, are you using a .INI customization file for it ? If yes, try to remove it.

[VHOJT]

Okay, I removed all YSSY ini files in appdata\roaming\virtuali etc.

I still cannot specificy that the scenery has a built-in CTRL+J jetway?

[virtuali]

I still cannot specificy that the scenery has a built-in CTRL+J jetway?

You don't have to specify it, GSX will know and, if they are not default, it won't create SODE jetways.

[VHOJT]

After resetting everything, it said "No Jetway" in the gate customisation page.

This means I will get stairs to the front door and not just nothing as before?

Before, I used to be able to say "Parking has a Jetway" with no other things like SODE jetways popping up?

Cheers,
Rudy

PS thanks for all your patience   

[virtuali]

After resetting everything, it said "No Jetway" in the gate customisation page.

That's because that gate doesn't have a default jetway. Are you sure the scenery doesn't already come with SODE jetways ?

[VHOJT]

It doesn't have any SODE jetways, no.

Now I come to think of it, this particular gate doesn't having a moving jetway.  The aerobridge is probably built-in into the scenery.  It doesn't move.

What is the best course of action to take for such a "fake" jetway?

Again, many thanks,
Rudy