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

[zkalos]

If i turn on the bluish floodlight, the FO lower environment panel's text blurry (with the 1.1.29 low res installer), like "bmw969" wrote Mon May 25, 2020 8:53 am, in "posts 69".

[pato_galex]

HI FRIENDS HOW DO I INSTALL THIS PATCH SOMEONE CAN HELP ME THANKS YOUR FRIEND EDUARDO

[Gimballock]

HI FRIENDS HOW DO I INSTALL THIS PATCH SOMEONE CAN HELP ME THANKS YOUR FRIEND EDUARDO

Hi Eduardo,

you need to uninstall the old version and make sure no KA folder remains in your P3D Simobjects folder. Then you install 1.1.29 with the installer that you can download from the first page of this thread.
I don't remember where exactly I read this, but it has worked for me.

Have a nice weekend!
Stefan

[henrik.bergvin]

Build 1.1.29
Cabin pressurization
Flight: CNK4 - KORD @ FL260
Note: Cabin controller set correctly

After take off pressure remained at departure field elevation. Cabin pressure diff increased the the red warning light and a hi press diff warning came on.
Adjusted controller - no change
Tried dumping the cabin - cabin dump switch not functional.

Dave

I had this happen to me today, on a long flight RJCN DCT PTR DCT SYA DCT PASY, cruise at FL310. The pressure dial was set to 32 on the inner, about 9500ft on the outer. Rate checked to be pointing at halfway. I wasn't monitoring it that closely, but as I passed about FL200 the CABIN DIFF HI light came on. I checked, and pressure was still at surface, inner needle at max: https://i.imgur.com/PbVMWvq.png

One thing I have noticed though - if I switch the environment switch to NORMAL instead of AUTO, I get about 5 seconds of -1000fpm cabin change: https://i.imgur.com/8sIA84L.png

Back to AUTO, I get a 1000fpm climb for a few seconds. https://i.imgur.com/OmM8B9e.png

Oxygen is armed, I guess I'll let the passengers breathe through masks on this flight

This issue does seem to happen sporadically. I loaded up this flight by choosing airport, then choosing the aircraft to use MVAMS defaults instead of using the save I had. But I have had it on flights where the save was used.


Another bug I have found in 1.1.29:


The PTR waypoint is indeed 63nm away, but SYA is 1116nm away. In addition, DIST TO GO is wrong, and ETE DEST isn't showing. Neither is TIME ALOFT

[Taguilo]

I had this happen to me today, on a long flight RJCN DCT PTR DCT SYA DCT PASY, cruise at FL310. The pressure dial was set to 32 on the inner, about 9500ft on the outer. Rate checked to be pointing at halfway. I wasn't monitoring it that closely, but as I passed about FL200 the CABIN DIFF HI light came on. I checked, and pressure was still at surface, inner needle at max: https://i.imgur.com/PbVMWvq.png

Hi,

I've done many tests and still couldn't replicate that issue. There must be a very unique situation that triggers the effect.
I will keep trying.

One thing I have noticed though - if I switch the environment switch to NORMAL instead of AUTO, I get about 5 seconds of -1000fpm cabin change: https://i.imgur.com/8sIA84L.png

Back to AUTO, I get a 1000fpm climb for a few seconds. https://i.imgur.com/OmM8B9e.png

That is how the real controller works. AUTO mode can select low or high flow depending on conditions; if it was in low when you switched to normal (high) then cabin rate will decrease for some seconds until flow stabilizes again. And the opposite when going back to normal, or low: cabin rate will increase until stabilized.

The same behavior can be observed when switching one bleed air valve to off and back on.

Oxygen is armed, I guess I'll let the passengers breathe through masks on this flight

Actually oxygen is not needed as cabin remains at SL altitude. In real aircraft DIFF HIGH there is a risk of damaging the fuselage due to excessive pressure, but in MV KA this is not simulated. The flight can be continued without consequences.


Tomas

[ccmh15]

Just noticed two small things on the FMS Status Screen (please see attached screenshot):

• The Data Base State should be amber only when outdated I guess?
• Shouldn't the string under "PROGRAM" display the actual version of the KingAir (so 1-1-29)?

Maybe some other pilots here could check if they have the same, or if I did screw something up during the last installation of the KA and/or the Navigraph Cycle.

Thanks!
Cheers,
Chris

[Turbofandude]

The program string is indeed the version number, so if you're seeing that, it means you are running an outdated copy. Similarly, yes, the database shows in yellow when outdated.

[ccmh15]

Thanks for your response, did another full clean reinstall - now the correct version is shown, and the AIRAC version is also shown in white.
No idea how this happened, obviously really no one is save from weird things happening during reinstallations

Cheers!
Chris

[Turbofandude]

I'm glad all is well!

[henrik.bergvin]

I have run into a weird issue in .29 recently:

If I change the simulator clock (for instance via FSRealTime) to match a given offset or just to the UTC time, things will break:
* Pressurization will not work
* Engines will hot start
* Autopilot will refuse to follow any settings on the MCP - seems like it is stuck in roll/pitch mode no matter what I choose.
* Fuel flow will be shown on the display properly, but no fuel will actually be used.

The way I do it when I load up the sim normally is as follows:
* Choose the airport
* Choose the cold & dark preset by choosing the aircraft in the aircraft select menu
* Set time to system time
* Hit start and wait for the sim to load.
* Once the sim is loaded, I open FSRealTime and choose to reset to UTC time or to an offset. This often forces a reload of the scenery since I might go from night time to daytime, or such.

What I suspect is that the last step causes the issues described, it is the only common denominator I have. The only possibility I can see is that the KA dll keeps track of time as a way to see how long stuff has been running and to calculate fuel flow, which causes weird discrepancies when the time is suddenly -8 hours from where it was the last minute.

This issue became a LOT more pronounced when I passed through the prime meridian and headed into the USA where timezones are negative.

My workaround to get through this is to set the time to the local time at the departure airport when I load the game. I can then adjust FSRealTime to the proper timezone without having issues with the King Air.

[Taguilo]

The way I do it when I load up the sim normally is as follows:
* Choose the airport
* Choose the cold & dark preset by choosing the aircraft in the aircraft select menu
* Set time to system time
* Hit start and wait for the sim to load.
* Once the sim is loaded, I open FSRealTime and choose to reset to UTC time or to an offset. This often forces a reload of the scenery since I might go from night time to daytime, or such.

What I suspect is that the last step causes the issues described, it is the only common denominator I have.

Yess, that's the cause. NEVER change date/time/airport/aircraft within a flight. Always do that in Scenario screen.
Check : https://milviz.com/forum/viewtopic.php?f=105&t=11990

My workaround to get through this is to set the time to the local time at the departure airport when I load the game. I can then adjust FSRealTime to the proper timezone without having issues with the King Air.

Good to know, thanks!

Tomas

[henrik.bergvin]

Yess, that's the cause. NEVER change date/time/airport/aircraft within a flight. Always do that in Scenario screen.
Check : https://milviz.com/forum/viewtopic.php?f=105&t=11990

Well, changing time isn't explicitly mentioned there, but yes, I'm quite aware of it now Should be noted that I haven't seen this issue with any other addon aircraft I have (PMDG, FSL, Leonardo's Maddog) and I have used FSRealTime for over two years now. But I'll comply to following the procedure/workaround I have.

[Torkermax]

Yess, that's the cause. NEVER change date/time/airport/aircraft within a flight. Always do that in Scenario screen.
Check : https://milviz.com/forum/viewtopic.php?f=105&t=11990

Well, changing time isn't explicitly mentioned there, but yes, I'm quite aware of it now Should be noted that I haven't seen this issue with any other addon aircraft I have (PMDG, FSL, Leonardo's Maddog) and I have used FSRealTime for over two years now. But I'll comply to following the procedure/workaround I have.

Never had an issue with any other aircraft either. I find it odd. Simply changing the time of day while parked throws the aircraft into a frenzy. Not right IMO.

[Taguilo]

Never had an issue with any other aircraft either. I find it odd. Simply changing the time of day while parked throws the aircraft into a frenzy. Not right IMO.

This is not quite "another aircraft". Many systems perform simulating reality as much as possible, hence depending on seamless time evolution.
But you can try this: within a flight, go back to Scenario screen, change time there and back to flight. Not sure, but might work ok this way.


Tomas

[eric_mbat]

Hello
I bought this product (KA 350i) via orbx central. I don't have a serial key to install the update. Where can i get it please. I have so many problems with this aircraft since i bought it.

regards

Eric