Products Support > GSX Support FSX/P3D
Pushback Sequence - change request
Captain Kevin:
--- Quote from: Alpolex on January 24, 2023, 03:01:02 pm ---It's not a question, it's fact similar to other users. As I said, performed with the FSL A320FAM not PMDG.
See quote:
--- Quote ---I am using the FSL A320FAM which obviously have different timings.
--- End quote ---
--- End quote ---
Yes, I see that, but even then, I don't think it should be taking that long even with a different airplane. I asked you to check something for me to see if the bypass pin location could be a problem. You haven't done this yet. I can't really do anything else if I don't get an answer to my question since I don't have the FSL A320, so I can't check myself. I do remember that prior to me fixing the bypass pin issue myself, it did take a bit of time from the time I selected a direction to the time I got the call to release parking brakes, but I don't have this issue anymore since I solved the bypass pin issue. Just to be clear, I'm not questioning the fact that it's happening, I'm questioning why it is, and I'm trying to figure this out for you because it shouldn't be doing that.
--- Quote from: gregoryv on January 24, 2023, 05:37:36 pm ---I fully agree with Alpolex.
Logical sequence is looks wrong to me too.
For offline flights it probably not an issue but for flying in Vatsim in busy event it takes too much time.
The proposal to enable to finish all pushback preparations before looks very logical to me.
--- End quote ---
I do fly on VATSIM, so I get what you're saying here with regards to timing. What I am saying here is if it works the way it should, it should already be doing what you propose it does. It shouldn't be taking 37 seconds from the time a direction is selected to the time you get the call to release the parking brakes. As far as the bypass pin issue, if there isn't a bypass pin position set in the GSX aircraft configuration, it defaults to 0,0,0, which is the center of the airplane. If that happens, the ground crew has a much longer distance to walk compared to if the bypass pin position is properly set in the GSX aircraft configuration. That's why I'm asking him to check this.
PavlinS:
Sorry for that message. I realize that I keep the parking brake on nvm I need to turn it off to pushback. Seems that my P3D disconnected my messages on screen so I was sitting on the gate like idiot. Kha, darn, I am so silly........ ;D ;D ;D ;D ;D ;D ;D ;D ;D
tcas_test:
100% agree with you here. In real life the pushback is connected and ready to go, as soon a clearance and a tail direction is confirmed pushback only takes a matter of seconds. Not 30-40 seconds which we are waiting at the moment.
Bypass pin - pushback connected - reopen gsx menu to pick direction - pushback commences. This would match the realworld nicely and bring the time down.
--- Quote from: Alpolex on January 24, 2023, 10:18:01 am ---Hello Captain Kevin,
just to make sure we're talking about the same factors: I am using the FSL A320FAM which obviously have different timings.
Starting the process with "Hello Captain we are ready for pushback" initiates the Ramp Agent going to the NLG to insert the bypass pins. However, after he confirms "bypass bin inserted" the p/b truck starts to arrive (1:11 min) to attach the aircraft to it's tug.
The announcement "locking the gear" (however, unnecessary call-out you wouldn't hear in real-ife) comes around 1:30 min with a pop-up message to state the direciton of pushback.
Selecting the direction it takes another 37 seconds for any movement before the "Release parking brake" announcement comes up.
To be straigh forward, because it seems you are not really understanding what I am asking for: I am not asking for a work-around after several years of intensive usage of GSX especially on VATSIM and online events.
I would like to enhance the sequence.
Improvement: Sequence should be initated with push-back completly ready and asking for direction during a second menu which means there are two stages in the menu:
a) Prepare for Pushback -> all preparations will be made and the tug is connected plus everything is ready upon selecting the next menu
b) Start Pushback -> request for direction and immediate start of pushback
--- End quote ---
Captain Kevin:
--- Quote from: tcas_test on January 27, 2023, 05:24:48 am ---100% agree with you here. In real life the pushback is connected and ready to go, as soon a clearance and a tail direction is confirmed pushback only takes a matter of seconds. Not 30-40 seconds which we are waiting at the moment.
Bypass pin - pushback connected - reopen gsx menu to pick direction - pushback commences. This would match the realworld nicely and bring the time down.
--- End quote ---
And speaking of the bypass pin, did anybody even bother checking to see where GSX thinks the bypass pin actually is on the airplane. I asked twice now, and up until now, nobody's actually done this. This is the only thing I can think of that might cause such a significant delay because one of the previous updates added the bypass pin location into the GSX aircraft configuration. If there isn't a bypass pin position set in the GSX aircraft configuration, it defaults to 0,0,0, which is the center of the airplane. If that happens, the ground crew has a much longer distance to walk compared to if the bypass pin position is properly set in the GSX aircraft configuration. This is the only reason I can think of for such a significant delay. I do remember that prior to me fixing the bypass pin issue myself, it did take a bit of time from the time I selected a direction to the time I got the call to release parking brakes, but I don't have this issue anymore since I solved the bypass pin issue.
Alpolex:
[aircraft]
nosegear = 9.40
refueling = 0
battery = 0
pushbackraise = 0
pushbackdummyevent = 0
pushbackcheckengines = 0
iscargo = 0
trafficcones = 1
preferredexit = 0
wingrootpos = 3.98 -2.31 -0.95
wingtippos = 15.16 -6.39 -0.08
fuelpos = 10.25 -2.92 -0.67
waterpos = -0.56 -14.45 0.00
lavatorypos = 0.67 -14.49 0.00
gpupos = 0.12 11.90 -2.17
engine1pos = -5.85 1.31 -2.57
engine2pos = 5.87 1.30 -2.57
engine3pos = 0.00 0.00 0.00
engine4pos = 0.00 0.00 0.00
[exit1]
pos = -1.95 9.40 -1.17 3.00
code = (L:FSLA320_pax_door1, number) 2900 >=
name = Left Fwd Cabin Door
embeddedStair = 0
[exit2]
remove = 1
[exit3]
remove = 1
[exit4]
pos = -1.70 -15.24 -1.12 -11.00
code = (L:FSLA320_pax_door3, number) 2900 >=
name = Left Aft Cabin Door
embeddedStair = 0
[service1]
pos = 1.93 9.50 -1.02 -4.00
code = (L:FSLA320_pax_door2, number) 2900 >=
name = Right Fwd Cabin Door
embeddedStair = 0
[service2]
pos = 1.74 -15.15 -1.02 10.00
code = (L:FSLA320_pax_door4, number) 2900 >=
name = Right Aft Cabin Door
embeddedStair = 0
[cargo1]
pos = 0.96 6.28 -2.13 0.00
code = (L:FSLA320_upper_cargo_door, number) 2900 >=
name = Upper Cargo Door
embeddedStair = 0
uldcode =""
[cargo2]
pos = 0.94 -8.14 -2.13 0.00
code = (L:FSLA320_lower_cargo_door, number) 2900 >=
name = Lower Cargo Door
embeddedStair = 0
uldcode =""
[cargomain]
remove = 1
Here's the A320CFM GSX Config.
Nevertheless, I would be happy if you could at least start to jump on this topic about the senseless and unrealistic sequence. I am working in the aviation industry and flying on a regular basis as a crew member on the flight deck - so my feedback is based on how those procedures are performed in reality.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version