King Air 350i Version 0.9 Build 40

[Turbofandude]

Please try a complete reinstall (and ensure that all files are deleted manually from SimObjects folder) and see if it still occurs. Please also include a screenshot of the issue if it does.

[Barnes]

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.

Yes- the main panel also has a brownish tint to it and the engines and prop spinners (when viewed from the VC) have a gold tint as well.

[Barnes]

Please try a complete reinstall (and ensure that all files are deleted manually from SimObjects folder) and see if it still occurs. Please also include a screenshot of the issue if it does.

Not sure if that was directed to me but I tried your suggestion anyway. I am still seeing the same
golden tint in the VC after restoring the default P3D shaders and re-installing the KA. See my previous post for pictures.
I did notice that some items in the VC are not affected by the tint, such as the overhead panel, the throttle quadrant/center console, rudder pedals and fuel panel. Not sure if this helps localize the problem.

Dave

[Heronjr]

Uninstalled the aircraft and MVAMS, removed residual folders and files, rebooted and reinstalled the whole thing. The result was the same: Cold & VERY DARK cockpit in daylight, except PAX cabin. I tried to turn off HDR without success. The only way to see something is turning off shadows cast/receive internal vehicle option in P3D, but this is something I have NEVER touched. I like my shadows in other aircraft and they are P3D native and worked perfectly with this KA350i until the last version.

[Barnes]

Uninstalled the aircraft and MVAMS, removed residual folders and files, rebooted and reinstalled the whole thing. The result was the same: Cold & VERY DARK cockpit in daylight, except PAX cabin. I tried to turn off HDR without success. The only way to see something is turning off shadows cast/receive internal vehicle option in P3D, but this is something I have NEVER touched. I like my shadows in other aircraft and they are P3D native and worked perfectly with this KA350i until the last version.

Coincidently, all the textures that are black in your sim are the ones that are tinted gold in my sim.
Are you using P3D 4.5 ?
If you are using 4.3 or earlier, PBR was not supported. It seems to me that PBR texturing may have been added to the cockpit in the latest build of the KA.

Dave

[Heronjr]

Coincidently, all the textures that are black in your sim are the ones that are tinted gold in my sim.
Are you using P3D 4.5 ?
If you are using 4.3 or earlier, PBR was not supported. It seems to me that PBR texturing may have been added to the cockpit in the latest build of the KA.

Dave

P3D 4.5 very newest! I don’t have any idea what is PBR but I know the textures were perfect until the black switches appeared 2 versions ago.

If I turn off the P3D shadows, the textures are the same as yours.

[rayharris51]

Hi All,

Thanks for this new version.

Only had very brief chance to try it on a couple of flights, sadly neither of them successful.

I can confirm I am using P3D 4.5 and cold dark textures are very dark as others have noted.

I am using Rex Environment shaders.

Second point is I got a CTD when selecting a Runway in a flight Plan CYCDCYBD in DEP/ARR whilst selecting RWY05 for CYBD.
Got the point about correct speed on the ILS approach - that works nicely now.

Can confirm TERR/RDR also works great.

Finally though, today I set a flight plan for CYCDCYLW. No idea whether this was pilot error but I selected a simple RWY34 departure and CYLW RWY16 arrival via the YDC Approach, about 250nm in Canada.

I had inserted a couple of intermediate waypoints out of CYCD (can't remember which ones). The flight plan appeared OK on the ground but once I took off and looked again, my intermediate waypoints to YDC had disappeared and the waypoints on the FMC now showed a new waypoint; DARUD over 600nm away and then VECTORS over 6100 nm! to EPRAV which I think must be part of the CYLW appoach.

I was now flying 250 degs which is almost the opposite to what I needed to be - about (60 degs) . So I selected HDG to at least turn 340 again and got a CTD.

User error not withstanding this is not a good experience yet, albeit a beautiful bird. I would like ideally to be able to ditch the Carenado B350i with Bills Mod and the GTN750 if I can - which is flawless mostly if not so accurate.

PS Really like to be able to save flight plans (or import from FSTramp?)

Kind regards,

Ray

[Heronjr]

I think there is a problem with some sounds in this version - I did not touch yet the sound bars in MVAMS:

1. Altitude alarm is too high - I remember it was this high in the first versions, then it came fine on this year.
2. Autopilot OFF alarm is no more heard, although Its light blinks red.
3. My sound is always kept in the same level. I noticed that I don't hear the right engine starting whining and initial roar high as before. The left engine sounds normal.
4. Sometimes, during the takeoff, the right engine suddenly sounds higher, leveling with the left engine sound.
5. Immediately after the altitude alarm sound is played, the L/R engines sound higher.

[rayharris51]

Hi Osh etc

Update; there seems to be a nav database error from what I can tell.
Just manually put in a flight CYCDCYLW - to keep it consistent with my last flight.
So what I found is
1. Using DEP/ARR auto entries for RWY34 CYCD to RWY16 CYLW are unusable as waypoints are thousands of nautical miles out.
2. Manual entry of waypoints as follows;
CYCD RWY34 - ARMAC YDC VIVEK DATBO DARUD XERUX EPSER EPRAV CYLW ILS16
Note some waypoints again showed distances of 1000s of nm away so couyldn;t be used. ARMAC looked OK in the FMC.

In the FMC after takeoff, when I checked ARMAC waypoint again it was 4.4nm away which was not correct either - FSTramp has the same waypoint as being 1.4nm away. FSTramp is always correct in my experience.
On the MFD - the same ARMAC waypoint was 3816nm away!

I did set up POS INIT correctly I believe at CYCD.

So it looks likely to be some internal database error/bug. Strange that the MFD and FMC say two different things.

Alway open to being corrected in case my ignorance of the KA is at the bottom of this. But I have never experienced anything like that that before in any other study level plane (Maj Dash 8 400/FSL Airbus...).

Is this Navigraph data?

KR

Ray

[rayharris51]

Hi

One other minor thing - when near the ground strnage textures appear on the prop cone - no doubt representing ground reflections. They look wierd though and are not stable.

May be somethning to do with the same dark cabin textures reported elsewhere here, that I also get.

Regards


Ray

[giorgio759]

Hey! I just tried to take her up and had a CTD while entering the departure airport on the Pos Init page of the FMC. A few weeks ago, same build, I had another CTD while entering legs in the FMC and in another flight, during climb-out and after engaging the autopilot in LNAV, the aircraft would not follow the flightplan and even Hdg Select didn't function. It just flew in a lazy circle. I haven't been able to get a full flight in since build 38. Still love the bird and I'm sure all will be sorted. Thanks and cya!

PS. I need to clarify my report by saying that I have only tried to fly a few flights in since build 38. Each attempt resulted in a CTD.