Stop position too far forward

[gaumond]

By default, GSX is placing the stop position way too forward causing the aircraft to park too far forward. This is causing the jetway to be unusable among just looking wrong. It is doing this at 3rd party airports and default airports. When I opened it in the editor it shows the stop position much further forward than the normal stopping position.  Could this be related to the MSFS stop position updates or is there something else going on?

[virtuali]

Could this be related to the MSFS stop position updates or is there something else going on?

Yes, of course is related to it, because we assumed it was an improvement that should be valid for both simulators: before the update, the bigger the parking radius, the more the airplane was placed too far back, because the default method (lacking a custom Stop position) would place the reference point of the airplane in the center of the parking spot so, larger parking spots that, due to their size, were placed more behind, would result in planes, especially mid/small jets parking in large parking spots, to far from the jetway, so now there is a correction fact, of about 1/3 of the parking radius.

But that's just the default, when no better data is available. For best results, you were always supposed to customized the Stop position, and in this case, changes to how the default position is calculated, won't have any effect, since the customized Stop position is always used, when available.

[gaumond]

Is there a way to change this default value either globally or across a individual scenery? In the past the default position were pretty close for the most part and only had to edit here and there. Now I am finding that it is placing the stop position right at the marshal's position, causing the marshal to be placed on a ladder when approaching a gate at every default scenery and many 3rd party sceneries.

If it isn't already a tweakable option could it possibly be in the future? It would be convenient to be able to adjust and set a standard stop position and tweak from there for sceneries that don't have a custom Stop position.

[doksas]

Same problem in P3Dv5.3 last few weeks, and customized the Stop position not solution because we have many airports with too many jetways.
When flying online you never know which gate ATC give to you.
 So, stop position customization is unacceptable, please give another solution Umberto.

[virtuali]

So, stop position customization is unacceptable, please give another solution Umberto.

Custom Stop position IS the best solution, and it's what should always used to be sure GSX works reliably.

Have a read at the chapter in the manual named "Understanding the Stop position". After such a read, it should be obvious that using GSX without a proper custom Stop position is asking for troubles.

However, in yesterday update we tweaked the default Stop position to be a bit back but again, it's just wrong having to rely on that alone, because sceneries places the parking spots with various combinations of positions and radiuses, which means it's just impossible to expect GSX could possibly always work with JUST this data.