Right engine crashes on every take-off

[Taguilo]

Hi,

To all, just to be sure please read : viewtopic.php?f=105&t=11990

Thanks

Tomas

[Taguilo]

I asked about hardware because I had the same thing, although with annunciator lights also. The warning light would come on saying my engine was being operated beyond limits IMMEDIATELY upon startup. I could ignore it and fly with no torque or ITT or other limits being exceeded, but the engine state would be severely degraded. I haven't had that issue since I put away my Saitek throttle.


Kdub

Hi,

Which annunciator light comes on? Shouldn't be any; exceedances are only displayed on respective gauges, not on annunciators.
Can you give more details? Thanks.

Tomas

[Nac301]

Hi,

To all, just to be sure please read : viewtopic.php?f=105&t=11990

Thanks

Tomas

This post is EMPTY

[Ephedrin]

just a guess.. But could you check the value inside the Simulator.ini here:

C:\Users\yourname\AppData\Local\MVAMS\Configurations\KingAir350i

Does the value actually reset when you restore it in MVAMS?

I personally had some issues in the "January version" too (sry not sure about the number anymore ) and simply set the file to read only. it's not what Milviz intend but at least my engines don't wear anymore. My sim with all its addons takes about 10 minutes to start the flight from double clicking the exe and my patience has suffered a little too much

[mml]

Hi,

Which annunciator light comes on? Shouldn't be any; exceedances are only displayed on respective gauges, not on annunciators.
Can you give more details? Thanks.

Tomas

Hi Tomas,

Kdub is right. I'm also getting a red master caution light as soon as the airplane leaves ground. But I don't have Saitek hardware. I'm using a thrustmaster and this one works for all my airplanes without problems.

Again and again, version 1.1.8 worked after initial installation quite a while without problems. Except the known bugs, of course. Then something must have happened and the engine problem appeared. Still version 1.1.8. All versions I tried afterwards including 1.1.7 and 1.1.9 fail. The aircraft rotates, red master caution light and the aircraft shows a strong drift to the right during rotation already and does not climb. The outer view shows that the right prob does not rotate and the engine display confirms that.

I can keep the aircraft a few feet above the runway or even landing again is possible. On ground again, the aircraft seems to be completely fine. You can shutdown the engines and start them again. But when you try to takeoff it is exactly the same. Very strange.

A MILVIZ comment on this would be greatly appreciated

[atlandrew]

Chiming in with the same, or at least, a similar problem. Both engines immediately cut out 30 seconds after takeoff after no problems in startup or taxi (nothing in red, following all procedures, etc) and this problem is repeatable. I have tried taking off with reduced power, props but get the same problem every single time. MVAMS is the same on engine condition after the failure which is in the green. I have tried resetting it and no changes. I have disabled almost all add-ons and the problem persists.

[jk.wall]

I seem to have cured my issues by re -installing Prepar3D_v4_Academic_4.5.13.32097 It clicked this morning that all my problems started when I installed HF3. Now back to a system that runs.

[Taguilo]

Guys,

Just in case problems persist for some of you, here you have a test gauge that can be used to monitor engine health status

MV_King_Air_350i_Test.rar

(93.04 KiB) Downloaded 166 times

First backup your Panel.cfg file and then copy the one provided in the rar file.
Also copy the XML file from B350i in rar to B350i folder in KA.

Now engine status can be checked by loading 2D popup "Engine Fail"
Value starts in 0 for max health, and degrades towards 100. Once reaching 100.00 engine will factually fail in any moment.

Hope this helps.

Tomas

[mml]

Tomas,

I installed the Engine Fail Test panel. Same result, right engine crash on startup with a good engine health. I've appended 3 pics showing what happened. First pic on runway immediately before takeoff. Pic 2, immediately after takeoff. You can see right engine failed already, prop does not rotate any more. Engine health displayed is still in the green. Finally the MVAMS windows also showing perfect engine health.

It is pretty obvious to me that the information given by the panel and MVAMS don't show what is really going on. Bug or feature but it simply doesn't work. BTW, I performed the test flight still on HF3

Michael

[Taguilo]

Hi,

Already checked by other user and engine parameters are ok still they quit after take off.

It is not a KA direct issue but probably produced by a third party addon conflicting, or a conflict with P3D HF3 version.
Did you check that P3D default engine failures is not enabled? Does it happen with any other turboprop aircraft?


Tomas

[mml]

No enigine failures in P3D enabled. Turbine Duke and Dash Q400 without problems. It seems to be a unique KA350 problem.

I'm using the following add-ons:

FSUIPC V5
Navigraph Simlink
GSX
Chaseplane
Active Sky

That's it. Except FSUIPC I've deinstalled test-wise all of them. No effect. Probably an HF3 issue? We have at least one report above that it works fine with HF2.

Michael

[hasse.w]

I use the same addons and Fsuipc and HF2
No problem

[Taguilo]

Please check :
viewtopic.php?f=105&t=11990

And be sure to comply with KA loading methods.

Thanks

Tomas

[mml]

Tomas,

I checked this a couple of times but it has absolutely no influence on the engine problem.

BTW, I do not fully agree what you wrote about (1). To my knowledge, (1) loads a flight that has been previously defined and saved as P3D standard flight. And the properties of this particular scenario etc. will be apply to all aircrafts.

This is the reason that the standard flight should always be defined with an P3D stock aircraft. Otherwise it can happen that payware aircrafts and others don't work correctly. This issue is well known for PMDG and Majestic. Please feel free to correct me if I'm wrong.

Michael

[Taguilo]

Tomas,

I checked this a couple of times but it has absolutely no influence on the engine problem.

Michael,

The engine failure system is not the cause of your trouble, certainly. It must be some configuration of your system that is affecting. Unfortunately I cannot assist you here further than I had. I would need more clues because it is not a KA350i code failure.

BTW, I do not fully agree what you wrote about (1). To my knowledge, (1) loads a flight that has been previously defined and saved as P3D standard flight. And the properties of this particular scenario etc. will be apply to all aircrafts.

This is the reason that the standard flight should always be defined with an P3D stock aircraft. Otherwise it can happen that payware aircrafts and others don't work correctly. This issue is well known for PMDG and Majestic. Please feel free to correct me if I'm wrong.

Michael

When P3D starts it displays Open Scenario with the default (stock) F22 aircraft. That is the basic situation needed by the KA to load correctly.

Tomas