Warren Allred

Fine. 😕

The reality XP GTN upgrade broke my F1 GTN program with an incompatible trainer. When i put back the old F1 supported trainer it broke RXP. Uninstalled the trainer and used the link via F1 to download their supported trainer instead of my old copy of the trainer (2.4.0.0) buth then Flight GTN was still saying it was the wrong version. After much digging found out there was an update to the Flight GTN product that I was not aware of nor notified of so I had to install that version - Reinstall the recommended trainer for that one and it is working in Reality XP. 3 hours of great fun LOL. Seems F1 doesn't have something you can run to check for updates like Reality XP does - So one has to go into the forums and find it out. I hate chasing upgrades - So many add-ons on 2 different platforms makes it a constant chore.

Found in the manual how you have to do some hoop jumping and copy directories around and set environment variables. What a kludge - Amazing you can't coordinate your two products.

Did it and it broke my F1 GTN 750 for P3D. Say (GTN750 doesn't support current Garmin Trainer) What are my options? Uninstall and reinstall and try to figure what level to upgrade too?

Do this: // This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com // Built Sunday, March 10, 2013 at 15:50 FSPS Build:20207 // changed Aug 10 HN // changed Sep 3 HN // changed Sep 11 HN // changed Oct 16 MJ [Window Titles] Window00=Main Panel Window01=Fuel and Payload Window02=Control Panel Window03=Monitor Window04=Clipboard Window05=Flight1 Garmin GTN750 U1 - DO NOT MODIFY Window06=Flight1 GTN Stack - DO NOT MODIFY Window08=GCA Window10=Monitor Help Window11=Keys //-------------------------------------------------------- [Window00] Background_color=0,0,0 size_mm=1024 position=2 visible=1 ident=MAIN_PANEL gauge00=C47!Main, 0,0,1,1 //gauge01=fsx_event_logger!event_logger, 0,600,120,73 //-------------------------------------------------------- [Window01] Background_color=0,0,0 size_mm=220,376 pixel_size=275,470 //220,376 ori position=0 visible=0 ident=10003 window_pos=0.00, -0.08 type=SPECIAL gauge00=C47!Status, 0,0,275,470 gauge01=C47_dsd_p3d_fuel_dump_x64!display, 10,850,515,63 //-------------------------------------------------------- [Window02] Background_color=0,0,0 size_mm=220,376 pixel_size=275,470 // 220,376 ori position=0 visible=0 ident=10004 window_pos= 0.00, 0.80 type=SPECIAL gauge00=C47!Control, 0,0,275,470 //-------------------------------------------------------- [Window03] Background_color=0,0,0 size_mm=924,150 pixel_size=924,150 visible=1 ident=10001 window_pos= 0.45, 0.05 type=special gauge00=Monitor!mon, 0,0,924,150 //-------------------------------------------------------- [Window04] Background_color=0,0,0 size_mm=275,406 pixel_size=275,406 visible=1 window_pos= 0.45, 0.925 type=special ident=10014 gauge00=Clipboard!clipboard, 0,0,275,406 //-------------------------------------------------------- [Window05] Background_color=0,0,0 size_mm=937,887 ident=14401 zorder=99 gauge00=F1GTN!GTN750, 0,0,937,887,UNIT1.POP window_pos= 0.660, 0.160 window_size= 0.340, 0.580 //-------------------------------------------------------- [Window06] size_mm=255,1039 Position= 0 window_size= 0.058, 0.243 visible=1 ident=14400 zorder=100 gauge00=F1GTN!GTNStack, 0,0,255,1039 [Window08] Background_color=0,0,0 size_mm=300,340 pixel_size=300,340 visible=1 ident=10010 position=8 type=special // activate the following gauges if you have Generic GCA 2.1 installed //gauge00=GCA!zzDAT37_FS9, 0,0,280,264 //gauge01=GCA!apsmall, 40,266,202,55 //gauge02=GCA_dsd_P3Dv4_xml_x64_sound!Sound, 1,1,1,1,.\Gauges\GCA\gcacalls.ini //gauge03=GCA!PAR, 0,0,1,1 //gauge04=GCA!APC, 0,0,1,1 //-------------------------------------------------------- [Window10] Background_color=0,0,0 size_mm=800,600 pixel_size=800,600 position=4 visible=0 ident=10000 gauge00=Monitor!help, 0,0,800,600 //-------------------------------------------------------- [Window11] Background_color=0,0,0 size_mm=1,1 position=0 visible=1 ident=10002 nomenu=1 type=SPECIAL gauge00=C47!Keys, 0,0,1,1 //-------------------------------------------------------- [Vcockpit01] Background_color=0,0,0 size_mm=512,512 visible=1 pixel_size=1024,1024 texture=$C117_01 gauge01=C47!Main, 0,0,1,1 gauge02=C47!Sim_C47, 0,1,1,1 gauge03=C47_dsd_P3Dv4_xml_x64_sound!Sound, 1,1,1,1,/DGSounds/CockpitSounds_C47.ini gauge04=DGSounds!KeyEvent_SND_C47, 0,0,1 gauge05=dsd_p3d_battery_charger_x64!charger, 0,0,1,1 //-------------------------------------------------------- [VCockpit02] background_color=0,0,0 size_mm=1024,1024 visible=1 pixel_size=1024,1024 texture=$dc_panel gauge00=radiosvvc!RadioDME, 11,625,230,130 gauge01=radiosvvc!comm1, 0,0,355,171 gauge02=radiosvvc!nav1, 368,0,355,171 gauge03=radiosvvc!comm2, 0,187,355,171 gauge04=radiosvvc!nav2, 368,184,355,171 gauge05=radiosvvc!adf, 0,369,355,171 gauge06=radiosvvc!xpond, 143,551,870,61 //-------------------------------------------------------- [Vcockpit03] Background_color=0,0,0 size_mm=2048,2048 visible=0 pixel_size=2048,2048 texture=$rain gauge00=Windshield!main,0,0,0,0 texture00=Windshield, 0,0,2048,2048 Day=255,255,255 Night=210,120,20 Luminous=228,64,64 [Default View] X=0 Y=0 SIZE_X=8192 SIZE_Y=6143

Because it didn't work right the first time and there are no installation logs to review to aid in troubleshooting.

Yes I get two new installers (650/750) run each as admin and click reinstall. And it appears all goes well. Did it again after cleansing the registry of all reality-XP stuff in addition to all the file directories and X-Plane plugin folders - I'll see if it pops up again.

Yes that's exactly what I am doing - With anti-virus disabled and as Administrator. Just got another popup today - Downloaded - Unzipped - Now I am out of activations since I've done it so many times.

So I download it - Extract - Have run right away, have also done a quick uninstall of the X-Plane 11 version via Control Panel and it still pops up saying I need the new update (version 2.5.22.2) - Continues to say I have 2.5.22.0 What am I missing please?

Me too - Just started tonight - Only thing I changed today was to install the PMDG 737NGXu

I was deploying flaps to help with drag but assumed that since my current FMC target speed was below the max extension limitation it would still hold the current programmed target speed. Too much Airbus and MD-88 time I guess... 🙂

So in a nutshell in full LNAV/VNAV mode on scheduled descent still 4 legs away from slowing to approach speed (scheduled on FMC is 240 - 200 - 173 - 147 - 138) and it has already slowed to 138...???? IAS/MACH MCP is blank as usual. Did something to force the aircraft to slow? What did I do? 🙂