Blackbird Sims / Milviz Forum Archive

All of a sudden, the right engine started to fail on every take-off as soon as the wheels loose ground contact. Never had this before over weeks since I'm flying the aircraft. Sometimes you can see the bad engine state after in MVAMS, sometimes you can not. I've of course always resetted the engine state to "good" after an engine failure.

I've reinstalled multiple times different versions of the aircraft, also the latest two. After deinstallation I've deleted all remaining files in the Prepar3D and Appdata directories, but no effect. I've also checked take-off with and without anti-ice. No difference.

At the moment, the aircraft is unflyable. Something is definitely wrong but what can I do ? No ideas left. The P3D installation seems to be fine (HF3) and my other aircrafts fly as they should.

check this

viewtopic.php?p=98622#p98622

Not Quite similar but a engine problem that has come up in the latest upgrades
last flight from EKCH-ENCN a little over one hour Engine work all the way no overstress... Climbout 1700 rmp reduce too 1600 at climb about fl100 /800 at fl 200 never exeed red area no warnings
but the engines is damn old after that short trip ...see pic ....
One time on the trip in desend i overspeed with 10 knots for 10 sec before i got it back too normal but that will not blow a engine in real world
Please give me some engines that works more than one and a half hour pr trip
Everyting works normal no warnings at all exept overspeed 10 knots for 10 seconds

Still a little hard on ram use but no ctd
and i use evntx and as16 same grapic as i use with latest pmdg 737-800 NGXU


Sorry for my bad english but i think you understand
Best
Robert

Nac301 wrote: ↑

Wed Apr 29, 2020 12:20 pm

check this

https://milviz.com/forum/viewtopic.php?p=98622#p98622

This is something completely different. Not relevant for my case I guess. But thanks anyway.

Like wise, however my left engine packs up as the wheels leave the ground. Reinstalled every thing last night no difference today. No red lining, no hot starts.

Can anyone shed a light on this please.

Hi,

Which status are you selecting to load the KA at startup? (C&D, ready to start, Current Conditions, etc)
Always the same?

Please go to USER\AppData\Local\MVAMS\Configurations\KingAir350i and check that folder has total control rights.

I suggest to try with Current Conditions and see if issue persists.

Thanks

Tomas

jk.wall wrote: ↑

Wed Apr 29, 2020 4:35 pm

Like wise, however my left engine packs up as the wheels leave the ground. Reinstalled every thing last night no difference today. No red lining, no hot starts.

Can anyone shed a light on this please.

Seems to be exactly the same problem. Interestingly, in your case it's the left engine. Which one do you start first ?

Taguilo wrote: ↑

Wed Apr 29, 2020 7:09 pm

Hi,

Which status are you selecting to load the KA at startup? (C&D, ready to start, Current Conditions, etc)
Always the same?

Please go to USER\AppData\Local\MVAMS\Configurations\KingAir350i and check that folder has total control rights.

I suggest to try with Current Conditions and see if issue persists.

Thanks

Tomas

The issue is completely independent from the start status. I checked all of them. The User\AppData\etc. folders have full access for my personal and the Windows system account. Checked this also. This should not be the problem.

Version 1.1.8 worked correctly for a while and then from one flight to another the right engine problem has started. From that moment on no version that I tried worked correctly including the latest 1.1.9 build.

I'm more thinking of a silent windows update or something similar. However, I'm lost and have absolutely no idea what I could try.

Ok,

YOu can try this:

- Go to MVAMS and restore engine state.
-Load a KA flight, start both engines and end the flight right afterwards. Close P3D
-Go to MVAMS and check your engine status.

Let me know.

Thanks

Tomas

PD: Remember P3D must NOT be running when you restore engine state

Okay so followed the suggestion, restored MVAMS with P3D closed.
Loaded in current conditions that had engines all running. Ended flight (End Scenario) closed P3D
MVAMS showed Engines all good, restarted and just off the ground and Left (left from pilot seat) engine stopped again, no red lines MVAMS shows engines are still good.

Is there away to remove MVAMS and reload? I have not checked when updating if MVAMS is removed or not.

Getting late may try removing the folders in USER\AppData\Local\MVAMS\Configurations\KingAir350i and remove all files and reinstall, tomorrow.

jk.wall wrote: ↑

Wed Apr 29, 2020 9:09 pm

Is there away to remove MVAMS and reload? I have not checked when updating if MVAMS is removed or not.

Getting late may try removing the folders in USER\AppData\Local\MVAMS\Configurations\KingAir350i and remove all files and reinstall, tomorrow.

You can simply deinstall MVAMS via the system management and remove the remaining files manually. But I tried this a couple of times, didn't help either.

Just a wild guess, what throttle hardware? As in brand of throttle hardware?


Kdub

Okay so removing all files and reinstalling has not helped.

Not sure where to go with this.

I have a Logitech / Saitek Yoke and single throttle quadrant

Okay, so have uninstalled P3D with HF3 and all folders cleared and reinstalled original version. Now to rebuild all add on's etc. But in the air and flying. Suggests that there is something in HF3 that is causing a problem.

Same here. And I think it is completely hardware independent.

I also checked an influence of the saved standard flights. But this seems not to be the case. The engine simply crashes immediately after take-off whatever I do and I cannot get rid of this any more.

I think it is a severe bug that occurs under certain circumstances. At least it is a show stopper for me.

Michael

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