So ... pushback used to work fine out of the box, until there were optimizations for big airplanes.
Same with the parking system readout, that was put higher for the bigger airplanes, creating problems for those flying A320/B737 and smaller aircraft.
Thus, you are basically telling us that everyone with a „smaller“ airplane now needs to customize their pushback at every stand we want to use in order to get it right?
You forgot the most important part of my sentence, which was "depending on the scenery". Smaller airplanes works perfectly fine in most airports, especially defaults in which the AFCAD nodes are usually spaced apart quite well, so GSX won't have any doubts about which one to choose.
However, some scenery designers are fixated in doing paths with too many points very close together, hoping to have more "control" over AI paths, even if this is mostly useless, since the simulator own ground handling engine for AI will smooth curves on its own depending on the AI ground handling specs anyway so, they won't usually obtain much by placing so many nodes close together, but this makes GSX work of choosing the right exit node more difficult, since most of the code of the GSX pushback is there only to throw away mistakes or silly methods found in some airports.
And, sometimes they are just not precise enough: it's very common to see problems like parking spots in the AFCAD not aligned with the actual lines in the scenery, and misaligned AFCAD paths as well, which are obvious if you just open the GSX customization editor, and compare how the default parking position is very often misaligned, that's why GSX also offers the ability to fix that.
That's why we added the Custom "Free" pushback in the editor first, and now as a very easy to use QuickEdit mode with autosaving: because it's simply impossible to have an automatic system that would always work, with every airplane, on every AFCAD, regardless how badly it was made.
With the next update, the QuickEdit will be even easier, since it will default with using NO corner node ( but up to 9 can be added ), so you'll only have to specify the airplane final position/heading, which will usually work most of the time for the standard parking types, and you'll have to do it only once, it will be autosaved, and you'll be given the ability to decide to save it either in one of the two default Left/Right slots, or create an entirely new slots (an unlimited number of them, for each parking), so you'll never want to use the automatic method anymore.
