FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: billkhaled on September 01, 2018, 12:51:28 pm
-
This is getting very annoying now as I complete my entire pre flight only to realise GSX will not push me back. The aircraft this usually happens is the PMDG 737 and has happened at UK2000 EGCC, EGKK and Flytampa Amsterdam. My verbosity setting is not too low, I read a thread with a similar issue which was of no use. If it is helpful when I re connect to ground power GSX continues with the messages, but I can’t push back on ground power.
-
If it is helpful when I re connect to ground power GSX continues with the messages, but I can’t push back on ground power.
Have you turned on the APU ?
-
Yes
-
If it is helpful when I re connect to ground power GSX continues with the messages, but I can’t push back on ground power.
In order to allow pushback in the PMDG 737, GSX checks the following:
- Wheelchocks must be removed
- the PMDG GPU vehicle must be removed
- the PMDG Air Start Unit vehicle must be removed
- the APU must be On
- the Pitot covers must be removed
There's nothing in the GSX code that ever checks for Ground Power (unless you meant the GPU vehicle) so, I cannot possibly understand why GSX allows pushback only when the Ground power (not the vehicle) is enabled.
And, in any case, if ANY of these constraint is active, you are supposed to see the GSX message window indicating all the conditions that must be satisfied. Assuming you have the verbosity slider up, of course...
-
After removing the chocks, everything is off and the APU is running with parking brakes set. After I hear “Hello captain we are ready for pushback” there are no further instructions.
-
After removing the chocks, everything is off and the APU is running with parking brakes set. After I hear “Hello captain we are ready for pushback” there are no further instructions.
Could be the usual issue with the scenery having the pushback direction set to None ?
-
After removing the chocks, everything is off and the APU is running with parking brakes set. After I hear “Hello captain we are ready for pushback” there are no further instructions.
Could be the usual issue with the scenery having the pushback direction set to None ?
No it’s set to both
-
*UPDATE ON THE SITUATION*
I figured out tonight that GSX is responding but with very long intervals. For example it will commence pushback 5 minutes after relasing the parking brakes. Also after selecting an option, going to the GSX settings page and back, means the instruction is followed instantly
-
For example it will commence pushback 5 minutes after relasing the parking brakes. Also after selecting an option, going to the GSX settings page and back, means the instruction is followed instantly
That's strange, and nobody ever reported it so far. GSX, like any other Simconnect addon, requires to be called BY the sim at some time interval, otherwise it won't process anything.
It's *possible* that, due to very high traffic on Simconnect (too many addons sending too many commands in a short interval) might cause this. Do you have a weather engine running ? Does it happen with a default airplane ?
-
Well I have projectfly and FSWX, I recently downloaded Ezdok camera v2 when this all began
-
Well I have projectfly and FSWX, I recently downloaded Ezdok camera v2 when this all began
Then the obvious next troubleshooting step would be disabling all addons (I'd start with Ezdok camera, since you said it started with it), then re-enabling them, one by one, until you find the culprit.
-
I removed EZdok camera but there was no change and GSX still remained unresponsive upon call for pushback. It goes as far as to say ‘locking gear’ but the marshaller never moves to lock my gear. I have even tried it without my weather engine, and I still have the same issue.
-
Since nobody else reported this issue (GSX working, but replying only after minutes), it must be some kind of conflict with another add-on so, as I've said in my previous reply, start with disabling *all* your other addon modules.
BTW, I think you haven't said which simulator you use. It might be important.
-
well, it's 2020 and I receive this error where nothing happens after here hello captain we are ready for pushback. Usually restarting Couatl will solve it sometimes once other times a few restarts.
-
Please describe PRECISELY when this happens, and which airplane are using.
-
well, it's 2020 and I receive this error where nothing happens after here hello captain we are ready for pushback. Usually restarting Couatl will solve it sometimes once other times a few restarts.
when this occasionally happens to me, 100% of times I solve this by just opening the FSUIPC options window, and closing it at once (I read this at avsim long time ago) ... interferences between addons communications with p3d, I guess
-
Just an observation:
You are not missing the pop-up box asking you for 'what direction' of pushback are you? Maybe it isn't displaying? I know I would prefer a 'ding' when it appears to let you know action is required (or a verbal). Anyhow, occasionally I have missed it, or spotted it just as it is closing. I have found it impossible to get it back. Ctl+F12 brings up the abort request not the direction box.
Aussie
-
I am so sorry for the late reply.
It is not aircraft specific sometimes I fly the FSLabs or Maddog but it's not specific to any aircraft. It just happens. up to a few days ago I was getting to take the most recent update of the bus out for a flight and it happened and it took two or three couatl restarts to hear the tug coming up to the airplane nose.
After the ground mechanic says hello captain we are ready for pushback he then proceeds to say locking gear. however, when this issue happens he says hello captain we are ready for pushback and just stand there. he does not move and the gear is not connected. There is no other action after making that first statement.
-
however, when this issue happens he says hello captain we are ready for pushback and just stand there. he does not move and the gear is not connected. There is no other action after making that first statement.
It's not a GSX issue. Some airplanes, and the FS Labs and the Leonardo Maddog, are able to control GSX themselves, and they disable some messages from GSX, to let this happening automatically so, you are probably missing a step in the airplane usage, so the airplane is expecting you to do something, and since the airplane has disabled the GSX messages, you can't tell what.
Sorry for not being more specific, but I'm not fully aware of the extent of the control over GSX these airplanes are able to exert, only that I'm sure they are able to suppress GSX messages and operates GSX menus automatically, to use it "hands free". So you might want to check with their support.