glennav8r

You actually raise a good point there. It appears that the really old legacy G1000 had a similar font to xplane but then it appears to have changed on the latter legacy units and the NXi. Thanks for that it kind of explains it.

I agree not a priority but they have their other avionics looking pretty good. Its mainly just the numbers that jump out as being way off

You have a good point I can see him doing that 😁

Does anyone have a solution for, or know why the X-plane G1000 fonts are so far removed from the font that Garmin uses? It really distracts from the whole look and feel of the X1000. For example, the zeros have a diagonal bar through them, and the nines are just wrong in X-plane. I did a search online and there are fonts available that are almost, if not, identical to the ones that Garmin uses. I have never understood this. Glenn

Hi I just done a Google search and it was the AI answer that I got presented with. Glad you got it sorted.

I just googled it for you. In Microsoft Flight Simulator (MSFS) 2020, the "ATC Enforce Flight Plan" setting determines whether the in-game ATC will adhere to the flight plan you've loaded or if it will suggest runways and approaches based on current conditions. When enabled, ATC will generally try to align with your flight plan, but may still make adjustments based on real-time factors. When disabled, ATC will disregard your flight plan and make its own decisions about runways and approaches. Here's a more detailed explanation: 1. ATC Enforce Flight Plan ON (Default): ATC follows your flight plan: When this setting is active, the ATC system will try to assign runways and approaches that match your pre-flight plan. Adjustments based on conditions: While it generally follows your plan, ATC might still deviate from it if there are significant changes in wind, weather, or other factors. Potential for conflicts: If the ATC deviates significantly, it can sometimes create a situation where you need to manually adjust your approach or even request a different approach from ATC. 2. ATC Enforce Flight Plan OFF: ATC makes its own decisions: With this setting disabled, ATC will ignore your flight plan entirely and assign runways and approaches based on the current conditions. More dynamic ATC experience: This can lead to more dynamic and unpredictable ATC interactions, as you may be assigned different runways or approaches than you initially planned. Potential for conflicts: You might find yourself needing to request a different approach if ATC's suggested approach doesn't align with your preferences. How to adjust the setting: You can find the "ATC Enforce Flight Plan" setting in the "Assistance Options" menu under "User Experience",

You need to change Enforce ATC setting. I can't remember which menu it's under, maybe realism settings. It's always been like this but the update has probably messed with your settings.

Ed Are you able to assist with my question please, if not please advise and Ill pursue another course of action. Regards Glenn

Hi Ed I am building a HSI to use with my Mindstar 530 and need to provide an Offset or lvar from the gps to drive the glideslope needle. Are you able to point me in the right direction with this please? I know you have requested LM to implement this previously but I assume they havnt at this point. Thankyou

Okay thanks I will try the cub again after I update to p3d 2.5 and see if I can replicate the problem on a fresh install.

<?xml version="1.0" encoding="WINDOWS-1252"?> @namespace html url(http://www.w3.org/1999/xhtml); :root { font:small Verdana; font-weight: bold; padding: 2em; padding-left:4em; } * { display: block; padding-left: 2em; } html|style { display: none; } html|span, html|a { display: inline; padding: 0; font-weight: normal; text-decoration: none; } html|span.block { display: block; } *[html|hidden], span.block[html|hidden] { display: none; } .expand { display: block; } .expand:before { content: '+'; color: red; position: absolute; left: -1em; } .collapse { display: block; } .collapse:before { content: '-'; color: red; position: absolute; left:-1em; } <SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>HyperGauge</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\hypergauge.dll</Path> </Launch.Addon> </SimBase.Document>

Im sorry I cant locate this file.

// Panel Configuration file // Piper J3 Cub // Copyright (c) 2002 Microsoft Corporation. All rights reserved. [Window Titles] Window00=Main Panel Window01=Radio Stack Window02=GPS Window03=Electrical Panel Window04=Clock Window05=Mini Panel [Window00] file=Piper_J3Cub_background.bmp size_mm=1024, 768 position=7 visible=1 ident=MAIN_PANEL gauge01=Piper_J3Cub!throttle, 2, 591 gauge02=Piper_J3Cub!trim_indicator, 87, 698 gauge03=Piper_J3Cub!rpm, 198, 484 gauge04=Piper_J3Cub!airspeed, 337, 492 gauge05=Piper_J3Cub!compass, 460, 492 gauge06=Piper_J3Cub!fuel, 513, 195 gauge07=Piper_J3Cub!altimeter, 584, 492 gauge08=Piper_J3Cub!oil, 709, 484 gauge09=Piper_J3Cub!engine_primer, 811, 596 gauge10=Piper_J3Cub!mixture_carb_heat_knobs,920, 666 gauge11=SimIcons1024!Kneeboard Icon, 192, 622 gauge12=SimIcons1024!ATC Icon, 216, 622 gauge13=SimIcons1024!Map Icon, 240, 622 gauge14=SimIcons1024!GPS Icon, 264, 622 gauge15=SimIcons1024!Electrical Panel Icon, 288, 622 gauge16=SimIcons1024!Radio Icon, 312, 622 gauge17=SimIcons1024!Clock Icon, 336, 622 [Window01] BACKGROUND_COLOR=0,0,0 size_mm=208,129 position=7 visible=0 ident=RADIO_STACK_PANEL gauge00=Handheld_Radio!radio,0,0 [Window02] size_mm=456,520 window_size=0.5 position=8 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=GPS_PANEL gauge00=MPI_GNS!GNS530, 0, 0, 456, 331, 1:1:225 gauge01=MPI_GNS!GNS430, 0, 331, 456, 189, 2:1:225 [Window03] size_mm=178,313 position=0 visible=0 ident=125 // Mooney bravo panel.cfg [Window Titles] Window00=Main Panel Window01=Radio Stack Window02=GPS Window03=Annunciator Window04=Overhead Panel Window05=Mini Panel [VIEWS] VIEW_FORWARD_DIR=2.000, 0.000, 0.000 //-------------------------------------------------------- [Window00] file_1024=mooney_background.bmp file_1024_night=mooney_background_night.bmp no_luminous=1 size_mm=1024 position=7 visible=1 ident=MAIN_PANEL gauge00=Mooney_Bravo!Clock, 105, 509, 65, 37 gauge01=Mooney_Bravo!Nav GPS Switch, 115, 586, 25, 29 gauge02=Mooney_Bravo!Magneto, 93, 695, 66, 67 gauge03=Mooney_Bravo!Airspeed, 314, 415, 120, 120 gauge04=Mooney_Bravo!Turn Coordinator, 314, 555, 119, 118 gauge05=Mooney_Bravo!Master Alt Bat, 86, 629, 40, 55 gauge06=Mooney_Bravo!Avionics Switch, 131, 629, 39, 56 gauge07=Mooney_Bravo!Fuel Selector, 321, 699, 57, 57 gauge08=Mooney_Bravo!Attitude, 445, 400, 142, 135 gauge09=Mooney_Bravo!HSI, 445, 549, 141, 134 gauge10=Mooney_Bravo!Standby Vac, 390, 702, 34, 54 gauge11=Mooney_Bravo!Prop DeIce, 430, 702, 34, 54 gauge12=Mooney_Bravo!Pitot Heat, 470, 702, 34, 54 gauge13=Mooney_Bravo!Boost Pump, 509, 702, 34, 54 gauge14=Mooney_Bravo!Elevator Trim Switch, 549, 702, 34, 54 gauge15=Mooney_Bravo!Altimeter, 598, 412, 120, 119 gauge16=Mooney_Bravo!Vertical Speed, 598, 554, 119, 120 gauge17=Mooney_Bravo!Fuel Flow, 196, 686, 110, 46 gauge18=Mooney_Bravo!Altitude Alerter, 190, 493, 110, 49 gauge19=Mooney_Bravo!DME, 200, 446, 88, 43 gauge20=Mooney_Bravo!VOR2, 183, 554, 119, 119 gauge21=Mooney_Bravo!Cowl Flap Display, 594, 691, 35, 74 gauge22=Mooney_Bravo!Cowl Flap Switch, 639, 702, 34, 54 gauge23=Mooney_Bravo!Flaps Switch, 693, 715, 30, 37 gauge24=Mooney_Bravo!Left Fuel, 734, 398, 56, 50 gauge25=Mooney_Bravo!Right Fuel, 790, 398, 56, 50 gauge26=Mooney_Bravo!Amps, 846, 398, 56, 50 gauge27=Mooney_Bravo!Fuel Pressure, 734, 460, 56, 51 gauge28=Mooney_Bravo!Oil Pressure, 790, 460, 56, 51 gauge29=Mooney_Bravo!OAT, 846, 460, 56, 51 gauge30=Mooney_Bravo!Turbine Temperature, 734, 511, 56, 50 gauge31=Mooney_Bravo!Oil Temperature, 790, 511, 56, 50 gauge32=Mooney_Bravo!CHT, 846, 511, 56, 50 gauge33=Mooney_Bravo!Manifold Pressure, 732, 569, 81, 81 gauge34=Mooney_Bravo!Tachometer, 823, 569, 80, 81 gauge35=Mooney_Bravo!Rudder Trim Display, 744, 660, 75, 35 gauge36=Mooney_Bravo!Rudder Trim Switch, 843, 660, 54, 34 gauge37=Mooney_Bravo!Thrust Controls, 737, 702, 245, 66 gauge38=Mooney_Bravo!Gear Lever, 935, 416, 26, 66 gauge39=Mooney_Bravo!Elevator Trim Display, 930, 518, 34, 85 gauge40=Mooney_Bravo!Wing Flap Display, 930, 613, 33, 83 gauge41=Mooney_Bravo!Master Caution, 131, 553, 39, 25 gauge42=Mooney_Bravo!Gear Light, 930, 487, 34, 18 gauge43=Mooney_Bravo!Autopilot Switch, 139, 483, 17, 16 gauge44=Mooney_Bravo!OMI Lights, 258, 418, 39, 15 gauge45=Mooney_Bravo!Flight Director Switch,160, 483, 17, 16 gauge46=Mooney_Bravo!Speed Brake, 87, 552, 37, 26 gauge47=Mooney_Bravo!Whiskey Compass, 957, 296, 61, 44 gauge48=SimIcons!Kneeboard Icon, 198, 742, 20, 20 gauge49=SimIcons!ATC Icon, 218, 742, 20, 20 gauge50=SimIcons!Map Icon, 238, 742, 20, 20 gauge51=SimIcons!Avionics Icon, 258, 742, 20, 20 gauge52=SimIcons!GPS Icon, 278, 742, 20, 20 gauge53=n_number_plaque!n_number_plaque, 663,677,67,19 //-------------------------------------------------------- [Window01] Background_color=2,2,2 size_mm=157,270 position=8 visible=0 windowsize_ratio=1.6 ident=RADIO_STACK_PANEL gauge00=Bendix_King_Radio!Bendix-King Radio Audio, 0,0 gauge01=Bendix_King_Radio!Bendix-King Radio Nav-Comm 1, 0,29 gauge02=Bendix_King_Radio!Bendix-King Radio Nav-Comm 2, 0,86 gauge03=Bendix_King_Radio!Bendix-King Radio DME, 0,142 gauge04=Bendix_King_Radio!Bendix-King Radio Xpndr, 0,179 gauge05=Bendix_King_Radio!Bendix-King Radio AP, 0,224 //-------------------------------------------------------- [Window02] Background_color=0,0,0 size_mm=456,378 position=8 visible=0 ident=GPS_PANEL window_size=0.5 gauge00=MPI_GNS!GNS530, 0, 0, 456, 331, 1:1:225 gauge01=MPI_GNS!GNS430, 0, 331, 456, 189, 2:1:225 //-------------------------------------------------------- [Window03] Background_color=2,2,2 size_mm=156,34 position=0 visible=0 windowsize_ratio=1.6 ident=ANNUNCIATOR_PANEL

Hi again Ed. Yes 5th parameter was included. I have just installed into the Mooney Bravo and it is working! My installation in the Piper Cub does not work, only shows the bezels.I don't know why this is, I have checked and rechecked the panel.cfg. Anyhow thanks for your time and help on this one. Regards Glenn.

Hi again Ed, thanks for your reply. I have entered the line ISIMCONNECT=NONE in the gns.ini file (It didn't actually exist at all) and it has removed the error message on start up, however the units will still not turn on. I have reinstalled, reactivated and ensured that I have full permissions. Regards Glenn.

Hi there I am having trouble getting my GNS to work after not having it installed for a while. I am using current version 1.08.0005 and P3D V2.3. On startup I get the error message MPI Gauge failed to load Sim Connect interface.dll Error code 14001. After I click okay, P3D starts and the gauge displays but will not turn on. I would appreciate any help with this please as I have tried everything I can think of. I did notice that in the Mindstar folder there is no sim connect dll for V2.3 only V1.4 - V2.2 not sure if that's a clue or not? Regards Glenn.

It is even more spectacular with the standalone ORBX Milford Sound Airport scenery installed. How did you get NZSI running in 2.3 when it is not even compatible with 2.2??

Thanks for the update to 2.7. Looks like the AMP side of the VAC/AMP gauge isn't working in P3D again though.

I had updated the P3D interface to V2.61. Tested again, still no reading on the AMP side of the gauge. Have Panel Builder running on same PC as P3D.

thanks for the new 172 gauges, they look nice. I don't have a reading on the AMP side of the VACAMP gauge it is sitting on zero. I have tried different aircraft in P3d. Also, needle movement on EGTFFLOW gauge very rough compared to other needles. Regards Glenn.