KA350i Version 1.1 (SP1 - 1.1.29) [UPDATED MAY 24]

[FinnJacobsen]

Yup, that makes sense. I apologize - you need to run it with the /beta switch (you can do this by creating a shortcut and adding it as an argument or by starting it from the command line as "RealLight_Installer.exe /beta".

Nope...
It seems to install the same beta version that doesn´t work, maybe a P3D V4.5 HF3 issue.
With this version there are no Reallight and the annunciator's and lighted buttons are very dim.

[Turbofandude]

What operating system are you running? Can you PM me so we can setup an AnyDesk session?

[FinnJacobsen]

I have PM'ed You twice, but the messages won´t leave the Outbox.

My specs:
7 3770 3.4 Ghz, 16GB RAM, GTX960 4GB, Win 7 Home 64bit, 1 TB HDD for windows, 2TB HDD for P3D V4.5 HF3

[Turbofandude]

My apologies, my inbox was full. I've cleared that and received them now.

[bmw969]

I managed to take off in P3D v5!
All electronics do not work, but I am satisfied.
Visual approach. The speed is intuitive.
Cheers!

https://youtu.be/s-60BOLC8q4

[FinnJacobsen]

My apologies, my inbox was full. I've cleared that and received them now.

Seems it´s full again.

[tredsell]

New reallight is definitely an improvement for me. I daren’t go all the way and say it’s enough ‘VRAMwise’ as I do think there is something swallowing up an unnecessary amount of memory. But this has definitely helped so thank you.

Only bug to report today is that I’m getting a cabin altitude warning at FL330. Pressurisation is fine and still in the green although the cabin alt exceeds 10,000ft - which I think I have read is normal in the king air. Is it normal to still get the warning? This never happened in previous flights.

[franz68]

hi everybody,

just wanted to bring up a small visual glitch I noticed after 1.1.7 and on …
it looks like when in spot view the side panel of the cockpit window opposite
to the viewer becomes transparent or isn't shown … this makes look the plane
as it would have no fuselage … see screenshot, also another thing I noticed
always in spot view is you are now able to see through the bottom of the
cockpit floor (this one is not pictured, but I can if requested).

hope this visual gets fixed maybe with the next beta ...

otherwise this is a great plane which I really enjoy, thanks to the team for
making it become "real"!!

ciao Francesco

[tamsini]

Hello all - hoping someone can shed some light on this problem that's been driving me crazy! Upon loading the KA 350, whether I assign the throttle axis via FSUIPC or none at all, the throttles load at 64 thrust (so just above idle - see screen capture). So I cannot configure the axis via MVAMS because the lowest it recognizes is 64,

How can I get the levers to load at a lower thrust level? Even if I use my mouse to move the levers down, the moment I jiggle my thrust lever on the Saitek, it'll jump to 64.

Any ideas?

[Taguilo]

Only bug to report today is that I’m getting a cabin altitude warning at FL330. Pressurisation is fine and still in the green although the cabin alt exceeds 10,000ft - which I think I have read is normal in the king air. Is it normal to still get the warning? This never happened in previous flights.

Hi,

It is not a bug. Cabin altitude for 33,000 ft by selector is ~ 9800 ft, so considering a normal leak it is expectable that might reach 10,000 ft and trigger the white annunciator avisory.
Notice that at 35,000 ft cabin altitude advisory will always trigger. In some high altitude airports cabin altitude CB is tripped to disable the alarm.

I personally checked that today and it's working as expected.

Tomas

[tredsell]

Thanks Tomas.

That’s interesting! Must be a little risky tripping it or silencing the alarm at FL350 in case of a subsequent loss of pressure going unnoticed.

Cheers for the info

Tom

[Taguilo]

Tom,

Actually not muck risky. There's a red warning annunciator for Cabin exceeding ~ 11,500 ft (CABIN ALT HI) and that is the one you must care about.
Still, pax oxygen maks won't auto deploy until ~ 12,500 ft.

Tomas

[jk.wall]

Hi All

Just had a successful flight in version 1.1.8, foolishly updated to HF3 for p3d and low and behold getting a lot of the errors folks are complaining about, WX.dll not compatible, dim warning lights. Screen shot is with the test button pressed, no warning lights.

hope I can role back to previous P3D version.

[mml]

Hello all - hoping someone can shed some light on this problem that's been driving me crazy! Upon loading the KA 350, whether I assign the throttle axis via FSUIPC or none at all, the throttles load at 64 thrust (so just above idle - see screen capture). So I cannot configure the axis via MVAMS because the lowest it recognizes is 64,

How can I get the levers to load at a lower thrust level? Even if I use my mouse to move the levers down, the moment I jiggle my thrust lever on the Saitek, it'll jump to 64.

Any ideas?

Exactly the same same problem here. I can try with or without FSUIPC the result is always the same. Also the MILVIZ calibration tool has no effect at all. No other aircraft of my hangar shows this very peculiar behaviour.

[N4GIX]

Hello all - hoping someone can shed some light on this problem that's been driving me crazy! Upon loading the KA 350, whether I assign the throttle axis via FSUIPC or none at all, the throttles load at 64 thrust (so just above idle - see screen capture). So I cannot configure the axis via MVAMS because the lowest it recognizes is 64,

That is the idle position! Anything below idle is reverse pitch.

Apply prop control forward, the drag the throttles using the "Both" mouse spot downwards and watch the KA backup!