ChuckOman

I'm also seeing no GPS glide path during LPV approaches using RXP GTN Touch 2.7.10 in XP v12.0.9-rc5 an Aerobask Legacy RG v12.1.r1 (latest versions of all three). ILS approach GS CDI appears normally. I tried ticking ON the RXP GTN Advanced Settings "Use Simulator GPS Commands" but it made no difference. Gather from HeinzXP's post that this has been seen since XP v12.08 in both LR and now aerobask a/c. Perhaps caused by a change in dataref, presumably affecting both LR and 3rd party (e.g. Aerobask) aircraft. Is a fix possible from the RXP side, so we can fly LPVs?

Hi Gerald - Many thanks for quick response. To troubleshoot I disabled FSUIPC <END> key transmission, made the fsinsider.ini VatsimPTT=32 change you suggested, and then set [GAMEPAD] UseWithVoxAtc=1, and verified [FEATURES] PilotSpeaksToATC=0. Then tried to run MCE. Pilot boards but MCE hangs, and any attempt to use the UI crashes MCE. I never see the red "Ready to go!". Set UseWithVox=0, and MCE starts normally. However, to my surprise, even after setting VatsimPTT=32, holding space bar gives me the mouse look cross pointer (so the key is being sent) but it does not mute MCE FO speech recognition. So UseWithVox=1 is messing up MCE startup somehow. I'll email my mce.ini to support, so you can have a look. What should I try next ? Would it be useful for me to turn on debug and obtain a startup log ? Chuck O

Hi Ben and Gerald - Using 2.7.4.2 on P3Dv4 for several months now - launches, kickstarts and generally works well. But recently when I resumed flying online with human ATC, I noticed that MCE copilot was responding to my human ATC conversation. Using prior versions of MCE with FSX and P3D3, I'd set up a PTT JS button via FSUIPC to send an <END> key when pressed, and this inhibited voice recognition per p. 10 of manual. I gather those keys were hard coded in MCE. But now with this MCE version, when a push PTT (or just press <END> or <SPACE> keys on keyboard, MCE voice recognition isn't inhibited. Are the <END> and <SPACE> keys still functioning ? Any idea why they aren't working ? I assume that as in prior MCE versions, "talk to ATC controllers" and the ATC tab in the UI should not be enabled - that is still just for AI ATC like RC4 or VOXATC, where you want MCE to parse voice commands and send them to AI ATC. (Based on CoolP's post (forum pinned MCE hints and tips), I tried setting UseWithVoxATC=1, but it crashes my MCE. Perhaps that post is dated now. I think I remember Ben telling me that this only works if ATC tab is enabled.) What is currently the best way to configure MCE for online human ATC, using a client like Pilot Edge that is looking for a keyboard key ? Regards Chuck O

This P3D flat switch problem is present in other P3D aircraft, such as the P3D version of the FSLabs A-320X. The A320 has many flat switches on the overhead systems panel. Hence all the MCE A320 voxscripts involving hydraulic, fuel, pneumatic and APU unfortunately are inop in P3D version, at least for now.

Experimenting, I discover the FSL standby frequency slot and FSL frequency swap buttons work as a separate system, independent from the FSX active and standby windows and swap function. But you don't have to use them. You can "set comm1 xxx.xx" and then "swap comm1" to put xxx .xx in the hidden but functional FSX standby slot. Works fine as long as you remember what you put there - it won't appear in the FSL standby window, or get swapped if you push the FSL swap button. You must use MCE's FSX radio swap command for that. You can put frequencies into comm2 active and standby in a similar way, and then say "select comm2" to use them. Only issue then is that you wind up listening to both radios. You'll have to punch off the audio on comm1 manually.

MCE won't set A320 Standby comm radio: MCE 2.6.9.8 and FSX FSLabs A320V 1.0.1.197: MCE command "set standby comm1 (or 2) xxx.x" works well on other aircraft, but seems not to work on the FSL A-320. Frequency is parsed and is read back correctly, but doesn't appear in the standby window. If I then say "swap comm1" the frequencies in the window swap, but the frequency I previously tried to enter in standby doesn't appear on the left side. However when I look at FSX radio frequencies using another utility (Plan-G v 3.1.2 navcomm radio panel) the standby frequency does get set by MCE. So somehow the MCE command isn't getting passed to the custom FSLabs comm standby window.

Recently started flying the Level-D 767 again, this time using MCE. I've been using MCE 2.6.5.6 and most generic commands and Level-D specific checklists and voxscripts work fine. However I can't find a functioning generic or Level-D 767 specific command to open the forward or aft cargo doors. I recall the MSFS aft cargo door command changed between the FS9 and FSX versions. Could it be that the MCE commands to run the doors were written for the FS9 version and weren't updated ? The default FSX keyboard commands shift + E, 2 and shift + E, 3 work fine. But when I ask the MCE mechanic to open/close the cargo doors, the main exit opens and closes. This in turn causes problems using GSX which checks door status during boarding/deboarding. I tried creating a VoxKey script, but VoxKey can only generate one keyboard command at a time, not two in close sequence as is required to open/close the doors. Is this something that is easy to fix ?

Ben - looking at mce.ini in the latest version, noticed a few edits. I see a [VATSIM] group not in my earlier versions and a NotifyPTTstate=0. What does this do ? Previously when I wanted to switch from using RC4 to fly online using a VATSIM SB4/vPilot/PE client ATC, I hat to edit[GAMEPAD] UseWithVoxATC=1. Do I still need to do that ? Are there any other mce.ini variable changes we should know about ? Chuck

Should MCE users who fly online with Squawkbox/FSInn/vPilot at a joystick PTT button: set [GAMEPAD] UseWithVoxATC=1 ? set [OPTIONS] AtcMikeUseIvao=0 ? Is there a way to update the NavData files in the MCE folder ? Can't find any mention in manuals or this forum.....

I've tried the various suggestions for dealing with the Radar Contact 4 handoff acknowledgment problem, but none seem to work consistently enough - at least for me - to avoid frustration. RC4 says there won't be an RC5, so this problem is unlikely to be fixed. But I've found another workaround that I now prefer: Set up RC4 with "play pilot .wavs" set to on. Find and download William Reynolds RC4 voicepack for RC4 so you have a voice similar to MCE copilot William. When you taxi out, say "you have the radios". Your MCE copilot will acknowledge all routine transmissions - you'll hear him do it. But you can still intervene with ATC requests in the usual way without having to say "I have the radios" - RC4 allows this. I've now made several trips this way, and have never been nagged !

I'm running REX2.3 with PMDG 737NGX/EXCA/UT2 on a gaming box with NVida 560GT, and enjoy high frame rates.But I still consistently get the arrow/hand mouse flicker when mousing over a hotspot.However discovered that if I close the REX2 GUI, but leave the REX2 weather engine running, the flickering goes away.I'm guessing the REX2 GUI (main program) talks to FSX or the weather engine in a way that messes the cursor graphics.Is that consistent with what you guys see ?Turning off REX2 GUI doesn't sem to be a problem, unless you want to change options or need it to check weather.