King Air 350i Version 0.9 Build 90 (RC1)

[Turbofandude]

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

Testing and Feedback Team,

Release candidate (RC) (0.9.9X) build 90 (RC1) is available here: https://www.dropbox.com/s/9lkmwouaaq7aq ... 9.exe?dl=1

The final version has arrived. This version is expected to be a complete version of what 1.0.0 will be. The team has worked tirelessly to close out the remaining items. The outstanding list is very small and may or may not be addressed after release.

As of now, release is planned over the weekend. Over the next 24 hours, we are looking for showstopper bugs that will prevent proper usage of the product. 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.

Things to look out for include:

• CTDs
• Inability for autopilot to fly certain routes/legs
• Flight-ending systems bugs
• Flight-ending FMS bugs

Please report ALL bugs via Mantis and tag a developer on Discord if needed.

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 the last build
FMS Changes
-Fixed graphic display of "H" on legs page
-Fixed runway elevation display issue
-Various fixes

Systems
-Fixed a TAWS related CTD
-Various fixes

PL21
-Various fixes

Visual
-Various fixes

[michaelth]

Did a short start up and check through the systems before going to work - all good & beautiful.

The installer still does this:

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

[timizo]

I did my standard test flight from KRDM to KPDX and let the autopilot fly almost the whole way. I didn't have any SID's or STARS but I did shoot an ILS. It seemed to do fine. I noticed that the VNAV information gives you the descent path angle now. I'm pretty sure a few builds ago it actually gave the the TOD. I don't know if there is something I need to do to display this. Also as I was making my last turn to intercept the glideslope the PDF showed an approach mode annunciation in green with the LOC armed in white. The flight director did not follow the final approach course and LOC never went green. I manually switched out of FMS mode to LOC and then it started to fly the ILS. I don't know if it's supposed to automatically switch from FMS to LOC but it didn't. Those are the only things I noticed. I did not try to manually enter waypoints or altitude constraints.
Two minor things I noticed. The fuel system was not preforming fuel test or showing what was in the auxiliary tanks and I could not get the pilots to show up in the external views.

[rayharris51]

Hi
Thanks for the new version.
First let me say, it looks and sounds amazing.
I also managed to get into the air with TERR switched on and range changed to 50mi.

Two things though:
1. When I selected TERR I got a several minutes freeze, after which it reccovered.
2. About 20 minutes after takeoff at FL190 on the way to FL210 it CTDd without warning.

I then tried the same flight with the Carenado B350i with Bills mod and GTN750 - absolutely no problem.

v frustrating

Ray

[Taguilo]

I did my standard test flight from KRDM to KPDX and let the autopilot fly almost the whole way. I didn't have any SID's or STARS but I did shoot an ILS. It seemed to do fine. I noticed that the VNAV information gives you the descent path angle now. I'm pretty sure a few builds ago it actually gave the the TOD. I don't know if there is something I need to do to display this. Also as I was making my last turn to intercept the glideslope the PDF showed an approach mode annunciation in green with the LOC armed in white. The flight director did not follow the final approach course and LOC never went green. I manually switched out of FMS mode to LOC and then it started to fly the ILS. I don't know if it's supposed to automatically switch from FMS to LOC but it didn't. Those are the only things I noticed. I did not try to manually enter waypoints or altitude constraints.
Two minor things I noticed. The fuel system was not preforming fuel test or showing what was in the auxiliary tanks and I could not get the pilots to show up in the external views.

Hi,

FMS won't switch automatically to LOC unless a NAV-to-NAV condition is up and armed. We're going to explain NAV-to-NAV in detail after the release

Regarding pilot display:

-Pilots will auto display as soon as there is one source of power ON (Battery, Gen, ExtPwr, etc).
-Pilots cannot be removed when using menu while the above condition is present.

Fuel bug was fixed. Thanks!

Tomas

[rayharris51]

Hi
Thanks for the new version.
First let me say, it looks and sounds amazing.
I also managed to get into the air with TERR switched on and range changed to 50mi.

Two things though:
1. When I selected TERR I got a several minutes freeze, after which it reccovered.
2. About 20 minutes after takeoff at FL190 on the way to FL210 it CTDd without warning.

I then tried the same flight with the Carenado B350i with Bills mod and GTN750 - absolutely no problem.

v frustrating

Ray

[tamsini]

Hello Milviz team. Can someone try this flight plan? The FMS repeatedly overwrites the previous waypoint. Not sure what is going on here:

KEY - KJAX

DCT CORGI DCT KARTR DCT CYY DCT RSW DCT ILBOC QUBEN1

At the end of entering waypoints, only ILBOC remains on the legs page.

Regards,
Mario

[michaelth]

Mario,

a valid flight plan would be "KEYW DCT CORGI DCT KARTR DCT CYY DCT RSW DCT ILBOC KJAX". The last entry "QUBEN1" is no waypoint but a STAR. It must be added through the Dep/Arr page together with a runway.

Michael

[tamsini]

I should not have referenced the STAR. The problem persists BEFORE entering STAR.

[michaelth]

EGHI DCT CPT DCT TNT DCT POL DCT CO DCT HAVEN EGPH

good flight with up to 360kts GS at FL260 and strong tail wind, ILS Rwy24 landing, everything including WXR working, no probs found.

Michael

[michaelth]

Hi Mario,

after positioning the King Air at KEYW, I did Pos Init, then entered the FP, no problem.


<?xml version="1.0" encoding="UTF-8"?>
<Version1>
<Departure>KEYW</Departure>
<Arrival>KJAX</Arrival>
<Legs>
<Leg Type="Waypoint" Ident="CORGI" Name="CORGI" Country="K7" Latitude="24.8618" Longitude="-81.7138" HasNavaid="False" NvdIdent="" NvdName="" NvdCountry="" NvdUsage=" " NvdChannel="" NvdNType="0" NvdLatitude="0" NvdLongitude="0" NvdFrequency="-1" NvdElevation="0" />
<Leg Type="Waypoint" Ident="KARTR" Name="KARTR" Country="K7" Latitude="25.496" Longitude="-81.5128" HasNavaid="False" NvdIdent="" NvdName="" NvdCountry="" NvdUsage=" " NvdChannel="" NvdNType="0" NvdLatitude="0" NvdLongitude="0" NvdFrequency="-1" NvdElevation="0" />
<Leg Type="Navaid" Ident="CYY" Name="CYPRESS NAPLES" Country="K7" Usage="H" Channel="" NType="4" Latitude="26.1534" Longitude="-81.7781" Frequency="17326080" Elevation="10" />
<Leg Type="Navaid" Ident="RSW" Name="LEE COUNTY FORT MYERS" Country="K7" Usage="T" Channel="" NType="2" Latitude="26.5299" Longitude="-81.7758" Frequency="17924096" Elevation="25" />
<Leg Type="Waypoint" Ident="ILBOC" Name="ILBOC" Country="K7" Latitude="29.2743" Longitude="-81.6074" HasNavaid="False" NvdIdent="" NvdName="" NvdCountry="" NvdUsage=" " NvdChannel="" NvdNType="0" NvdLatitude="0" NvdLongitude="0" NvdFrequency="-1" NvdElevation="0" />
</Legs>
</Version1>


Michael

[Heronjr]

First Build 90 flight first CTD: KCIC-KEUG FL220

1. Yokes' chronos now visible and with lights when battery on. Thanks! Panel still with dark textures. Awful!
2. New sounds on startup. Good!
3. WX radar working without issues.
4. When crossing 16000 up to FL220, received a red warning about PRESS, even with the correct press altitude set and ENV switches OPEN. This is happening since some past builds.
5. CTD when choosing ILS 13L EUG intersection. At the moment I clicked on the EUG LSK button came the CTD. I've been flying this route on each and every build release without problems. Frustrating!

It may be a coincidence, but it is being reported as asked. It's Friday, I'll try some whisky now.

[tamsini]

Hi Mario,

after positioning the King Air at KEYW, I did Pos Init, then entered the FP, no problem.


<?xml version="1.0" encoding="UTF-8"?>
<Version1>
<Departure>KEYW</Departure>
<Arrival>KJAX</Arrival>
<Legs>
<Leg Type="Waypoint" Ident="CORGI" Name="CORGI" Country="K7" Latitude="24.8618" Longitude="-81.7138" HasNavaid="False" NvdIdent="" NvdName="" NvdCountry="" NvdUsage=" " NvdChannel="" NvdNType="0" NvdLatitude="0" NvdLongitude="0" NvdFrequency="-1" NvdElevation="0" />
<Leg Type="Waypoint" Ident="KARTR" Name="KARTR" Country="K7" Latitude="25.496" Longitude="-81.5128" HasNavaid="False" NvdIdent="" NvdName="" NvdCountry="" NvdUsage=" " NvdChannel="" NvdNType="0" NvdLatitude="0" NvdLongitude="0" NvdFrequency="-1" NvdElevation="0" />
<Leg Type="Navaid" Ident="CYY" Name="CYPRESS NAPLES" Country="K7" Usage="H" Channel="" NType="4" Latitude="26.1534" Longitude="-81.7781" Frequency="17326080" Elevation="10" />
<Leg Type="Navaid" Ident="RSW" Name="LEE COUNTY FORT MYERS" Country="K7" Usage="T" Channel="" NType="2" Latitude="26.5299" Longitude="-81.7758" Frequency="17924096" Elevation="25" />
<Leg Type="Waypoint" Ident="ILBOC" Name="ILBOC" Country="K7" Latitude="29.2743" Longitude="-81.6074" HasNavaid="False" NvdIdent="" NvdName="" NvdCountry="" NvdUsage=" " NvdChannel="" NvdNType="0" NvdLatitude="0" NvdLongitude="0" NvdFrequency="-1" NvdElevation="0" />
</Legs>
</Version1>


Michael

Thanks Michael. I tried this twice and both times had the overwrite of the previous waypoint problem. I'm at a loss - guess I'll give it another try tomorrow.

Mario

[johnh]

When I turn Ext Pwr Switch on and change the overhead selector to Ext Pwr the Volts = 0 and Amp = -60. Am I doing something wrong? I would have thought that I would be able to use Ext Pwr whilst prepping the Aircraft and FMC

[dbw]

Fuel panel...
Selecting aux tanks fuel qty does not work.
Selecting aux fuel transfer over ride appears not to work.

Note: FD now stable in turns.

Dave