Search the Community
Showing results for tags 'vloc'.
Found 1 result
Hi guys, I need to get to the bottom of some issues that I've immediately experienced in both the provided configs that come default with the installation of the 430-530 as well one I have been designing on my own over the past few weeks. I'm using Prepar3D v3.3.5 in Windows 10. This is all installed on a reformatted PC so everything has been a fresh install over the past two months. I have the gauges working now but am trying to overcome some extended issues. I first built a custom 2D panel set on my own which contains 5 instances of the GNS530 only. The gauge is located on the following; 1-VFR panel, 2-IFRv1 panel, x-IFRv2 panel (not on this one), 3-CoPilot panel, 4-RadioStack panel 5-PopUp panel. Yes, I know it may be a little extreme but I'm trying to cover several options between single monitor sim use and cockpit building use. And if I need to break this panel down into two separate panels instead I can do that too. For example; using the VFR panel with the radio stack or using IFRv2 panel with the radio stack undocked or use the IFRv2 the copilot panel undocked which has the radio stack built in (and so you then don't use the radio stack popup). A planned 6th instance was going to be for the virtual cockpit but seeing that there is no other model provided that could accommodate a single GNS530 I immediately deduced that this isn't possible so only 2D it shall be. I'm pretty sure I've set everything up properly as far as window positions, zorder, and especially the unit:instance:ident values as I can see the gauges, can turn them on, and when one turns on the rest turn on etc. I am however having a problem with the old C172 Nav / GPS switch. It works once and then just stays locked on GPS and cannot be toggled back at all. This immediately creates a condition of not being able to use the autopilot properly or perhaps only being able to use it with the GPS. At first I figured this was a possible issue with either my autopilot and radio setting in the Aircraft config or was the old FSX Cessna gauges (Cessna NAV/GPS annunciator as well as the NAV/GPS switch) But....BUT.... a big red flag for me was when I looked into several of the included panel config files that Mindstar has tweaked for the C172 and I see that these same two gauges in particular are masked out so that they are not used. Oddly though it was retained in the VC, but not anywhere else on the panel. I think one of the panel sets still has it on one window, but that one to me looks much more like it was overlooked and that it too was really supposed to be erased or blocked as most all of them have the // masking to hide these two gauges. What's most disconcerting however is that I also see there are no included replacements in the configs for the nav-gps switch nor are any included with the gauge purchase. Now, don't get me wrong, I do enjoy hand flying small aircraft and realize from a training perspective that is what is done most often but in doing IFR work, various commercial practice, and long cross country flights I would greatly appreciate having a functional autopilot replete with a functional NAV/GPS switch. I think most flight simmers would agree that this is a very basic necessity we've all been accustomed to for a very long time. So either I'm missing something here or is this package is purposefully sold (*and not advertised*) as being autopilot incompatible? I seriously hope this is not the case and that I've just overlooked something simple. Ideally I wanted to install a UHF1 - GPS - UHF2 gauge that allows you to also operate a Nav 2 with glideslope. I think learning how to bounce off two VORs with the autopilot is an equally good training experience as hand flying between two are, especially if you are a more advanced pilot. I also have several larger aircraft I would like to install the GPS430/530 into such as a few business jets as well as a King Air, a Metroliner, and maybe a DC-3, etc. In short, having autopilot control and the ability to switch between NAV-GPS mode in larger aircraft is obviously crucial. Lastly, another immediate issue I noticed is that the two knob zones for radio tuning seem too small and narrow for touchscreen use and I was really hoping to try this out with a touchscreen, particularly an iPad mini because its screen is the exact size of a Garmin 530. I don't want to use my mouse and keyboard and I also don't want to have to invest into a hardware unit as I really like to keep everything virtual. Thanks for the help.