Developer's Backdoor > GSX Backdoor

Pushback Procedure overhaul?

<< < (2/4) > >>

virtuali:
I'm not sure why people keep referring to that X-plane plugin as an example of how an eventual GSX pushback could be improved. If anything, that would be a perfect example of how it should NOT be done!

That kind of interface could be maybe used in the scenery *editor*, possibly to create a custom pushback route but, it's just wrong being forced to go through all that procedure each time. The whole point of the GSX pushback, is that is able to figure out MOST of the common push backs automatically, and it's not realistic that you, as the pilot, would do that.

The issue is, that plugin, with all that fancy (and cumbersome, if you are flying, not editing a scenery) interface, is made that way, just because it's much EASIER, from a programming point of view, to force users to tell everything to the pushback, rather than having the program figure it out automatically 95% of the time, which is how GSX works. So, this is a clear example of when a program that "looks" more featured, but only because it's less capable of doing the proper calculations on its own.

That kind of interface might be used when editing a scenery, but surely we wouldn't want to go through that each time you ask for pushback.

In any case, when I refer to improving the pushback, it means actual new features, like push-ins and gate to gate transfers and more realistic procedures, with better animations too. These will all come at some point.

Speedbird ATC:

--- Quote from: virtuali on February 05, 2018, 12:31:56 pm ---I'm not sure why people keep referring to that X-plane plugin as an example of how an eventual GSX pushback could be improved. If anything, that would be a perfect example of how it should NOT be done!

--- End quote ---
The UI takes just a few seconds to customize, and it generally results in a far more precise pushback then GSX could ever give. The fact is I do not have the time to go through GSXs cumbersome editor for every gate I want to pushback from only to either have my airplane slew across the field or have the pushback not turn out right.

virtuali:

--- Quote from: Speedbird ATC on June 11, 2018, 03:12:26 am ---The UI takes just a few seconds to customize, and it generally results in a far more precise pushback then GSX could ever give. The fact is I do not have the time to go through GSXs cumbersome editor for every gate I want to pushback from only to either have my airplane slew across the field or have the pushback not turn out right.
--- End quote ---

I'm not really sure what you are trying to say with the "GSX cumbersome editor". There's NO editor for the pushback route yet so, how you could possibly call "cumbersome" something that doesn't even exists yet ?

Eeven if it takes "a few seconds" to do it in X-plane, you must do it at every pushback, while the proper way should be doing it only ONCE, and then having it saved forever for that gate, which how we'll do it, of course.

And this would be required only for some specific pushback routes because, most of the time, when the parking is straightforward, GSX CAN pushback correctly and very precisely, automatically, with no user intervention, while the "better" pushback plugin always requires your input, because it's not able to sort it out those standard Left/Right directions automatically, like GSX does.

lpf20011:
A slightly related request from myself from the OP.

 Will it be possible to have more than 2 pushback options - Hong Kong has for instance 3 - 4 pushback options (labelled red, green, blue yellow). I like that in the current version of GSX you can rename the pushback options but having more would be very handy.

I  think also giving a maximum wingspan to a pushback option would be useful, especially where one pushback route may not provide sufficient wing tip clearance.

Thanks

VHHHflyer:
I personally prefer the GSX pushback over the XPlane one, which i find unrealistic/cheap.

Navigation

[0] Message Index

[#] Next page

[*] Previous page