Legacy, always…Lock is very jarring to me as a long time PC simmer 
. I regularly update TDS and I noticed there was a new update a few days ago coinciding with AAU1…but unfortunately that did not resolve the issue for me. I checked by re-installing the WTGNS package from the marketplace and had the same problem. JF support said it was definitely a thing, so 
Thinking of picking the King Air book by Tom Clements, any review on that? (The King Air Book – Volumes I & 2 e-Books | The King Air Book)
Tom C has some very interesting Kingair videos on Youtube for those that are interested.
1 Like
Really loving the King Air. Have quite some time in the AirFoillabs KA350. I’m having a blast to fly this great aircraft once again in MSFS.
Only thing really bothering me is the taxi physics. Not sure if it is the lack of MSFS native turboprop beta range/ground fine or something weird with wind while on the ground. A 10 knot headwind during taxi requires a lot of thrust to keep it rolling. In ground idle it will grind to a stop as if there is 0 momentum. Taxiing with tailwind causes it to accelerate very, very quickly. Due to lack of proper ground fine, one currently has to use only wheel brakes or actual reverse, of which the slightest amount grinds the aircraft to a stop and starts reversing it.
This is one of the very few issues bothering me. Once on the takeoff roll and into the skies, it is absolutely awesome. Hopefully the devs find a way to implement ground fine/beta or Asobo finishes their implementation of which they’ve mentioned that it is or was in development. I find it astonishing that this was not implemented with the latest turboprop physics update.
2 Likes
Hey, me too! (Although I do like the King Air quite a bit… just prefer the Van.)
Couldn´t agree more, I wonder if Asobo is ever gonna fix the flawed turboprop modeling.
Both, in my opinion.
I agree. Although the wind affecting taxispeed is much less noticable in for example the AAU1 Longitude. Let’s hope Asobo gets this and turboprop beta fixed soon. But it seems priorities are elsewhere, currently.
Have you found a solution for the TDS bug? I really love the King Air but not being able to click on the right half of the GTN750 makes it unusable for IFR flights.
It’s clickable fine if you fly from copilot seat. Move your camera there, press CTRL+F10 to save that position as new default camera for that airplane and fly mormally.
Not a great workarround but it gets the job done.
Edit: another workarround is to use both TDS NXi and WT530 at the same time and then the TDS also works ok.
I really hope all parties (Asobo, TDS or PMS, WT and the devs) can get the avionics incompatibilities sorted out soon. Going between the TDS GTNxi and the WT530 is extremely cumbersome as you have to completely uninstall one to use the other, with a restart of the sim in between. I strongly prefer the 750, but more planes use the 530, so for now, that’s all I’m keeping installed.
I can’t get APPR to function on RNAV at all. It works for an ILS landing but not for RNAV.
1 Like
What is the problem you’re having with approach mode on RNAV approaches? Is it following the lateral guidance only, but not the vertical glide path? Does the approach actually have LNAV/VNAV or LPV minimums on the chart? Is your CDI set correctly?
No perfect solution without removing the WT-GNS package. What @sle18mad said is correct (GTN + GNS avionics selection) but I have found that the GNS530 puts out garbage nav information when used in conjunction with the TDS, since TDS has to hijack the default nav system in order to work. So, to me that GNS unit becomes more of a distraction.
I have a couple of problems since AAU1 with several third party planes, including the BS analog King Air. RNAV will follow lateral guidance just fine but pressing the APPR button gets no reaction and the glide slope never appears. Perhaps resulting from the same bug is that I can’t do a cold and dark start successfully. The voltage meters never respond and if I get it started, the system will often quit during taxi, as if the batteries are not recharging. I think there’s a conflict between AAU1 and the PMS 50 GNS 750. I’m going to experiment with it today. ILS approaches still work but not RNAV.
At the moment we don´t have a real “Beta Range” in the standard SDK of the SIM. So at least the forward Portion of Beta Range from Ground Fine to Flight Detent is not realisticly simulated. Which make it really hard to get a real feeling of this range implementd.
Kind Regards
JayDee
3 Likes
Hi thank you for all what you are doing for us!!!
do you think that making prop_uselegacytables would be a good idea?
Thanks for your reply, JayDee. IIRC SWS has coded some kind of work around to omit this SDK limitation for the Kodiak. Is that a viable option for the BS KA350? Or reverting to legacytables as mentioned earlier?
Anyway, thanks for your efforts on the KA350!
I am able to fly an RNAV glide path down to minimums in approach mode on the AP every time in this plane. I’m using the PMS 750 and the KAP 140 mod. Make sure the RNAV approach you’re trying to fly actually provides vertical guidance. Not all of them do. Not sure what else could be going wrong for you, but the plane is definitely capable of it.
No I dont think so. The disadvanteges would outweight possible advantages.
Kind Regads