But if you are Honestly, you see that it is not going on the yellow line and also I don't know how much test und tries he need for this one pushback to set up.
It follows the yellow line quite reasonably.
As explained so many times, the *actual* path will change depending on the airplane used and the pushback used, because the curve will have to take into account the mechanics of the whole system, which is made by the airplane wheelbase length + the pushback towbar (if there is one) + the tow truck wheelbase length AND even the maximum excursion allowed to rotate the front gear by the tow bar or the towbarless system.
ALL of these will affect the final curve, so you will never see exactly the same curve being performed each time, as lone at least one of these parameters is not the same.
because it seams you running out of Arguments (again) i just have another to say about the limitation of GSX.
You ran of of arguments again, because you have been proved wrong over and over. The famous "impossible" S pushback at TCNM can be done quite well with just 2 custom points, and that's a fact.
Now, i can set up ONLY 2 Taxi Directions ( called left/right in GSX ) but here i have to set up 3 ones because it i related to the Stand and not to the Arcraft ( which is ok ) but with my Proposel from the last post you can set up the PB in the Pre Setup for your actual Airplane, which one it ever is.
Now that you have been proven wrong by the supposedly "impossible" S pushback at TCNM, which was your pet-peeve, you are now adding an entirely new issue, which is a pushback depending on the airplane kind.
That's obviously a possible feature to add but, of course, it doesn't have anything to do with your suggestion, which seems to ask over and over the same nonsensical "Better pushback" usage patter of constantly asking and re-asking for pushback EVERY TIME.
As I've said, so many times already, this is just wrong, annoying, time consuming and not realistic. A Pushback should be configured only ONCE in your life so, even if there are several procedures which could be aircraft-dependent, it would be wrong to mimic the X-plane plugin just because of that.
The proper solution would be, of course, tagging the procedure by aircraft type, and automatically save the airplane type used, if requested.