What you have argued makes sense except for one thing. The parking guidance was happy with the aircraft position as it showed STOP followed soon after by OK. If I had moved further forward then I would expect to see TOO FAR.
The parking guidance will always work, because while it will work even when you are outside of a parking ( of course ), but that's an entirely different thing than GSX not detecting if you are inside a parking or not.
Now, you are describing a 3rd party scenery, without saying which kind of guidance it was using, and which kind of jetways it came with. Please clarify exactly:
- Which scenery you are using
- Which kind of guidance system it has ( Provided by the scenery or made with GSX )
- If the scenery came with a GSX profile.
So why is one aspect of GSX happy with the aircraft position but the other half isn’t. Maybe there’s a mismatch in the code between the guidance indicator and what is required for the jetway to operate.
There's no mismatch anywhere in the GSX code. It's just you must understand the relationship between the parking location in the AFCAD, the GSX Stop position and its interaction with the scenery jetways.
Editing what are essentially expert created jetways shouldn’t be necessary.
Nowhere I said you must edit jetways, that's the only thing you shouldn't do, assuming they are well made and can be used with a reasonably wide range of stop positions for that airplane, but it simply impossible without doing some customization in GSX, so be sure a 3rd party scenery using either a GSX guidance system or its own guidance system, that stopping following those indications would *always* result in BOTH:
- the jetway working from there
AND
- GSX still assuming you are inside a parking
That's why I said to check BOTH the parking location in GSX ( which is a way to move the parking without editing the AFCAD ) AND the Stop position in GSX.
Reading the "Understanding the Stop position" chapter at Page 43 of the GSX manual will surely clarify the issue to you.
