The main difference would simply be to have to click once or twice from a bird’s eye view to make your pushback path and that’s it, it’s really not a big deal.
That's only in the case of the most simple procedures, those that GSX can already calculate automatically now.
But then it’s also not realistic to push back on completely wrong paths because they were computed for you. I’m sure you know it is very common to have planes pushback onto further out taxiways or down different distances because of taxiways constraints (A380), other traffic taxiing, pushing back, etc… The complexity is endless. Being able to create custom pushback routes depending on the situation (traffic, ATC requests) is, in my opinion, more valuable than simply not having to do a couple of mouse clicks more.
I suggest reading the manual, the part that explains the custom pushback nodes. GSX already had for some time the ability to create custom routes and with what you have now, it's already possible to fix a lot of less common used cases.
What we are missing is only:
- The ability to base the route on waypoints which are not already-existing AFCAD nodes.
AND
- The ability to pull too.
AND
- The ability to have more than 2 custom routes.
And that's what we'll going to add.
Can you imagine how annoying it would be if users had to start to look on forums for “pushback profiles” every time a scenery comes out or is updated, just to have more accurate (but still hardcoded!) routings?
So, you find more "annoying" to create the route yourself, each time, when someone might already made it ? That's not how should be done.
With GSX Level 2 addon, the airport configuration capabilities will be already more extensive, which means there's added value in users sharing their own custom profiles, for example with airports having a completely new set of jetways.
Which means, at some stage, we would like to have some kind of network of user-created content, where the program can automatically look for airport profiles, and download them on the fly, possibly with the ability for other users to up/down-vote the contributions.
For sure, it’s quite obvious that GSX is a lot more complex, algorithmic-wise, but sometimes the best solution is actually the simplest one, and I think that’s the case here.
The simplest solution is already the one that GSX use now: being able to sort out the most common cases automatically.
Ultimately you guys already did the hardest part! Having automated pushback on any airport. So if coding the alternative method is so straight-forward, why not offer both to users in GSX?
And where, exactly, you read we are NOT going to do it ? I only said we are not going to do it in THAT way.