Hi Ben -  As you may recall I've had problems getting AES and GSX services to start ever since you made the 777 upgrades this summer.  For me, version 2.6.0.3 was the last one where AES/GSX support worked properly.  This week I installed the latest version, 2.6.3.1 hoping for a fix. Though other MCE functions work fine, still no success with either AES or GSX support via MCE.    (My AES and GSX functions activate normally via keyboard but the MCE "ground services" voice command support doesn't kickstart, or appear later after I start AES or GSX.  When testing I have been using PMDG738WL - which worked fine with AES/GSX prior to version.  Normally I start MCE after FSX, but reversing the order doesn't matter.  When testing I verify that my mce.ini GroundServicesMode is set appropriately for the airport type.  What can I try to fix this problem ?

 

 

What can I try to fix this problem ?

 

OK, let's proceed step by step.

 

Install MCE V2.6.3.1 (latest) and restor MCE to factory settings

Install the latest GSX implementation. V1.9 or higher.

 

Set yourself up at EGLL, any suitable gate for your aircraft, with engines not running.

 

Start MCE. Do you get the ramp agent introducing himself?

 

If Yes, all is normal, otherwise we are looking at MCE possibly not reading simulator data properly. For instance when engines are seen as running, there would be no ramp agent.

 

Just to be on the safe side, set "fsx.exe" or/and "Prepar3D.exe" to run as admin.

Ben -  I did the troubleshooting procedure, following step by step.

I verified I'm using MCE 2631 and GSXv1.9. 

I used PMDG B738 and B777 to be sure problem isn't aircraft specific.

My EGLL is an AES airport so I also tested at EGKK, making sure GroundServicesMode was AES for EGLL and native for EGKK/

 

I got consistent results:

MCE will not kickstart GSX or AES at either airport.  Other MCE functions work OK, and GSX/AES do too, via keyboard.

 

However perhaps I found a clue:

I often fly online so I then tried to disable "talk to ATC controllers" by unticking the UI box.  Doing this hung MCE.

I then edited mce.ini PilotSpeaksToATC=0, and restarted MCE.  ATC tab was grayed, as expected.

But to my surprise I found that  if and only if my MCE ATC services are disabled,  AES and GSX ground services kickstart properly at both airports, and with both airplanes. 

 

Why should unticking "talk to ATC controllers" hang MCE ?

Why should AES and GSX kickstart function depend on my MCE ATC setting ?

 

BTW I have MCE programmed to talk to ATC using FSUIPC 4.937 and yoke button 2.  When I use MCE with Radar Contact 4, this works fine.

 

 

BTW I have MCE programmed to talk to ATC using FSUIPC 4.937 and yoke button 2.

 

Issue could be linked to this unusual and untested setup.

 

The workaround "UseWithVoxATC=1" in [GAMEPAD] section, assumes you have setup a joystick button within the MCE UI, and MCE monitoring the PTT directly, not responding to simulated PTT down and up events using FSUIPC.

 

I call on any registered user to confirm whether disablng/enabling the "Talk to ATC feature" causes the UI to hang. Definitely not happening here.

 

Don't forget, some joysticks have some buttons in the always ON state. And if for some reason, one of those is seen by MCE as the main PTT switch, disabling or enabling the ATC feature while the PTT is down can result in unexpected behaviour.

 

AES & GSX aren't directly connected to the ATC feature. However, when PTT button is detected "Down", it sets many things in motion, like stopping all voice output,

Ben - Since I have a joystick plugged in, I realize the MCE setup compels me to assign a joystick button for PTT.  I previously also had the same button assigned as PTT via FSUIPC for use with VPilot and PilotEdge clients, so I deleted the FSUIPC PTT assignments, did a factory reset of MCE, but GSX/AES still does not kickstart. 

 

Following your suggestion that my PTT joystick button might be sticking, I tried unticking the  MCE UI ATC menu "use: btn 2: ch flight sim yoke usb", leaving the Use <DEL> key for transmission.  So MCE shouldn't be reading the joystick and FSUIPC wasn't reading it now either.  Restarted MCE again.  GSX/AES Ground services still wouldn't kickstart.  (BTW I also directly verified btn 2 function using the driver cal routine - it isn't sticking).

 

Next, I again tried to untick MCE talk to ATC controllers, to disable ATC.  Doing this still hangs the MCE UI.

Finally, I killed MCE, edited PilotSpeaksToATC=0, restarted MCE, and this time GSX/AES kickstarted, and ground services works.

If I then tick "talk to ATC controllers" back on, the MCE UI doesn't hang as it does when unticking, but with it ticked once again ground services then again stops working.  At least behavior is consistent !

 

So I still don't know why enabling ATC kills the GSX/AES kickstart, or why I can't untick "talk to ATC controllers", but does this rule out the joystick button and FSUIPC as a cause ?

 

What else can I try ?

 

 

What else can I try ?

 

To take the joystick out of the equation, take this different approach.

 

Disable MCE ATC feature

Disable MCE joystick monitoring for other ATC systems ("UseWithVoxATC=0" in mce.ini)

 

Now, instead of emulating the DEL key in FSUIPC, emulate  <END> key down and <END> key up.

Making some progress:

 

Set yoke button with FSUIPC to send END, rather than caps lock.  (However I left the FSX PTT default keyboard assignment as caps lock.)

Set UseWithVoxATC=0 so MCE would launch with ATC disabled.

Set TalkToATCControllers=0 so MCE isn't monitoring joystick.

Launched MCE.  As expected GSX kickstarted, since ATC was disabled.

 

Then a nice surprise:

I found I was able to enable ATC using the UI by ticking "talk to ATC controllers", after a brief "getting data from current model"

Ground services remained active now even with ATC active.

 

However, after a few minutes I tried to disable MCE ATC again by unticking "talk to ATC controllers" in the UI. 

MCE hung while waiting to get data for current aircraft. 

 

In a second experiment, I set TalkToATCControllers=1 so MCE would restart with ATC already active.

I left UseWithVoxATC=0 as before.

Launched MCE, and ATC was enabled, as expected, but now GSX did not kickstart.  I tried to disable ATC using the UI - I assume I should be able to do that - but again MCE hung while waiting to get data from current aircraft.

 

So something consistently hangs the GSX kickstart when MCE starts up in ATC mode, and is preventing me from turning off the ATC mode via the UI.  No FSUIPC joystick in the loop now. 

 

Are there any other simconnect apps that could be interfering ?  I have UT2 installed but traffic is turned off.  EZDok in use, but no button assignment overlap and no joystick use.

 

BTW would you expect that if I changed the joystick button FSUIPC assignment from END to DEL, that MCE voice recognition would activate, and send my interpreted voice response to my RC4 ATC ?

 

 

BTW would you expect that if I changed the joystick button FSUIPC assignment from END to DEL, that MCE voice recognition would activate, and send my interpreted voice response to my RC4 ATC ?

 

As long as you setup 2 clear emulated keyboard events.

 

Joystick button down emulates DEL keyboard key down

Joystick button released emulates DEL keyboard key UP

 

...with no repeats and no shaky button that could trigger those events accidentally, should operate the same way as pressing DEL key which fsInsider.dll listens to.

 

Still don't understand why you prefer to emulate those keys, when MCE can monitor the assigned PTT joystick button directly.

 

Suggest you disconnect joystick completely and use keyboard only for the next session.

 

DEL key to talk to RC4 ATC

END key to talk to Vatsim.

 

See if the UI hangs when enabling/disabling ATC for instance.

Hi Ben - Happy New Year. 

 

Many thanks for helping me resolve my AES/GSX kickstart issue. 

 

 I ran the tests you suggested and made an interesting discovery:

 

• When I have MCE configured to use RC4, GSX does not kickstart but RC4 works OK using either the DEL key or when reading the joystick button set in MCE window. 
  • (Configuration was: PilotSpeaksToATC=1., GroundServicesMode=native, UseWithVoxATC=0, UseRadarContact=1 and with the del key enabled but joystick button input disabled on the MCE ATC menu.)
• When I have MCE configured for VATSIM/VPilot, GSX does kickstart correctly, and MCE works OK using either the End key or when joystick button is programmed via FSUIPC to send End key to Vpilot.  Apparently something about having MCE ATC enabled at startup is impairing the ground services kickstart.
  • Configuration was PilotSpeaksToATC=0, UseWithVoxATC=0, GroundServicesMode=native, UseRadarContact=1
• Discovery:  If I leave MCE configured for VATSIM/Vpilot as above, with MCE ATC disabled, when MCE starts, GSX then kickstarts correctly. But I discover I can then enable ATC using the “Talk to ATC Controllers”, untick the use joystick btn 2, seaving the DEL key ticked, and then start RC4 with a valid flight plan.  Since MCE has already shifted over to ATC mode, the DEL key is active and can be used for RC4 ATC voice interaction.

 

Tentative conclusion: To get consistent AES/GSX kickstart, I should always leave MCE set up for online VATSIM use (with Vatsim client programmed to respond to joystick button programmed with FSUIPC to send End key, so that UseWithVoxATC remains at the default.)  For all flights,  start MCE in the online configuration with ATC disabled, and let GSX/AES kickstart. When flying online, proceed as usual  If RC4 ATC is desired, first shift MCE back to ATC mode by ticking "Talk to ATC controllers", go to ATC tab and untick the joystick button.  Finally start up RC4 with valid flight plan. When the menus appear use DEL key for RC4 PTT voice interaction.  Note with this scheme MCE always starts up with the ATC tab dimmed, and UseWithVoxATC always remains set to zero, so there is no need to edit mce.ini.

 

Does this technique make sense ?

 

A couple of questions:

 

• Which mce.ini variable codes the joystick input checkbox on the MCE ATC tab?  UseWithVoxATC=1 ?
• After starting up RC4 with a valid flight plan, the MCE ATC tab displays my aircraft callsign and registration.  However usually the remaining flight plan information is missing and displays only ???.   Have others reported this ?  I notice that RC4Path= and FlightPlanPath= are blank in my mce.ini file.  Should they be set to something ?
• The “show ATC”, “Hide ATC” and “option1” commands described in ATC manual don’t seem to work with RC4.  Are they specific to FSX ATC window ?
• Each time I start up MCE the copilot always briefly responds as if he heard a phantom command, even though I didn’t speak into the mike.  Frequently he says something like “you see..it was selected”.  My headphones stay silent on startup, so it can’t be due to speaker-mike crosstalk.  It is a minor nuisance.  Is it common ?  Is there a fix ?
• In my mce.ini file, [VATSIM]  NotifyPTTstate=0 .  Is this the proper setting for online flying ?  What does NotifyPTTstate do ?

Regards

 

Chuck

Which mce.ini variable codes the joystick input checkbox on the MCE ATC tab? UseWithVoxATC=1 ?

 

There is no option in the MCE UI right now. That's because it's a workaround to accomodate VoxAtc.

After starting up RC4 with a valid flight plan, the MCE ATC tab displays my aircraft callsign and registration. However usually the remaining flight plan information is missing and displays only ???. Have others reported this ?

 

Assuming RC4 isn't networked, and you don't have more than one installation (some people keep one RC4 for FS9 and a separate one for FSX), and assuming MCE knows where RC4 is installed (via registry info or by supplying path), it should be able to fetch the path to current flight plan.

 

I notice that RC4Path= and FlightPlanPath= are blank in my mce.ini file. Should they be set to something ?

 

Not when RC4 is installed locally and not moved since installation. MCE will get the path from registry. On the other hand, if your RC4 folder has been moved around, select option "IgnoreRC4Registry=1" and next time you start MCE, you'll be prompted for the path to RC4 installation. Be it local folder or a networked one.

 

The “show ATC”, “Hide ATC” and “option1” commands described in ATC manual don’t seem to work with RC4. Are they specific to FSX ATC window ?

 

Good catch, thanks. Appears to be an oversight not to consider the scenario where users assign CTRL+1, CTRL+######+2 etc. Will be fixed in next version. Should work if not using CTRL or SHIFT.

You could eventually get it to work yourself using Voxkey.

 

Create your own voice command (must be different from any existing ones)

Example: "I want option one", then tie the newly created command to whatever key combination is set to trigger Option 1 in RC4 keyboard settings.

 

 

Each time I start up MCE the copilot always briefly responds as if he heard a phantom command, even though I didn’t speak into the mike. Frequently he says something like “you see..it was selected”. My headphones stay silent on startup, so it can’t be due to speaker-mike crosstalk. It is a minor nuisance. Is it common ? Is there a fix ?

 

I really can't tell. Unless everyone is getting that same prompt every time on startup.

In my mce.ini file, [VATSIM] NotifyPTTstate=0 . Is this the proper setting for online flying ? What does NotifyPTTstate do ?

 

No use for most users. When enabled, you just get noticication via text in red font, that MCE has switched from ATC mode to Normal mode and vice versa. For some it's great, for others it's a nuisance

 

 

Good to hear you found a workaround for your usage scenario.

 

Answers embedded above.

 

Happy New Year.

I hoped that the new update 2.6.3.3 would solve my pushback problem with GSX. Since GSX was upgraded to include the de-icing window, mce-mediated pushback does not work anymore.

 

I call ground for pushback, and mce makes the selection in the first GSX pop-up window. However, when the de-icing windows appears, nothing happens. Eventually, the de-icing windows closes after two seconds. Even if there are no de-icing conditions, mce-mediated selection stops at the first GSX pop-up window, and no pushback.

 

I can only push by hand-select the option in the GSX window.

 

Any idea how to solve the problem?

Chris

Hello,

 

GSX interface is working well except when it ask to choose a pushback direction left/right.

I see the GSX direction choice dialog opened and closed by MCE, but GSX pushback sequence does not start.

 

If I start GSX pushback manually (Ctrl+F12...) then the pushback starts and everything is going well: after end of pushback I can request ground to disconnect and so on.

 

I'm using last MCE version 2.5.994 and test is done with Majestic Q400 at Aerosoft Heathrow airport.

 

Thanks for your support.

 

Roland

Hello,

 

I am having this identical problem also. Was there a reply or answer to this question?

 

Regards,

Michael.

Michael,

 

No solution yet, but they are aware of the problem!! ;-)

 

 

I am having this identical problem also. Was there a reply or answer to this question?

 

Should be fixed in latest V2.6.3.8

 

http://www.multicrewxp.com/Downloads.html

Should be fixed in latest V2.6.3.8

 

http://www.multicrewxp.com/Downloads.html

Yup, the problem was fixed with the new version 2.6.3.8 release.

Thanks very much.

 

Regards,

Michael.