New subject. I notice the plane’s landing lights are part of the nose gear, meaning there’s no point turning on the LL until the gear is down. I guess the “LL on below 10,000 feet” concept doesn’t apply with the King Air? What’s the standard operating procedure?
Recog lights below 10k.
1 Like
I saw that the PMS50 Free Version had an update, so I updated it. Fired up the King Air, and no matter how many buttons I pushed, the GTN750 never fired up. It worked fine for the Baron/Bonanza/Caravan. I reverted to the older version and got it to work in the King Air.
Question: If I purchased the TDS version of the GTN750, does that have same power-up issue, or is it strictly with the PMS50 version?
with the 2.1.95 I have not seen any issues still
edit : well I will update, even with the patchs I also still face sometimes boot issue, but unlike KingairB200, switching avionics doesn’t reset the engine damages or faillures setting
short question, when ScorpionFilm422 made his recommendation, you were still running with an older version ? did you installed the last version while the sim running ? (I don’t recomend doing this !)
if not did you reload your aircraft once the sim launched by switching it in the hangar with another one
I saw issues in past when directly jumping in an aircraft that had just been updated or part of it (like livery etc) without refreshing it by reloading and clearing cache, doing so led me to issues like the game loading old data and not properly the updated one
Nope, I’ve learned to only make changes to my Community folder when the sim is not running. 
I’ll recheck to make sure the latest GNS530 patches are installed as well.
1 Like
Be sure to update the WTT mod package for the aircraft too.
2 Likes
I updated and had this same bugged behavior yesterday. Check out 7:30 in this video. I had even used the GTN 750 breakout panel to program the flight plan in prior to this moment (around 4:14) and yet the GTN in the plane never came on through all of that. As you can see here, it wasn’t coming up for me and then I pulled up the minimenu to pull out the breakout again and just as I hit the menu button, the one in the plane initialized. 7:30 in this vid really says it all. I’ve been seeing this for the past month since purchasing this plane. I don’t recall seeing it in my 414c nor Kodiak flights in the months prior to this. I updated my PMS50 version prior to this flight and had done the patch that went out.
Yep, same. The King Air is the only one that is still flaky…Caravan/Bonanza/Baron all work immediately. Only once was I forced to restart the flight…all other times I just keep flipping switches until it turns on. And yes, I have all the latest patches.
1 Like
I had thought over the weekend that perhaps its the famed simobject limit issue in the sim that is causing the flakiness. When I am close to that limit, I start to notice strange behaviors especially in VR. If I restart a flight with the King Air after having already loaded in once, half the time the battery/alternator switches are ON and buried in the little metal safety door which is in its down position. If I have an addon airport with the King Air, that is enough to put me over with traffic. I have seen this happen in the Pipers as well which have a similar hot-swappable avionics suite and I think all of those count as discrete simobjects. In VR, because menus themselves are objects, I know I’ve hit the limit as soon as my menus stop coming up with the ESC key (while I can still hear the chime… the 3D object is just not drawn… you can see me demo THAT issue here: VR Menus not appearing | Simobject bug? - YouTube ). That happens a lot for me in this plane without GSX or other heavy addons loaded. In the Pipers, if my sim is over the limit, upon load the avionics packages will be jacked like this and more. My thinking was maybe that is why the other black squares don’t exhibit the issue as readily. All of that said, I’m aware that its all a lot of speculation on my part, but my experience with planes that don’t pack the avionics options all into 1 instance of the plane fair better than those that do, at least for VR users who may have more 3D objects (menus/etc) than mono-versions.
Not sure but this could be the issue in the WT GNS530 hot swapping code that may prevent some other gauges to power on.
You could try to install our WT GNS530 patch available here: WT GNS530 Compatibility
Think to update it when there is a new version of the WT GNS530.
1 Like
I had installed that patch, but perhaps that was before I did the PMS50 update if that order matters. I assumed that the update was doing what the patch did. I’ll give all of this some more testing over these next days and confirm that I’m in fact using all of the latest of everything. I’m 95% certain I am. Thanks for the help and I’ll see if I can confirm all of my packages are updated.
With or without that extra patch doesn’t seem to make a difference ( what exactly does it do, anyway? ) - still have to reset the KA avionics to get a working 750.
I think I found a pattern. I normally have both the (PMS50) GTN750 and GNS530W activated (both of the COMM switches pushed to the right). If I start a flight, but the cockpit panel does not display the GTN750, then the GTN750 will not power on, no matter how many buttons you push. It’s almost as if the plane doesn’t recognize that you have the GTN750 installed. I think if you simply restart the flight, the GTN750 will likely re-appear, and will work once the avionics turn on. It might be worth turning on the battery and immediately turning on the avionics to see if the GTN750 lights up…otherwise the engine start procedure will be a waste of time.
Maybe the GNS530 hot swapping issue. Try with this patch: WT GNS530 Compatibility
Yep, I’ve had that patch installed since early July.
New question. This is more PMS50 GTN750 related, but I figure since ScorpionFilm422 and NikoTin are on this thread, it might get answered faster.
When should you hit “Activate Approach” on this unit? Sometimes I just do a direct-to from Origin to Destination, and mid-flight I’ll pick an approach. The plane then switches waypoints from Dest to the IAF as expected. Sometimes when I hit the IAF, the remainder of the route turns to a white dotted line, and the plane stops following the route. I’ve tried hitting Activate Approach when in this state, but it never recovers, so I’ll just hand-fly it the rest of the way (not a bad thing). But just curious how this is supposed to work, especially given my experience with the G1000/G3000.
I am not an expert and this may not be the answer you’re looking for, but I actually never activate the approach.
I load the approach into the flight plan, then fly the GPS to the IAF, where I hit APR mode on the autopilot. It captures the localizer and assuming I’ve hit the right altitude, it captures glide slope, and I’m good to go.
I think you don’t have the WTT mode installed. Do it. You will get the better WT flight planner and AP manager. (get it on Aircraft second section).
A direct TO is different as flying a complete flight plan. If you want to fly an approach, set your origin and destination in your flight plan. Add your enroute waypoints if you have some and insert your approach. After flying your last enroute waypoint, activate your approach in the GPS.
I must concede that despite all the modifications and fixes you suggested, the boot issue still persists in the King Air, and I also encounter it occasionally. Thank you for continuously providing your assistance throughout this thread; it is very much appreciated
I have the issue 100%, no matter what patches are installed - only in the KA though.