OrtegaS

mpi_gns.gau = 8/19/2016 1:41 PM 12,214 KB

Yes the GNS.ini file is there and contains the remark. ie. [GNS] CheckForUpdates=NO GpsRedrawRate=4 NrstRange=100 MAP_ORIENTATION=TRACK_UP AUTO_ZOOM=NO SHOW_TRACK_VECTOR=YES SHOW_WIND_VECTOR=YES SHOW_TOPO_DATA=NO SHOW_TOPO_SCALE=NO SHOW_TERRAIN_DATA=NO SHOW_OBSTACLE_DATA=NO NAVDATA=REALNAV WAASENABLED=NO [AIRCRAFT.DEFAULT] ChecklistFile= Style= ShowBezel=YES AnimateStartup=YES [KEYBOARD] GPS1_COM_VOL_PRESS= GPS1_NAV_VOL_PRESS= GPS1_COM_FREQ_TOGGLE= GPS1_NAV_FREQ_TOGGLE= GPS1_LARGE_CV_INCR= GPS1_LARGE_CV_DECR= GPS1_SMALL_CV_INCR= GPS1_SMALL_CV_DECR= GPS1_SMALL_CV_PRESS= GPS1_CDI= GPS1_OBS= GPS1_MSG= GPS1_FPL= GPS1_VNAV= GPS1_PROC= GPS1_RANGE_INCR= GPS1_RANGE_DECR= GPS1_DIRECT_TO= GPS1_MENU= GPS1_CLR= GPS1_CLR_HOLD= GPS1_ENT= GPS1_LARGE_GPS_INCR= GPS1_LARGE_GPS_DECR= GPS1_SMALL_GPS_INCR= GPS1_SMALL_GPS_DECR= GPS1_SMALL_GPS_PRESS= GPS1_RAIM_PREDICTION_FAILURE_TOGGLE= GPS1_RAIM_ACTUAL_FAILURE_TOGGLE= GPS1_FAIL_GS_TOGGLE= GPS1_FAIL_GS_SET= GPS2_COM_VOL_PRESS= GPS2_NAV_VOL_PRESS= GPS2_COM_FREQ_TOGGLE= GPS2_NAV_FREQ_TOGGLE= GPS2_LARGE_CV_INCR= GPS2_LARGE_CV_DECR= GPS2_SMALL_CV_INCR= GPS2_SMALL_CV_DECR= GPS2_SMALL_CV_PRESS= GPS2_CDI= GPS2_OBS= GPS2_MSG= GPS2_FPL= GPS2_VNAV= GPS2_PROC= GPS2_RANGE_INCR= GPS2_RANGE_DECR= GPS2_DIRECT_TO= GPS2_MENU= GPS2_CLR= GPS2_CLR_HOLD= GPS2_ENT= GPS2_LARGE_GPS_INCR= GPS2_LARGE_GPS_DECR= GPS2_SMALL_GPS_INCR= GPS2_SMALL_GPS_DECR= GPS2_SMALL_GPS_PRESS= GPS2_RAIM_PREDICTION_FAILURE_TOGGLE= GPS2_RAIM_ACTUAL_FAILURE_TOGGLE= CURRENT_SMALL_GPS_INCR= CURRENT_SMALL_GPS_DECR= CURRENT_LARGE_GPS_INCR= CURRENT_LARGE_GPS_DECR= CURRENT_ENT=

That is correct. I am trying to create a flight plan. Just about all waypoints that I am trying are not available. Gobby, Embow, Yenns etc....all points around KSAT.

Hello, I've seen this topic before, but I am not able to solve my own issue. The GNS boots up with the latest installed cycle from Real Nav Data as 1607 and the software ver in aux pages confirms this. My latest gauge dates are mpi_cdigauge 11-24-14, mpi_gns 8-19-16. I have downloaded the latest ver a few times and reinstalled as per the instructions using the admin process. I've reinstalled the real nav data a few times and run the activation process a few times for the gauge. Non of this seems to work. None of the waypoints I am trying are recognizable. This def seems to be system related. Not sure what else to to do. Thanks Steve

Hello, Regarding approaches, the GNS 530 always goes into suspend mode for any hold procedure on an approach. Shouldn't the GNS 530 fly the appropriate holding pattern then continue with the approach? Or, is this normal behavior-having to manually fly the hold then unsuspend and continue (the depicted holding pattern goes magenta like it wants to fly it but it always turns inbound on the next leg)? Also, after unsuspend it doesn't automatically pick up the next fix. I have to select the next waypoint and activate the leg in the menu item. Is this normal as well? Thanks! Steve

Hello, When executing approaches the GPS window only shows "APP" instead of LPV, LNAV+V, etc-not the actual type most suited or downgraded to in case of some kind of outage or failure. The appch itself seems to work smoothly and the vertical guidance appears to be right on. I even created a 2D popup gauge using one of the two analog gauges Mindstar provides to use with A/C that don't yet have vertical guidance in their gauge and that showed correct behavior as well. I cannot delete any fix on any given apch segment or from any STAR or SID thats "pre-configured." I can only delete actual fix names that I input. I don't receive any liability warnings that "......for guidance only" etc. The OBS button does not seem to unsuspend the unit for continued "fix following" on an appch, nor does it seem to suspend the unit for multiple manual holding patterns-each select of the OBS button allowing for another turn in holding. Is this current correct behavior? I searched the forum and couldn't find this. Sorry if its been discussed already. Also I tried to load a SID off KSAT and incorrect fixes were displayed. The LEJON3. ie RW#, "alt", Manseq, SAT. Instead of SAT, TATAR, CSI. Is this a RealNav query? Thank you very much. Steve

Hello, Ed, Is your KAP140 capable of WAAS autopilot guidance? I am interested in this gauge. Does your KAP140 work with all A/C? Even those that do not have an default autopilot. thanks, Steve

Hello Cees, Sorry for your troubles. If you read my posts it appeared there was a conflict(issue) with EZCA. At least looking at my Event Viewer indicated a problem with it. I don't think, for me, there ever was an issue with the Mindstar gauge. Uninstalling EZCA solved my freezes. After reinstalling, I'm still experiences no issues so it might have corrected a corruption somewhere. If you have been experimenting with the *.cfg files I would look there. If you don't use EZCA (as a possible culprit like in my case), then use FSX with an A/C that you are not trying to use the Mindstar gauge with. If you can pull up 2D panels (pop ups) using the click spots or the shift+X without issue, then maybe your are not coding your .cfg files the right way. That really sounds like your doing something wrong. I have both and they work ok. Good luck, Steve

Hello, I was just about to post. Yes it is a view prgm. I uninstalled it. Ran FSX for the longest period without issue. I actually stopped the pgm intentionally. Reinstalled EZCA and still no issues (no freezes.....as of yet.) I have run it the longest without interruption. So I might venture it was EZCA somehow-logic says anyway. I hope I'm good to go at this point. Thank you very much. If you dont mind? I know there is no map but no fix names are visible above 15nm.....? and LPV appchs or ILS appchs do not indicate a Glideslop dev indicator ...correct? Thank you again, Steve

Thank you. There does not ever seem to be an error msg associated with this issue. It does not crash to desktop. It simply freezes as is. There is still sound related to the current attitude. But I can do nothing else with FSX. Its like a picture with sound. This seems to happen whenever I move from the V/C to a 2d popup panel of the GNS. Back and forth. I didn't see any error generated from FSX in the event viewer, but the "information" side had this: og Name: Application Source: Windows Error Reporting Date: 7/28/2016 12:27:47 PM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: MainBang Description: Fault bucket 107719236887, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: EZCA.exe P2: 1.1.8.7 P3: 2a425e19 P4: StackHash_1410 P5: 0.0.0.0 P6: 00000000 P7: c0000005 P8: PCH_F6_FROM_ntdll+0x0007718C P9: P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_EZCA.exe_4c287196e0de6cc28cf736a7bbb5d3687a2_794a7b46_26ec22c4 Analysis symbol: Rechecking for solution: 0 Report Id: 2ee114f6-086c-4c8d-a4ab-ff53906a3d81 Report Status: 0 Hashed bucket: 3b2c0c93909d336b8ae44df53e453217 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-07-28T17:27:47.433693000Z" /> <EventRecordID>37972</EventRecordID> <Channel>Application</Channel> <Computer>MainBang</Computer> <Security /> </System> <EventData> <Data>107719236887</Data> <Data>1</Data> <Data>APPCRASH</Data> <Data>Not available</Data> <Data>0</Data> <Data>EZCA.exe</Data> <Data>1.1.8.7</Data> <Data>2a425e19</Data> <Data>StackHash_1410</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>PCH_F6_FROM_ntdll+0x0007718C</Data> <Data> </Data> <Data> </Data> <Data> </Data> <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_EZCA.exe_4c287196e0de6cc28cf736a7bbb5d3687a2_794a7b46_26ec22c4</Data> <Data> </Data> <Data>0</Data> <Data>2ee114f6-086c-4c8d-a4ab-ff53906a3d81</Data> <Data>0</Data> <Data>3b2c0c93909d336b8ae44df53e453217</Data> </EventData> </Event> Thank you, Steve

Hello, It seems when i install the Mindstar GNS430/530 into an A/C where VC gauges are used the sim locks up after a few min of play. If i disable that, then all seems well, but the VC gauges are blank and clickspots are disabled. I have to use SHIFT + X to pop up the panel and use that way. It would at least be nice to have some display in the VC gauge while using the 2D pop up. I know each developer is different, and have even read of some of the same issues elsewhere online, but it doesnt seem to be that prevalent. If you don't mind checking to see if I missed something plz. I used the Milviz C310 installer which has a mindstar installer. Real Air i tricked the configurator into thinking there is a RXP gauge with a dummy file RXPgns.dll in the guages folder then altered those entries with mindstar entries. I hope I'm missing something, but these are their entries, with a few minor differences to suit my needs. These issues were present even before I made minor changes. My changes are in red. Thank you, Steve // This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com // Built Tuesday, July 22, 2014 at 18:46 FSPS Build:22767 [Window Titles] Window00=Main Panel Window01=Throttle Window02=Copilot Window03=Engine Panel Window04=Electrical Panel Window05=C310 Prelight Window06=Mindstar GNS530/430 [VIEWS] VIEW_FORWARD_WINDOWS=MAIN_PANEL,THROTTLE_PANEL,GPS_PANEL VIEW_FORWARD_DIR=10.000, 0.000, 0.000 //-------------------------------------------------------- [Window00] file=Main_Panel.bmp size_mm=1680,1050 window_size_ratio=1.000 position=7 visible=1 ident=0 window_size= 1.000, 1.000 window_pos= 0.000, 0.000 gauge00=C310_XMLGauges!FBS_KAP140, 856,777,392,117 gauge01=C310_XMLGauges!KR 87 ADF, 1280,600,392,99 gauge02=C310_XMLGauges!C310_DME, 25,737,150,75 gauge03=MilVizC310!EDM700_L, -9,850,200,198 gauge04=MilVizC310!EDM700_R, 206,852,200,198 gauge05=C310_XMLGauges!C310_Airspeed Indicator, 220,450,169,169 gauge06=C310_XMLGauges!C310_Vertical Speed, 648,657,169,169 gauge07=C310_XMLGauges!C310_Altimeter, 648,449,169,169 gauge08=C310_XMLGauges!C310_RMI_NAV_Source, 612,989,24,24 gauge09=C310_XMLGauges!C310_HSI_NAV_Source, 507,844,24,24 gauge10=C310_XMLGauges!C310_RMI, 648,868,169,169 gauge11=C310_XMLGauges!C310_HSI, 413,644,202,194 gauge12=C310_XMLGauges!C310_TurnCoordinator, 220,657,169,169 gauge13=C310_XMLGauges!C310_Clock, 62,597,117,117 gauge14=C310_XMLGauges!CopilotPanel, 1010, 337 ,546,48 gauge15=C310_XMLGauges!EnginePanel, 444,927,151,53 gauge16=C310_XMLGauges!ElectricalPanel, 444,983,151,64 gauge17=C310_XMLGauges!ThrottleQuad, 1399,844,279,208 gauge18=C310_XMLGauges!C310_Gear_Flap_Panel, 858,906,529,153 gauge19=C310_XMLGauges!C310_Fuel_Low_Left, 1557,829,25,25 gauge20=C310_XMLGauges!C310_Fuel_Low_Right, 1623,829,25,25 gauge21=C310_XMLGauges!C310_Artificial_Horizon, 413,442,202,194 gauge22=MPI_GNS!GNS530, 856,494,392,283,1:3:0 gauge23=MPI_GNS!GNS430, 1280,416,392,184,2:3:0 //gauge22=C310_XMLGauges!FBS_GNS430_2, 1280,416,392,184 //gauge23=C310_XMLGauges!FBS_GNS530_1, 856,494,392,283 gauge24=C310_XMLGauges!BK_AudioPanel, 856,416,392,78 gauge25=C310_XMLGauges!FBS_GTX330, 1280,699,392,104 draw_order00=gauge22,gauge23,gauge03,gauge04 //-------------------------------------------------------- [Window01] Background_color=0,0,0 size_mm=296,547 window_size_ratio=1.000 position=8 visible=0 ident=10030 window_size= 0.176, 0.514 window_pos= 0.834, 0.486 zorder=2 gauge00=C310_XMLGauges!C310_ThrottleQuad, 0,0,286,547 //-------------------------------------------------------- [Window02] file=Copilots_Panel.bmp file_1024=Copilots_Panel.bmp size_mm=824,1050 window_size_ratio=1.000 position=0 visible=0 ident=10040 window_size= 0.500, 1.000 window_pos= 0.510, 0.000 zorder=1 gauge00=C310_XMLGauges!C310_Clock, 649,947,106,106 gauge01=C310_XMLGauges!C310_Manifold_Press, 33,455,164,164 gauge02=C310_XMLGauges!C310_Airspeed Indicator, 442,864,164,164 gauge03=C310_XMLGauges!C310_RPM, 33,660,164,164 gauge04=C310_XMLGauges!C310_FuelFlow, 33,864,164,164 gauge05=C310_XMLGauges!C310_FuelQty, 235,659,164,164 gauge06=C310_XMLGauges!C310_LeftEngineTemps, 235,457,164,164 gauge07=C310_XMLGauges!C310_RightEngineTemps, 442,457,164,164 gauge08=C310_XMLGauges!C310_EGT, 442,659,164,164 gauge09=C310_XMLGauges!C310_Suction, 649,661,106,106 gauge10=C310_XMLGauges!C310_OAT, 649,804,106,106 gauge11=C310_XMLGauges!C310_DoorSeal Switch, 646,539,24,24 gauge12=C310_XMLGauges!C310_Fuel Qty Switch, 304,859,27,24 gauge13=C310_XMLGauges!C310_FuelTest_Left, 236,841,30,30 gauge14=C310_XMLGauges!C310_FuelTest_Right, 376, 841 ,30,30 gauge15=C310_XMLGauges!CopilotPanel, 0,341,546,48 //-------------------------------------------------------- [Window03] file=EnginePanel.bmp file_1024=EnginePanel.bmp size_mm=789,196 window_size_ratio=1.000 position=0 visible=0 ident=10050 window_size= 0.400, 0.179 window_pos= 0.000, 0.830 gauge00=C310_XMLGauges!C310_EnginePanel, 0,0,798,196 gauge01=C310_XMLGauges!EnginePanel, 0,142,789,53 gauge02=C310_XMLGauges!EnginePanel, 0,0,789,30 //-------------------------------------------------------- [Window04] file=ElectricalPanel.bmp file_1024=ElectricalPanel.bmp size_mm=800,102 window_size_ratio=1.000 position=0 visible=0 ident=10060 window_size= 0.520, 0.120 window_pos= 0.000, 0.880 gauge00=C310_XMLGauges!ElectricalPanel, 0,0,800,27 gauge01=C310_XMLGauges!C310_ElectricalPanel, 0,0,800,102 //-------------------------------------------------------- [Window05] Background_color=0,0,0 size_mm=500,243 window_size_ratio=1.000 position=0 visible=0 ident=70 window_size= 0.400, 0.324 window_pos= 0.000, 0.040 gauge00=C310_XMLGauges!C310_Preflight, 0,0,500,243 //-------------------------------------------------------- [Window06] Background_color=0,0,0 size_mm=800,910 window_size_ratio=1.000 position=7 visible=0 ident=11013 window_size= 0.340, 0.580 window_pos= 0.660, 0.420 zorder=99 gauge00=MPI_GNS!GNS530, 0,0,800,581,1:2:11013 gauge01=MPI_GNS!GNS430, 0,581,800,330,2:2:11013 //-------------------------------------------------------- [Vcockpit01] file=C310_VC_01.bmp size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$C310_VC_01 gauge00=Milviz_Sound!FBGS_XMLSound, 0,0,1,1,SimObjects\\Airplanes\\Cessna 310R MilViz\\panel\\C310R_Sounds#22 gauge01=C310_XMLGauges!FBS_KAP140, 0,767,640,163 gauge02=C310_XMLGauges!KR 87 ADF, 0,630,640,134 gauge03=C310_XMLGauges!C310_DME, 649,32,300,150 gauge04=MilVizC310!EDM700_L, 658,193,350 gauge05=MilVizC310!EDM700_R, 658,540,350 gauge06=C310_XMLGauges!C310_Logic, 693,11,1,1 gauge07=C310_XMLGauges!3D_Altimeter, 681,796,283,368 //-------------------------------------------------------- [Vcockpit02] file=C310_VC_02.bmp size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$C310_VC_02 gauge00=C310_XMLGauges!FBS_GTX330, 0,376,512,136 //-------------------------------------------------------- [Vcockpit03] Background_color=0,0,0 size_mm=64,64 visible=1 pixel_size=64,64 texture=$C310_VC_03 gauge00=C310_XMLGauges!FLTPanel_dimming, 0,0,64,64 //-------------------------------------------------------- [Vcockpit04] Background_color=0,0,0 size_mm=64,64 visible=1 pixel_size=64,64 texture=$C310_VC_04 gauge00=C310_XMLGauges!InstPanel_dimming, 0,0,64,64 //-------------------------------------------------------- [Vcockpit05] file=Mindstar_GNS530.bmp size_mm=512,512 visible=1 pixel_size=512,512 texture=$MPI_GNS530 gauge00=MPI_GNS!GNS530, 0,0,512,,1:1:-1 //-------------------------------------------------------- [Vcockpit06] Background_color=0,0,0 size_mm=512,512 visible=1 pixel_size=512,512 texture=$MPI_GNS430x2 gauge00=MPI_GNS!GNS430, 0,0,512,,2:1:-1 [Color] Day=255,255,255 Night=85,85,85 Luminous=140,140,140 [Default View] X=0 Y=0 SIZE_X=8191 SIZE_Y=3384 -------------------------------------------------------------------------------------------------------------------------------------------------------------------- // Panel Configuration file // RealAir Simulations Beechcraft Turbine Duke V2 2014 Update // Panel and Gauge Programming by Sean Moloney // Copyright (c) 2014 RealAir Simulations // =============================================================================== // IMPORTANT - 'Window01' AND 'Window02' BELOW ARE RESERVED FOR GPS POPUPS AND CAN // BE OVERWRITTEN BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY // EDITING THIS FILE. IF YOU WANT TO ADD CUSTOM WINDOW ENTRIES, YOU CAN USE ANY // VALUE FROM 'Window03' TO 'Window 09'. // =============================================================================== [Window Titles] Window00=Main Panel Window01=Reality XP GNS 530 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE Window02=Blank [Window00] file=2D_Help.bmp size_mm=1024, 95 position=6 BACKGROUND_COLOR=0,0,0 visible=1 ident=MAIN_PANEL [Window01] Background_color=0,0,0 size_mm=800,910 window_size_ratio=1.000 position=7 visible=0 ident=15531 window_size= 0.340, 0.580 window_pos= 0.660, 0.420 zorder=99 gauge00=MPI_GNS!GNS530, 0,0,800,581,1:2:15531 gauge01=MPI_GNS!GNS430, 0,581,800,330,2:1:15531 //window_pos=0.739583,0.000000 //window_size=0.260417,0.300000 //visible=0 //ident=15531 //zorder=99 //gauge00=rxpGNS!GNS530,0,0,100,100 [Window02] size_mm=1,1 position=0 visible=0 ident=15600 BACKGROUND_COLOR=0,0,0 gauge00=RASDuke!Blank, 0, 0, 1, 1 [VCockpit01] size_mm=1024,1024 pixel_size=1024,1024 texture=$RAS_Duke_CFG background_color=1,1,1 gauge01=Config!Options, 1020, 1023, 1, 1 gauge02=Config!RealView, 1021, 1023, 1, 1 gauge03=Config!RadioLayout, 1027, 1023, 1, 1 gauge04=RASDuke!InitVars, 1022, 1023, 1, 1 gauge05=RASDuke!1hzCode, 1023, 1023, 1, 1 gauge06=RASDuke!2hzCode, 1024, 1023, 1, 1 gauge07=RASDuke!18hzCode, 1025, 1023, 1, 1 gauge08=RASDuke!NavCom1, 1, 2, 509, 61 gauge09=RASDuke!NavCom2, 1, 64, 509, 61 gauge10=RASDuke!ADF, 4, 127, 332, 49 gauge11=RASDuke!Xpndr, 7, 243, 305, 57 gauge12=RASDuke!Autopilot, 5, 177, 292, 62 gauge13=RASDuke!DME, 4, 305, 256, 46 gauge14=RASDuke!KA285_Annun, 512,2,337,108 gauge15=RASDuke!Annunciator_Turbine, 516, 111, 226, 245 gauge16=RASDuke!Moritz_LCD, 808, 133, 214, 259 gauge17=RASDuke!Fuel_Qty_LCD, 410, 128, 105, 86 gauge18=RASDuke!Master_Warn, 893, 1, 130, 129 // =============================================================================== // IMPORTANT - 'gauge19'. 'gauge20, 'gauge21', and 'gauge22' BELOW CAN BE OVERWRITTEN // BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY EDITING THIS FILE // IF YOU WANT TO CHANGE THE GPS ENTRIES AND DON'T WANT THEM OVERWRITTEN IN ANY // CIRCUMSTANCE THEN CHANGE THE GAUGE NUMBERS. EG - CHANGE 'gauge 19' TO 'gauge22' // =============================================================================== //gauge19=rxpGNS!GNS530, 1, 660, 504, 364 gauge19=MPI_GNS!GNS530, 1, 660, 504, 364, 1:1:-1 gauge20=RASDuke!Blank, 0, 0, 1, 1 gauge21=RASDukeTv2_Sound!Sound, 1,1,2,2,./SimObjects/Airplanes/RealAir Duke Turbine V2/Panel/Sound/RASDukeTv2_Sound.ini gauge22=RASDuke!Sound_Manager, 1,1,3,3 gauge23=RASDuke!Pressurisation, 1024, 1023, 1, 1 [Color] Day=255,255,255 Night=225,117,89 Luminous=200,200,101 [Default View] X=0 Y=0 SIZE_X=8192 SIZE_Y=6144

hello, I have quite a few at this point....PMDG B737/B777; Aerosoft A320/321/318/19; Aerosoft F14; Milviz Adv T38, F100, F86, F15; Ants T28; Captain Sim L1011; Feelthere ERJ 145; iFLY B737; Simcheck A300; Xtreme Prototypes X15; and Freeware C47....along with native FSX A/C. Watching A/C browser go through its iteration, it always gets this error when reaching PMDG 737NGX Tutorial #2 EHAM-LOWI Before Top of Descent.FLT. So I tried removing it and it was successful until it reached one of the X15 .Flt tutorial. Removing that allowed it to be successful in loading itself. But putting them back results in the same error. Yes, I noticed these seemed to be support software which seem very nice so i started to use them trying to figure out my issue. I received a dual registry error for FSX box and FSX steam. I sinced solved that but it does not resolve my original issue. Running the sim support tool FSX.CFG results in runtime error 75....Path/File access error. Strangely enough P3D V3 tool buttons all seem to work with no issues that i can tell. At this point it doesn't seem to be effecting my sim play. All this was an issue when I went to see if the Mindstar app installed successfully, noticed the tools and became curious. Thank you very much, Steve

Hello, I have both P3D v3 and MSFX steam installed and using both. I have run steam and the GNS 530/430 seems to run ok with the installed C172.....haven't really tested P3D. I have yet to integrate the gauges. My problem is when i go to apps in win 10, Mindstar and run Aircraft browser as admin i get an runtime 6 error over flow msg. Any help is appreciated. Thank you. Steve

I just purchased this product via paypal and was sent a receipt from them and an email from PMDG with order #; order code; and FSX key. I clicked on the download link from the email and this is what I receive: "Error: Your request ID is incorrect. Please contact store administrator for more information." Also logging onto PMDG site doesn't show my purchase history of B777. I did buy from PMDG site. I sent a ticket but was wondering if anyone had this and solved. Thanks. Steve Ortega Figured it out!!!!!!!!!!!!

Hello, Thank you for the reply. I had kept after it and found a solution that worked for me. See my post here: http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=3853 Thanks Steve

Hello, I have the exact same error message. Did you solve this issue? Thanks Steve

Hello, If a GPS failure occurs would my only indication be a switch from "GPS" to "IRS" in the ND display and maybe an FMC msg? Meaning a lateral or vertical error indication is displayed only because either the primary, secondary, or even 3rd backup has gone OTS? If so, would this mean an out of limits caution would be advisory only and execution of the appch would still be allowed because you have an ANP value that is still better than the required RNP value? Or do you only get an error when all this equipment has failed all together(outside factors not withstanding) forcing a discontinuation of the appch? Lastly, wouldn't the failure backup sequence actually be....GPS, Radio Nav, ADIRU? Still learning......... :-) Thanks Steve Ortega Wondering if PMDG has plans to update the NGX for RF.

Hello, Really good information. Scandinavian13 thanks for the link. Interesting ready though slow. In the sim ANP is always good. I cant think of any reason why I wouldn't be able to shoot an RNP appch using the lowest min's or why my tolerances would ever go yellow inside the FAF, Unless mag dec changed so much between FSX inception and current data base, but even then I'm not sure. Thanks copper. NGX can only do one decimal place. Figured that one out. But as mentioned above in FSX it doesn't really matter. Also, when is it appropriate to change the MCP altitude to your missed appch alt? Doing so with LNAV and VNAV engaged and auto pilot still active seems to effect the NGX. Is it always done after disabling auto pilot? Got to love this stuff.... :-) Thanks, Steve Ortega

Hello, I reflew the same appch into KSEA and was successful in inputting 0.1 into the CDU. I do believe though that I should be able to input 0.12 as this is on the appch chart. I am not absolutely sure of this as I am not a real B737 pilot :(. Also, some of the radius to fix dont look so RF. Some are more straight line instead of curved. Is this a NGX display or data quirk? I am using the NavData Pro set as I understand that at this point Navigraph does not yet support this feature. Thanks, Steve Ortega

Hello, Thanks. I will try using just the single value after the decimal. I wasn't sure if its a limitation of NGX or an input "sequence." From what I have read the FMC always allows you to fly the RNP appch of the most restrictive min's without user input, but if you wish to actually fly the lower min's you must actually input the RNP DA value. I'm not 100% certain though. Thanks. Steve Ortega

Hello, What is the lowest RNP cat appch the NGX is capable of? I flew the RNAV (RNP) Z RWY 16L into KSEA and had to use the min's for RNP 0.30 DA since I was unable to input 0.12 into the FMC for the lower min's. Is this even possible? It seems that since the ANP is usually around .02 this shouldnt be an issue. Thanks, Steve

Hello, Ok, thanks for the reply's. Hopefully it will be fixed soon. Will check the cold and dark vs normal startup routine. Steve

Hello, When selecting Radio from Baro on the EFIS, 9980 always is displayed as the selected value instead of 200. Any ideas why? Or should I be doing something different. Thanks Steve

Hey all,I have been using the Be1900c in FSX for quite some time now. After installing REX 2.0 (maybe coincidental) I noticed that when I go to FSX-Aircraft-Fuel and Payload- and change fuel option.....the capacities have all changed. The aux are 92.7 and the left and right are 241.9. They used to be correct. Somehow these changed. Anyone know how this happened or better how to fix this? Thanks a bunch.Steve Ortega