King Air 350i Version 0.9 Build 42

[fs5868]

Hi guys,

350i Inop

1. I have the AVAMS as default with Aircraft ready to fly at the runway.
2. Defaults options for P3D before loading Aircraft.
3. Aircraft loads. No Sound. No lights on panel. Props Spinning. But brief msg stating aircraft has not been started.
4. Only axis operable is aileron on Yoke or Stick.
No Pitch. No THR 1 or THR 2.
5. Checked all Axis - they are assigned and calibrated.
6. Exited P3d.
7. Loaded P3d.
8. Loaded Milviz p-38. All functions normal.
9. Changed options in AVAMS to Cold and Dark
10. Ran P3d
11. Loaded 350i - Still Inop

I believe I troubleshooted it enough to determine that there appear to be collisions between the honeycomb panel switch settings and the 350i configuration. The interesting issue is that the Warthog throttles dont work while the yoke is attached with the 350i, it works with the P-38.

Further research --- I have a DXDiag but was not able to attach .

[Taguilo]

Awesome, thank you for that information. I really appreciate it! I’ll try that out. Do you know about issues with the flight plan altitudes. I put in a cruise altitude of 14000 ft and every waypoint had 2300 ft listed. Does VNAV follow entered altitude constraints?

That population of waypoints with vnav data is a bug and will be fixed for the next release.

Tomas

[Taguilo]

I keep getting the error "FMC TEXT INCOMPATIBLE". I used to be able to get rid of it with each build using the "install" of each font or using the font that was attached to an older post. But with the last two releases I can't get it to fix the issue. Any ideas?

Hi,

Please do not install more fonts. Message has nothing to do with that; it's a real FMS advice that displays when there is no Flight Plan loaded and the FMS-TXT option is selected on MFD's upper format menu.

Tomas

[rayharris51]

Hi

I just noticed an error message on installation.

It is dxweb9.0 related and always comes up twice during TruGlass and lights installation, saying that 'cannot create process in ...etc etc, giving advpack.dll as the reason.

It has never actually stopped installation, and as far as I can tell installation has always been apprently unaffected.

Are you aware of having seen this type of error before?

KR

Ray

[wale03]

Still getting the line drawing issues when I do and Direct-To, the LNAV seems to almost turn backwards before intercepting the correct course.

[rayharris51]

Hi Again

Big improvement thanks.

Most things seem fixed. Trying CYCDCYLW again - no FMS problems this time.

My question may be as much my ignorance of KingAir procedure as any bug.

I forgot to switch on the Battery Bus until after take off. GENs were on and everything seemed else to work fine except for having no speed tape on the ND. (red). The thermometer to lower left of pilot seat also doesn't work.

So I am currently flying with no speed readout. btw the normal anti ice switches are all on - including pitot etc which I would have expected to may be responsible.

Also the AP keeps turning itself off, something I had not seen in a while. We have an approx 50 knot cross wind, not sure if that's realistic behaviour for the KA.

I will try another flight as soon as I can and report back.

Ray

[FSPrivatePilot]

Do you folks have the aircraft manual available for us by chance? That may help when we are testing the aircraft...

Just a thought. Even if the manual is a draft.

Thanks.

[michaelth]

EFOB: still scratching my head.
Pics 2 and 3 show the waypoints from EGHI to EGPH, Pic 1 the Prog page. Amount of fuel was 2800 lbs before starting engines. Fuel at RW2 2772 lbs, but at TNT (third waypoint) 2940 lbs. Also: what does the negative ETE mean?

Michael

[Taguilo]

I forgot to switch on the Battery Bus until after take off. GENs were on and everything seemed else to work fine except for having no speed tape on the ND. (red). The thermometer to lower left of pilot seat also doesn't work.

So I am currently flying with no speed readout. btw the normal anti ice switches are all on - including pitot etc which I would have expected to may be responsible.

Also the AP keeps turning itself off, something I had not seen in a while. We have an approx 50 knot cross wind, not sure if that's realistic behaviour for the KA.

Hi,
Most probably you departed with pitot covers over the pitot tubes. That should explain the anomalies in your speed data and also the autopilot disconnection because of invalid data compare between left & right ADC and AHC.

Tomas

[rayharris51]

OK final note

Pressed rad/terr button whilst prepraing for descent and CTD. So not sorted and really disappointing. This is still a potentially serious issue for release if that is not resolved.

Other issues I reported previously though are now OK. No issues with AP, FMS or speed tape anymore.

ANother question - I am not able to turn on the Chronometer or thermometer at the moment. They came on automatically with the other electrics previously. Is this just user ignorance, and is there a separate circuit for these?

Thanks

Ray

[rayharris51]

Hi Tomas

I think you are right.

Previouly we had to manually switch on the external GPU, chocks, pitot covers etc. Now that are on by default, I did check these on the second flight and ensured they were all off - hence no problems. Only the CTD in my previous email now.....

[fs5868]

Hi guys,

RE: Honeycomb Pilot Yoke
350i Inop

1. I have the AVAMS as default with Aircraft ready to fly at the runway.
2. Defaults options for P3D before loading Aircraft.
3. Aircraft loads. No Sound. No lights on panel. Props Spinning. But brief msg stating aircraft has not been started.
4. Only axis operable is aileron on Yoke or Stick.
No Pitch. No THR 1 or THR 2.
5. Checked all Axis - they are assigned and calibrated.
6. Exited P3d.
7. Loaded P3d.
8. Loaded Milviz p-38. All functions normal.
9. Changed options in AVAMS to Cold and Dark
10. Ran P3d
11. Loaded 350i - Still Inop

I believe I troubleshooted it enough to determine that there appear to be collisions between the honeycomb's panel switch settings and the 350i configuration. The interesting issue is that the Warthog throttles dont work while the yoke is attached with the 350i, it works with the P-38.

I have a DXDIAG I was not able to attach. Contact me if needed.

[dbw]

Greetings. Just installed this latest version.
Disclaimer: I have rw time on several versions of the 90 & 200.
Flew the steam gauges and the Garmin 1000 but never the PL21.
Observations:
1. On most king airs the normal fuel transfer is automatic. On this fuel no transfer lights are on and fuel does not appear to be transferring unless forced to by fuel panel switch selection. When selecting override on the lights go out for a short time. Turn it off and they come back on.
2. Flight Director.... Seems to be for the most part for better words...out to lunch. Also, Flight director on/off buttons on both sides are not functioning.
3. Baro Setting button... press for STD (climbing thru 180) and you get nearest local altimeter setting. You need to press B to get it to go to STD.
4. External view of nose wheel during turns...Does not seem to have enough deflection for turn that is happening.
5. PL21ILS approach. Indicated both localizer and glide slope accurately all the way to the ground but I could not get the PL21 autopilot to lock on and fly it down.....This may be due to my unfamiliarity with the PL21 and missing something.
This was on a flight from KRNO (Reno) to KSFO (San Francisco) at FL220. Flew an appropriate SID and STAR. On the whole the aircraft flew well and was a joy.
Hope this is of assistance.
Dave

[Taguilo]

Greetings. Just installed this latest version.
Disclaimer: I have rw time on several versions of the 90 & 200.
Flew the steam gauges and the Garmin 1000 but never the PL21.
Observations:
1. On most king airs the normal fuel transfer is automatic. On this fuel no transfer lights are on and fuel does not appear to be transferring unless forced to by fuel panel switch selection. When selecting override on the lights go out for a short time. Turn it off and they come back on.
2. Flight Director.... Seems to be for the most part for better words...out to lunch. Also, Flight director on/off buttons on both sides are not functioning.
3. Baro Setting button... press for STD (climbing thru 180) and you get nearest local altimeter setting. You need to press B to get it to go to STD.
4. External view of nose wheel during turns...Does not seem to have enough deflection for turn that is happening.
5. PL21ILS approach. Indicated both localizer and glide slope accurately all the way to the ground but I could not get the PL21 autopilot to lock on and fly it down.....This may be due to my unfamiliarity with the PL21 and missing something.
This was on a flight from KRNO (Reno) to KSFO (San Francisco) at FL220. Flew an appropriate SID and STAR. On the whole the aircraft flew well and was a joy.
Hope this is of assistance.
Dave

Hi Dave,

1. On most king airs the normal fuel transfer is automatic. On this fuel no transfer lights are on and fuel does not appear to be transferring unless forced to by fuel panel switch selection. When selecting override on the lights go out for a short time. Turn it off and they come back on.

Fuel no Xfer lights appear when you have fuel in the aux tanks and ignition system is active. Fuel transfer is inhibited in these cases. This is a tricky one even to real KA350i pilots...

2. Flight Director.... Seems to be for the most part for better words...out to lunch. Also, Flight director on/off buttons on both sides are not functioning.

We don't have any other reports of FD working bad. Does it happen to you with or without Autopilot engaged? You can use SYNC method of FD to synchronize FD bars with aircraft's current attitude; just map TOGGLE_WING_FOLD event to any joystick button or keyboard key.

3. Baro Setting button... press for STD (climbing thru 180) and you get nearest local altimeter setting. You need to press B to get it to go to STD.

Actually is the other way around, pressing B will bring you local altimeter and pressing the Baro button, STD, changing to FL and the current altitude at the moment it is pressed.

4. External view of nose wheel during turns...Does not seem to have enough deflection for turn that is happening.

NW deflection is affected by aircraft's current speed. At high speeds it remains quite straight, which is real. Most of sim addons seem to not use that relationship therefore showing greater than real NW deflections.

5. PL21ILS approach. Indicated both localizer and glide slope accurately all the way to the ground but I could not get the PL21 autopilot to lock on and fly it down.....This may be due to my unfamiliarity with the PL21 and missing something.

For ILS approaches it is mandatory to capture and fly the glidepath at proper airspeeds. Recommended are from 140 to 120/115 KIAS.


Thanks Dave, we really appreciate you comments.

Tomas

[Heronjr]

First flight in Build 42:

1. Dark textures are still there. The PAX cabin is in normal textures and cockpit with very dark textures. Without the flood lights, the pilots seats cannot be seen, even in daylight.

2. Why did you remove the panel under the 2D FMS?

3. With the MVAMS sound switches in the original 50% positions, the sounds are now too low for gear and flaps up/dn. I will try them at 100%.

4. Even setting the cabin altitude to FL220, a red CABIN DIFF HI lights on crossing FL210.

5. The control wheels' clock/timer are off all the times, battery on or off.