Embedded stairs on arrival

[Framsen]

Hi guys and Happy Holidays!!

I’m opening a new topic as recommended, but this is related to an older discussion that still seems relevant:
https://www.fsdreamteam.com/forum/index.php/topic,33110.0.html

The issue is still present and reproducible with both PMDG and iFly 737 aircraft.

GSX correctly detects embedded stairs on departure (since they are already extended), but on arrival the embedded stairs are retracted, so GSX spawns both front and rear stairs. Once spawned, GSX continues to use them even if the embedded stairs are extended afterward.

Workarounds currently require parking without GSX or resetting GSX after parking. Aircraft profiles are correctly set, so this does not appear to be a profile configuration issue.



Thanks for looking into this, and keep up the great work! 

Best regards,
David

[Fabo]

Looks like the same thing is a thing with MD-80?

[virtuali]

This has been discussed many times and, it's not really a bug, it's more something that would require a change in design.

The CONDITIONAL embedded stair cannot be detected on arrival, because the choice to create (or not) stairs is done depending on the variable controlling the condition, but the variable won't be set until after you park and extend the airstairs, but by that time, the decision to create stairs has already been made when you select the gate on taxi (or even before the arrival).

So, ideally, we should have a way to announce your *future* intention to use the embedded stairs when the gate is selected, which is just not there, but we are planning this.

The closest thing to that, is to create an airline-specific .CFG file where the Conditional staircase is replaced with a fixed condition (just type 1 in the xml condition field, so it will always be True), to simulate an airline-specific policy of always use the airplane own stairs.

[Fabo]

The closest thing to that, is to create an airline-specific .CFG file where the Conditional staircase is replaced with a fixed condition (just type 1 in the xml condition field, so it will always be True), to simulate an airline-specific policy of always use the airplane own stairs.

How would one do that?

[virtuali]

How would one do that?

Page 77 of the manual.

[Fabo]

Ah! Very useful, thanks. I can see that I can also use it to force belt loaders on A320s, but only those which are LCC or charter airline operated and leave cans for mainline. That's a feature I didn't even know I want, but I do.

[Framsen]

Yeah however, I have a GSX profile saved for an airline, I saved it for A320 CFM SL like this:

[cargo1]
pos = 0.76 5.27 -0.86 0.00
code = (A:INTERACTIVE POINT OPEN:8, percent over 100) 0.9 >
name = FWD Cargo
ceiling = 1.2
width = 1.8
embeddedStair = 0
pigsenabled = 1
uldcode = BELT

[cargo2]
pos = 0.79 -9.25 -0.84 0.00
code = (A:INTERACTIVE POINT OPEN:9, percent over 100) 0.9 >
name = AFT Cargo
ceiling = 1.2
width = 1.8
embeddedStair = 0
pigsEnabled = 0
uldcode = AKH

However on my next flight upon loading was correct, but upon unloading cargo I had belt at the rear cargo aswell... The inside GSX AC setting window is correct there is no BELT allowed, however I got 2x belt loader. I don't know why.
The default gsx.cfg for this AC is also like this.