ChuckOman

Have been happily running RXP GTN Touch v6.6.1 & Trainer v 2.62.4 on my Win10 P3D5.3HF2 system. Prompted by the RXP GTN update checker, downloaded and ran the new RXP update. Seemed to finish OK, but the GTN touch opening screen still says I'm running RXP v2.6 and Trainer 6.62.4. Reran the updater, same result. The GTN touch v2.6.1 still works OK, but now the Software Update thinks I have version 2.7.1.0, and each time I restart my system, I get a Software Update reminder dialog (a Windows host Rundll 32 process, not a startup app) that 2.7.4.0 is available. So three questions: May soon update to P3D 5.4, but If I'm not planning to update to P3Dv6, do I really need the new RXP v2.7 update? If I update to RXP GTN v2.7 do I need to update to a new Trainer also? If not, and I'm happy with v2.6.1/Trainer 2.62.4), is there some way to turn off the RXP Software Update reminder? (Can't do it via Task Mgr Startup tab)? Chuck

Reporting success running installer 2.6.11 then going to existing Garmin Trainer v3.2.3 and accepting options to update the trainer and all the Xi updates and new databases. All seems working with no tweaks to existing installations...

Jean-Luc - thanks for the update! Could you remind me: can I just run the new RXP 2.6.11 installer over my existing P3D5.3 HF2 RXP GTN touch installation (2.5.3.0 and Trainer 3.2.3.0)? Will the installer offer to download the trainer update, or should I update the Trainer first and then run the RXP installer? Chuck O

Thanks. Turned off the transition altitude alerts completely in my mjcq400 profile and issues disappeared.

Hi Bryan - Was looking at my RAAS Pro for P3D UI and noticed the MISC SECTION includes two "transition" boxes, an Alt Set box, and a Repeating Alt Setting Warning. Are these documented anywhere ? I checked on http://www.support.fs2crew.com/help/manuals/page.aspx?pageid=user_interface_overview, but the MISC SECTION is simpler - perhaps you added them later. So unsure what these additional features do. I've been flying The MJC Dash-8 Q400 with RAAS Pro. Most features work fine, but I have been getting persistent "Altimeter Setting" female voice aurals that repeat every 30 sec during descent or approaches, even after I've reset the altimeters. The MJC uses a separate jbsim flight dynamics engine - could that cause a problem? Regards ChuckOman

I've encountered it even before v1.5. Presume it is a PMDG cargo version issue - panel code thinks service door 2R exists, even tho it isn't in the doors menu.

After reading earlier posts, I experimented with PMDG B737 NGXu v2.91.0122, monitoring GPU load and VRAM use with GPU-Z. On my Win10 Pro /i7 9700K/ 11GB 2080Ti system, turning on/off all the different cockpit interior and exterior lights - your mileage may differ, but on my system it made no consistent difference in GPU load or VRAM utilization.

Unfortunately nothing in the MilViz Basic Flight Plan tutorial video suggested by RudiJG1 about user created waypoints, or how to add a hold to a flight plan. Anyone know if it is possible ?

Yes, I always keep the green bar showing - that's how I discovered the recognition errors are so specific to the commands that set the NGXXu comm and nav frequencies, whereas other phrases work fine. The recognizer has no trouble with the radio commands when I dictate into wordpad, but when I say the identical phrase to FS2Crew, for some reason it messes up. I tried setting all the NGXu cockpit sounds to zero thinking that background noise might somehow be leaking from my phones across my mike, but doing that made no improvement.

Can't find any detail on FMS. Can user create waypoints ? program holds ?

Assume there is no harm in voice training, right ? I have FS2Crew working on both FSL A320 and PMDG NGXu. Command recognition is almost perfect now (high nineties) on both, except that the NGXu version struggles with the radio commands like: SET 119 point 2 0 0 ON STANDBY COMM one; SET 119 point 2 0 0 ON COMM one; SET115 point 7 0 on standby NAV one the recognition mistakes are typically substitution of "Nav" when I actually said "Comm", or omitting "standby". Odd thing is that I have trained up the speech recognizer on these specific phrases so recognition of these phrases is consistently perfect when dictating them into wordpad. Nonetheless FS2Crew still struggles with these particular radio commands when I say them in the sim. Any thoughts on why this might be? I've got the PMDG cockpit engine sounds turned down to 30, and my headset is a corsair that covers my ears completely.

Thanks. Discovering that training specific words really improves accuracy. Have added "LNAV", "VNAV", and "bug up" to my speech dictionary. Wondering about spaces in some phrases: Should I be training "QNH" to transcribe as "QNH" or "Q N H"? "APU" to transcribe as "APU" or "A P U"? "Autothrottle" or "Auto throttle" ? If this works, would it be worthwhile to post a set of FS2Crew specific words and phrases for users to train into their speech dictionaries. Or have you already done that somewhere and I've just missed it? Regards Chuck

Thanks ! So I will train recognizer to transcribe comm with two m's . Should I train it to transcribe comm "one", or comm "1" - and does it matter ? Chuck

Hi Bryan - I have been using FS2C v1.4 NGXu with some success - most commands reliably recognized. But monitoring the green window, I realize recognizer still struggles with the voice comm and nav frequency setting commands. - I have tried training specific words, but wonder: should be training "comm" to be spelled "com" or "comm" for FS2C - or does it matter ? Should I be training single digits like "two" to be recognized as "two" or "2" - or does it matter ? - Is there any issue in v 1.4 with the "set xxx.xx in comm 2" command ? It seems to always set the standby window. Chuck O

Hi Bryan - Flew the FSL A320 KSMF RNAV (RNP) Z R16R. I have v1.4, but only options are for ILS Cat I/II/III, Non Precision, Visual and Visual Pattern. RNAV (GPS) approaches are indeed non-precision, with advisory only vertical guidance, but the other variety - RNAV (RNP) approaches - are precision approaches. They are flown to precision minima and can include curved RF legs. The A320 has been flying them for half a dozen years - they are common now. After verifying the RNP value on the PROG page, the SOP is just push FCU APPR. Unlike an ILS approach you should not activate the LS. You just set the ALT window down to minimums and monitor the approach. When FINAL APP is enunciated green and you are past the FAF, you set ALT up to the missed. The autopilot follows the brick down the DH and then disconnects - you either go around or land visually. But if LS mode is inadvertently set on an RNP approach, FINAL APP never is enunciated. Setting up the altitude window up on final then messes everything, and you must go around. Confirmed that if you try to fly an RNAV RNP approach with FS2C set to ILS precision approach, since PM activates the LS , it messes the approach. Having to remember to catch and then de-select LS is yet another gotcha. Hope you can add an RNAV (RNP) precision approach option in the next release - just needs to leave the LS off. Chuck