Sign in to follow this  
ozflyer

Issue with latest GSX

Recommended Posts

Hi...

 

I updated GSX to the latest version end of last week. I find that during push back... to the left / right is not executed by ground.

 

I think it could be bcos GSX has introduced a new option to start engines before pushback And ground could be confused!,, by an extra prompt that has been introduced.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

You  can  adjust  the push back   parameters to  what ever  direction  you want, its  all  explained  in the manual on how  to do it

Share this post


Link to post
Share on other sites

Hi...

 

I updated GSX to the latest version end of last week. I find that during push back... to the left / right is not executed by ground.

 

I think it could be bcos GSX has introduced a new option to start engines before pushback And ground could be confused!,, by an extra prompt that has been introduced.

 

Thanks for the heads-up.

 

Will look at it.

 

Indeed. Since there's no SDK, we have to constantly adjust to what GSX comes up with.

Share this post


Link to post
Share on other sites

You did not give any information as to what airport and to what gate but GSX normally only uses the information contained in the afcad. If GSX does something wrong or unexpected most of the times the cause lies with the afcad of the airport in question. However as explained there is a GSX menu that allows you to configure various options like e.g pushback directions.

Share this post


Link to post
Share on other sites

You did not give any information as to what airport and to what gate but GSX normally only uses the information contained in the afcad. If GSX does something wrong or unexpected most of the times the cause lies with the afcad of the airport in question. However as explained there is a GSX menu that allows you to configure various options like e.g pushback directions.

Understood... the issue is that GSX is not catering to an extra input that is required now by GSX...

 

Let's wait for Gerald to investigate and report back.

Share this post


Link to post
Share on other sites

Thanks for the heads-up.

 

Will look at it.

 

Indeed. Since there's no SDK, we have to constantly adjust to what GSX comes up with.

Hi Gerald.... any luck.

 

I find that MCE by default chooses engine start before pushback... and the gsx ground crew wait for the engine start before pushing back. Can this be fixed ?

 

 

Thanks

Share this post


Link to post
Share on other sites

Hi Gerald.... any luck.

 

I find that MCE by default chooses engine start before pushback... and the gsx ground crew wait for the engine start before pushing back. Can this be fixed ?

 

 

Thanks

Yes, confirmed and fixed here.

 

From now on co-pilot will prompt whether you want engines started before push-back. If you confirm that he'll press option 1. If you don't or simply keep silent, he'd select option 2.

There will be a patch, either tomorrow or Saturday at the latest.

Share this post


Link to post
Share on other sites

How is it handled when using just ATC and GSX voice control ?

I can initiate e.g. catering or boarding via voice, but stuff like “Ground, are you ready for pushback“ or “Ground pushback to the left/right“ remains unanswered.

Does that have to do with the Operator selection ,(e.g. Servisair or Swiss or whatever) ?

The latter comes up via menu if I initiate Pushback from the GSX menu.

 

Mike

Share this post


Link to post
Share on other sites

How is it handled when using just ATC and GSX voice control ?

I can initiate e.g. catering or boarding via voice, but stuff like “Ground, are you ready for pushback“ or “Ground pushback to the left/right“ remains unanswered.

Does that have to do with the Operator selection ,(e.g. Servisair or Swiss or whatever) ?

The latter comes up via menu if I initiate Pushback from the GSX menu.

 

Mike

 

I will have to check. I believe interaction with mechanic is associated with the "Real crew coordination" feature. I mean, commands won't be available unless it's enabled.

Share this post


Link to post
Share on other sites

 

 


“Ground, are you ready for pushback“

 

Forgot to mention...

 

You cannot interact with ground mechanic until you have established first contact.

 

try "cockpit to ground" or "ground from flight deck". After that see if the command for pushback works.

Share this post


Link to post
Share on other sites

Yes, confirmed and fixed here.

 

From now on co-pilot will prompt whether you want engines started before push-back. If you confirm that he'll press option 1. If you don't or simply keep silent, he'd select option 2.

There will be a patch, either tomorrow or Saturday at the latest.

Brilliant... thanks for the fix... will make the experience a whole lot better.

 

How will we get the patch ?... will you post the link to it?.

 

Will avoid downloading the whole 700mb+ installer.

Share this post


Link to post
Share on other sites

 

 


Forgot to mention...
You cannot interact with ground mechanic until you have established first contact.

 

Ok, great, works now. Thanks for the heads up.

 

One more question : The manual says, after engine start, 'relieve mechanic from his duties (never forget that)'. Which phrase would I have to use for that ?

 

Mike

Share this post


Link to post
Share on other sites

 

 


Which phrase would I have to use for that ?

 

There are a number of variations.

 

mechanic you may disconnect now

Ground you may leave now.

ground engineer you may disconnect

....etc...

 

With GSX, the ground mechanic would automatically hand you over to GSX push team when the truck turns up (in which case, there is no need to release him), unless you have option "Keep mechanic on push" enabled in "Advanced options" panel.

 

And of course, you have the option to ignore all existing trigger sentences and use one that comes to you naturally (in ANY language). To do that, you'd have to create your own sentence and tie it to any of the built-in ones.

Share this post


Link to post
Share on other sites

Thanks for the info, Gerald, and for the patch.

But the pushback still doesn`t work after the patch, when using just GSX and PF3 voice recognition.

 

Pushback request gets recognized, but I`m asked to start an engine first. If I start an engine and request pushback again I get a message from GSX to turn off engines first.

In that case, could MCE automatically select “no engine start before pushback“ as default? At least I would prefer that.

 

Mike

Share this post


Link to post
Share on other sites

Thanks for the info, Gerald, and for the patch.

But the pushback still doesn`t work after the patch, when using just GSX and PF3 voice recognition.

 

Pushback request gets recognized, but I`m asked to start an engine first. If I start an engine and request pushback again I get a message from GSX to turn off engines first.

In that case, could MCE automatically select “no engine start before pushback“ as default? At least I would prefer that.

 

Mike

 

Will double-check...

 

Just in case, latest patch assumes you have the very latest GSX implementation with the prompt to select whether to start engines first (before pushback) or after pushback has been initiated. Previously, GSX wouldn't let you start first. FO should ask you whether you want to start first, then select option 1 or 2 depending on your reply

 

If you're on the latest GSX, when prompted by FO, either confirm you want to start engines first, or keep silent if you don't intend to.

 

If option is to start first, typically GSX will keep waiting until you have started at least one engine, then will start the push, without you asking for it.

 

I wonder whether the subsequent request caused MCE to send other keys that may have cancelled the pushback or something.

 

Also, since you're only using the pushback side of MCE+GSX implementation (a scenario that may not have been tested thoroughly), suggest you use another service like catering as a first request and see if request for push is handled OK thereafter. Don't worry, you won't need to handle the doors yourself, they will be automatically opened and closed as the trucks dock/undock.

 

To request catering...

 

Agent_Name + "we need catering"

 

Example: "Simon we need catering", "Dieter, we need food and drinks" etc...

Share this post


Link to post
Share on other sites

 

 


Pushback request gets recognized, but I`m asked to start an engine first. If I start an engine and request pushback again I get a message from GSX to turn off engines first.

 

Also, very important, since there is no SDK, the Green bar is the means by which MCE finds out what GSX is doing.

 

GSX says "Open door X", MCE opens door X etc...

 

You cannot disable the green bar, or MCE would be reduced to sending keys without any kind of feedback.

Share this post


Link to post
Share on other sites

 

Also, very important, since there is no SDK, the Green bar is the means by which MCE finds out what GSX is doing.

 

GSX says "Open door X", MCE opens door X etc...

 

You cannot disable the green bar, or MCE would be reduced to sending keys without any kind of feedback.

 

Gerald..'a'quick Q.

 

I have customized flows etc.

 

When I uninstall a nd install a new version of MCE , doo I lose all the customized flows ?..

 

Including voxkey I have configured ?

 

Thanks

Share this post


Link to post
Share on other sites

no, you can easily (un)install MCE. Have done it every update. All flows and voxkey stuff still working

 

Best regards

Share this post


Link to post
Share on other sites

 

 


I wonder whether the subsequent request caused MCE to send other keys that may have cancelled the pushback or something.

Also, since you're only using the pushback side of MCE+GSX implementation (a scenario that may not have been tested thoroughly), suggest you use another service like catering as a first request and see if request for push is handled OK thereafter.

 

that seems to be the case indeed.

I tried to request catering. Request recognized, Dialog started, but then the GSX menu popped up and stayed there. I was surprised to see the FSUIPC window pop up as well with info regarding ACARS ATIS not available this time.  This is PF3 Hotkey 2 !!

So I assume MCE tried to send Menu Selection "2" to GSX, but it got understood as Hotkey 2 for PF3.

 

Does MCE realize if PF3 Hotkeys get changed? So I might try to change the PF 3 Hotkeys 0 to 9 to something else.

 

Mike

Share this post


Link to post
Share on other sites

 

 


Does MCE realize if PF3 Hotkeys get changed? So I might try to change the PF 3 Hotkeys 0 to 9 to something else.

 

Provided PF3 is installed on same machine as MCE, every time you connect it to the sim, MCE is able to see that and detect new call-sign, flight plan and assigned hotkeys.

 

Maybe better to use CTRL+SHIFT on all PF3 hotkeys, since you're using voice control and no need to press them manually. That will rule out interference with GSX assigned keys, never mind FSX built-in ATC and whatever other add-on.

Share this post


Link to post
Share on other sites

OK, problem solved. I assigned the PF3 Hotkeys 1 to 6 to something else and now GSX works fine with MCE voice recognition.

 

Well, almost, just a little disturbance. Catering, fuel and boarding request work. Pushback works as well, but as soon as the pushback gets initiated, MCE FO comes up with necessary engine start before pushback. However, it isn't, GSX has already started it's pushback sequence and simply ignores it. So pushback continues normally.

Just a cosmetical disturbance . Real Cockpit Crew coordination is not even active, so MCE does not need to mention necessary engine start before pushback.

 

Mike

Share this post


Link to post
Share on other sites

 

 


Just a cosmetical disturbance . Real Cockpit Crew coordination is not even active, so MCE does not need to mention necessary engine start before pushback.

 

Good catch! Thanks

 

Will be taken care of. You'll have to manually handle that part in next update.

Share this post


Link to post
Share on other sites

Ok.

 

But to be honest, I`m not sure why GSX introduced that selection at all.

Engine start during pushback yes, but start engines even before the pushback tug is connected ??

Does that really happen in the real world ?

 

If you would ask me, MCE could automatically select `no engine start before pushback` by default.

 

Anyway, thanks a bunch for your fast reaction !

 

Mike

Share this post


Link to post
Share on other sites

Ok.

 

But to be honest, I`m not sure why GSX introduced that selection at all.

Engine start during pushback yes, but start engines even before the pushback tug is connected ??

Does that really happen in the real world ?

 

If you would ask me, MCE could automatically select `no engine start before pushback` by default.

 

Anyway, thanks a bunch for your fast reaction !

 

Mike

 

Some aircraft like Concorde or CS 707 don't have APU, therefore need to start at least one engine on Ground air start before pushing. I believe it's also needed for Majestic Q400 for some reason.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this