King Air 350i Build 0.0.39

[Turbofandude]

Folks,

Build 0.0.0.39 is available here: King Air 350i Build 0.0.39. As always, you will need a serial key to install and use the product. Oisín (doodlebug) or I can handle getting your keys. Please message one of us and we'll get you set up.

This build is approaching the final test version. Please test heavily and report items in this thread when issues are found. We expect the next build, or potentially the build after next, to be the final development build. At that point, we will begin asking testers to help us ensure it is ready for release and identify snags that would prevent that.

FAQ
Q: I can't install it without a serial key.
A: Message me or Oisín (doodlebug) for a serial key.

Q: I get SUPER low FPS.
A: Try disabling "transparent surface rendering" in the MVAMS.

FMS Changes
-Fixed issue with flight plan entries not appearing
-Fixed incorrect page max index on FPLN page under certain conditions
-Allowed airport coordinates to be copied to the scratchpad on the POS INIT page via the left side key
-Allowed pilot/ref wpt coordinates to be copied to the scratchpad on the POS INIT page via the left side key
-Fixed some terminal legs being unreasonably marked as conditional (preventing DIRECT TO, etc.)
-Fixed certain operations not returning to the correct page index after initial waypoint entry
-Fixed naming of "FD" legs
-Added ability to enter PBD, PBPB, and lat/lon waypoints directly into LEGS/FPLN page
-Fixed DEST on PROG not displaying the proper leg
-Added format/value restrictions to leg speed/altitude restriction entries
-Fixed inability to enter mach number to speed restriction
-Fixed WIND entry format issue
-Fixed inability to copy VNAV data
-Fixed missing VPA data for certain legs
-Fixed PROG page
-Fixed inability to advance MFD text PROG page
-Fixed missed approach waypoints not displaying as climb-type waypoints

PL21
-Fixed incorrect display of BETWEEN altitude restrictions on PL21

Other Changes
-Fixed missing XML/additional gauges

[michaelth]

Sorry, no Mantis:

- Master Caution blinks dark (not red)
- Text on fuel, engine and ice protection panel not sharp (ghosts)
- FMC shows "unable CRZ altitude"
- Baro push button inoperative
- Nose wheel and rudder locked to the left (not responding to pedals). This was working up to version 0.0.37.

I still have problems with holdings (see screenshot). It seems that the holding is entered, but then diverts to the next waypoint. Do I have to set FMC AUTO/INHIBIT to INHIBIT?

You did very beautiful liveries!

Michael

[rayharris51]

Hi

Thanks for the update.

First - just to say it looks fantastic now and flies really great.
DEP/ARR works well
Radar seems to work OK

Nose wheel still stuck full right. Not sure why that should be? Doesn't seem to affect runway taxi.

First trial flight - took off RWY07 ENBO towards ENDU.
Whilst playing with ND range knob after takeoff (passing through FL011) after takeoff - sudden CTD.
Not sure why there is this instability.

Tried again. This time on the threshold of the runway pressed radar ON = then freeze - CTD.

Not had time to test much else.

No idea why it is unstable. It doesn't seem to be any one thing, but somehow related to the ND buttons in some way. Wish it could be sorted out, getting fed up with it.

Kind regds

Ray

[Torkermax]

Is there any plan to implement a decent arc on the Proline display?

Thank you

[michaelth]

Timer in yoke is not coupled to battery. It is always on.

Michael

[Turbofandude]

Any CTDs, please include FULL steps to reproduce.

[N4GIX]

Timer in yoke is not coupled to battery. It is always on.

Noted: it will be fixed for master battery power. I am also going to increase the resolution of the gauges.

[N4GIX]

- Baro push button inoperative

Are you clicking on the Baro knob with the mouse wheel? That should 'push' the Baro button.

[rayharris51]

Hi

My CTDs were seemingly simple

First time it crashed I was whilst I was in the air; increasing the range on the ND when it froze and CTD.

Second time I was on the ground when I selected the radar button. This had worked OK previously.

That’s why I don’t think it’s necessarily the gauge or buttons themselves. In fact both range and radar buttons have worked OK previously.

Equally it is specific to the Milviz. I don’t think it’s my system, as I flew the same route immediately after with a Carenado modded B350i with GTN 750 and it all worked perfectly.

Any ideas? I’d love to get this bird working in a stable way somehow.

[xxd09]

Nose wheel frozen to the left
Safety Warning sound as engine revs reduced seems to engage/sound rather too soon ie with reasonable engine revs still in operation
xxd09

[dbw]

Upon first start up when entering a a flight into the FMS every location was responded to by the message - not in data base. Shut down P3d, restarted my computer, restarted p3d and everything then worked fine with the FMS.
This was a one time only occurrence.
Also, while it's already been reported about the cocked nose wheel.... in cruise flight with the rudder trim centered the rudder is also cocked to the left.

[N4GIX]

Also, while it's already been reported about the cocked nose wheel.... in cruise flight with the rudder trim centered the rudder is also cocked to the left.

The non-updated .dll is the cause of the rudder deflection to the left. With the correct .dll the problem is solved.

[jwf69822]

Hi Guys
Just installed this version and like 0.38 the nose wheel and rudder are turned to the left.
Odd and unable to recentre it using the num 5 key or anything else otherwise its looking amazing.
Noting the previous post about the .dll..
Where can I get that?
See attached pic.
Rgds
Jon

[Heronjr]

WAAS?

If yes, how to use it?

Great build! Regards,

[dihedral]

Noting the previous post about the .dll..
Where can I get that?

Hi Jon,
Should be included in next build which are released typically on Fridays.