King Air 350i Version 0.9 Build 40

[Turbofandude]

Please read carefully as this is not a normal weekly build.

Testing and Feedback Team,

Official beta (0.9.X) build 40 is available here: King Air 350i Version 0.9 Build 40

The official non-development version has arrived. This version is expected to be a feature-complete version of what 1.0.0 will be. The team has worked very hard over the last few weeks to iterate over and close a number of bugs in many areas and add remaining missing features. This version of the product may still have some minor bugs - your continued feedback will help us refine it further and prepare it for release.

As of now, release is planned on December 16th, 2019. Over the next 10 days, we will be doing more regular and incremental builds to help refine and iterate over the last rough spots. We anticipate a service pack at some point post-release to address issues discovered by the wider audience and we may expand some functionality with that update.

Now is the time to help us catch anything that seriously impacts the experience. Things to look out for include:

• CTDs
• VNAV calculation issues
• Magenta line drawing issues
• LNAV performance issues
• Flight-ending systems bugs
• Flight-ending FMS bugs

Please report ALL bugs via here.

If there are items found that are outside the scope of the above list, we do still care. Please do report them but understand that we may not be able to them immediately. Thank you all for your feedback so far and we are looking forward to bringing it home.

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.

Changes from dev build 39
FMS Changes
-Prioritized yellow messages over white messages
-Added better detection of MAP and FAF (internal)
-Added new VPATH related messages
-Fixed terminal HOLD objects not being identified properly
-Fixed DIR TO VERTICAL behavior
-Added ability to enter "1" into the cruise altitude field to enter the preselected altitude
-Fixed a CTD viewing DEP/ARR pages
-Fixed inability to deselect an approach to select a runway
-Fixed departure/arrival airports not copying when pressed with an empty scratchpad
-Fixed a page index issue when adjusting existing departure runway selections
-Fixed "VIA/TO" color on FPLN page
-Fixed alignment of top/title line
-Fixed a CTD when deleting certain waypoints
-Fixed improper page indexing when manipulating flight plans
-Added default VECTORS transition
-Added indication of turn direction and heading in bearing line on LEGS page
-Fixed procedure turn display and flight
-Fixed hold flight, and fixed hold entry type decision and hold entries (direct, teardrop, parallel)
-Added support for hiding MAP legs
-Added support for display of arrows for intercept legs
-Added display of turns after overfly waypoints
-Fixed altitude conditional wp early sequencing
-Fixed procedure turn early sequencing
-Refined turn anticipation
-Fixed hold early sequencing

Systems
-Revised engine parameters and control
-VNAV completion

PL21
-Various functional and visual updates (there are quite a few, just not itemized)

Visual
-Various model/texture improvements

[michaelth]

On my system, P3D has two different dll.xml:

1. resides in \AppData\Roaming\Lockheed Martin\Prepar3D v4

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>XMLTools64</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files\Lockheed Martin\Prepar3D v4\XMLTools64.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
<Launch.Addon>
<Name>FSUIPC 5</Name>
<Disabled>False</Disabled>
<Path>C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>as_connect</Name>
<Disabled>False</Disabled>
<Path>C:\Program Files\Lockheed Martin\Prepar3D v4\as_srv\as_connect_64.dll</Path>
</Launch.Addon>
</SimBase.Document>

2. resides in \ProgramData\Lockheed Martin\Prepar3D v4

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="AceXML" version="3,0" id="dll">
<Descr>AceXML Document</Descr>
<Filename>dll.xml</Filename>
<Launch.Addon>
<Name>PMDG Interface</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDG_Interface.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
<Launch.Addon>
<Name>RAASPRO</Name>
<Disabled>False</Disabled>
<Path>.\RAASPRO\RAASPRO.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
<Launch.Addon>
<Name>PMDG_HUD_interface</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
<Launch.Addon>
<Name>WXAdvantage</Name>
<Disabled>False</Disabled>
<Path>Modules\MV_WXM.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
</SimBase.Document>

Although the first one already contains the XMLTools64.dll, the installers always imports the same lines into the second one. Please let the installer check both instances of dll.xml.

Michael

[michaelth]

from a short flight:

- nose wheel turns on ground but lags behind aircraft steering
- gear retraction after take off results in flap warning sound when flaps are set for take off
- left/right generator off in flight: voltmeter does not drop
- autopilot APPR mode does not follow glideslope (Yakutat ILS Rwy11); descent much too steep)
- still not able to program Holdings

VC looks fantastic!

Michael

[Taguilo]

from a short flight:

- nose wheel turns on ground but lags behind aircraft steering
- gear retraction after take off results in flap warning sound when flaps are set for take off
- left/right generator off in flight: voltmeter does not drop
- autopilot APPR mode does not follow glideslope (Yakutat ILS Rwy11); descent much too steep)
- still not able to program Holdings

VC looks fantastic!

Michael

Hi,

-Nose wheel turns correctly according to aircraft's current speed.

-Flaps warning sound will happen if using DOWN (full) flaps position for take off, and the gear is raised before retracting flaps at least one position (APP or UP). That's correct.

-Voltmeter for Left/Right generator BUS will not drop when turning either gen off at a time, as the other BUS remains powered through the GEN TIE system.

- Glideslope path must be followed using proper app speeds. Once GS is captured, glidepath is controlled by throttle inputs. GS optimal speeds are in the range of 120-140 knots.

Thanks!

[michaelth]

Hi Taguilo,

I checked it on a second flight (LOWI to LFMN): indeed it captures and follows glideslope when speed is correct.

Also: holdings work when entered correctly (my bad).

Having lots of fun flying,
Michael

[tamsini]

Fantastic update! Am able to cycle through the various PFD settings (i.e. WX/Terr) with ease. This was always causing CTDs beforehand.

Just drop-dead gorgeous plane!

Mario

[Heronjr]

This file name is: MV_KA350i_v0.9.41_191206.zip

The last one from 11/20/2019 was MV_KA350i_v0.0.40_191120.zip. Are you sure the build number is still 40?

Flying it:
1. Again, I don't think the time is for changing textures. Now, even in daylight, the cold/dark panel became cold/REALLY DARK until the flood lights are on. Sorry, but the 38 and 39 versions textures were perfect. Lets fix things that need to be fixed. Is it working? Please, don't touch!

2. It seems the nav systems are all OK, and the radar is working without CTDs. I will try some more different kinds of approaches to test VNAV.

3. Is there a way to save flightplans in the FMS?

4. The Proline 21 Manual would be a great resource to learn all its simulated features secrets.

Regards

[michaelth]

Gear warning and altitude alert a are very loud. It seems that they are not coupled to the MVAMS cockpit sound slider. Altitude callouts seem also to be independent of the cockpit sound slider.

I am just flying from LYBE to LOWW. The analogue fuel quantity is 2200 lbs, the FMS Perf Init page shows about the same, but the FMS Prog page calculates 2800 lbs for a waypoint which is 60 miles ahead. (MVAMS is set to 2800 lbs fuel.)

Michael

[Barnes]

Hello,

I have not tried the last couple of betas so I am not sure if this is an old issue or not (or if it is even an issue).
Everything in the VC seems to have a golden/brown tint and I don't think that it is by design because the passenger cabin does not have the same tint (see comparison shot below). The older versions that I had tried had matching coloring in the cockpit and the cabin, without the tint.
I am guessing that this may have something to do with the addition of PBR texturing in the VC. I also thought that it may be caused by custom shaders since I use Tomato Shade, so I restored the original shaders and the results were the same.

Thanks,
Dave

[N4GIX]

No images appear.

[Barnes]

No images appear.

Hi Bill - Hopefully images above are visible now?

Thanks,
Dave

[Heronjr]

After entering the approach on DEP/ARR page, the altitudes in the LEGS page go havoc until the FAF. This is a new behavior in FMS. Example, after entering KLWS RNAV Y RWY 26 INT PETEZ, coming from KBZN:

Altitude entered in PERF page: 16000

Altitude when DEP/ARR was entered: 16000
...
TAGOE 250/5100 ==> ???
MSO 250/5100
WAANE 250/5100
LOLLO 250/5100
JIROS 250/5100
CEPER 250/5600

From here all altitudes as the chart
PETEZ 250/5600 ==> INTERSECTION
HENVO 250/5600A ==> FAF

Regards

[Heronjr]

VNAV is working OK. Watch your speed to use it - don't let the thing dive!

Where is the A/P OFF alarm?

Great job guys. Almost there!

Regards

[N4GIX]

Hello,

I have not tried the last couple of betas so I am not sure if this is an old issue or not (or if it is even an issue).
Everything in the VC seems to have a golden/brown tint and I don't think that it is by design because the passenger cabin does not have the same tint (see comparison shot below). The older versions that I had tried had matching coloring in the cockpit and the cabin, without the tint.
I am guessing that this may have something to do with the addition of PBR texturing in the VC. I also thought that it may be caused by custom shaders since I use Tomato Shade, so I restored the original shaders and the results were the same.

I see the same thing here in my dev sim computer. The cabin fixtures are a light tan while the cockpit seats are more a "honey gold" color.

[Heronjr]

Until the last build (Nov 20) the panel in my monitor was crispy clear, with every niche and all details visible. Now most of it is dark. Nothing near the images you showed here.

The pax cabin is OK.

I've never had this problem before with any aircraft.

Regards,