Jump to content

Engine died for no apparent reasons


Gunfreak
Go to solution Solved by Art-J,

Recommended Posts

Auto start does not switch On "Guvernor Automation" - auto RPM control.

It is probably the reason for failure.

F-15E | F-14A/B

P-51D | P-47D | Mosquito FB Mk VI |Spitfire | Fw 190D | Fw 190A | Bf 109K |  WWII Assets Pack

Normandy 2 | The Channel | Sinai | Syria | PG | NTTR | South Atlantic 

F/A-18 | F-86 | F-16C | A-10C | FC-3 | CA | SC |

Link to comment
Share on other sites

Yep, over revving K-4 can easy kill engine. But someone had to not pay any attention to rpm gauge in flight to do so.


Edited by grafspee

System specs: I7 14700KF, Gigabyte Z790 Aorus Elite, 64GB DDR4 3600MHz, Gigabyte RTX 4090,Win 11, 48" OLED LG TV + 42" LG LED monitor

Link to comment
Share on other sites

  • 2 weeks later...

^ This time we've got a replay track and it's a bit puzzling indeed. Prop regulator clearly works and maintains RPM around 2200, boost never exceeds 1.25. The only thing that's worth investigating is oil cooler beahviour. Even at these modest power settings oil temp goes up during combat to 110 and stays there. Module manual is inconsistent in description if such temp is OK or not - in one place it says permissible max is 130, while in the other it says max is 95 but only "briefly" (?). So, which one is it - can we go above 95 or not? At the same time, oil cooler outlet flap remains almost closed.

The big MT patch allegedly brought some changes in oil pressure simulation, so one has to wonder it that hasn't caused some unintended (buggy) side effect? Last small patch hasn't changed anything further (probably, because we know patch notes are always incomplete).

Does anyone remember what oil temps the plane was reaching in typical combat scenarios two versions ago? In either case, some more test flying is needed.

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

Link to comment
Share on other sites

Thank you for your answer. My guess too there is "something" with the oil temp behaviour that cause engine to die. I did more tries at different altitude, til 20000ft, and the problem remains. Of course MW50 is unusable. Please ED investigate what's going on here.

Regards

Link to comment
Share on other sites

Here again 3 flights, in the 2 & 3 I removed the sounds mod from Echo19 for the Spit and the P51, switched off MW50 or selected P2 pump instead of 1&2, radiators in Auto or Open. Same result when I push to 1.39ATA. I joined the corresponding DCS log. Please forgive my aerobatic takeoffs😄

Cheers

Bf109k4 messing around engine quit1.trk Bf109k4 messing around engine quit2.trk Bf109k4 messing around engine quit3.trk dcs1.log dcs2.log dcs3.log

Link to comment
Share on other sites

Sadly, I cannot check the track-files atm. (bad performance after recent patches). I am not talking about the temperatures, I am asking specifically if you are doing the engine warm-up prescribed in the manual? Check the BF-109K4 manual on pages 123-124. If you haven´t done this, try it, follow the exact warm-up procedure, and check again.

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

7 minutes ago, zerO_crash said:

Sadly, I cannot check the track-files atm. (bad performance after recent patches). I am not talking about the temperatures, I am asking specifically if you are doing the engine warm-up prescribed in the manual? Check the BF-109K4 manual on pages 123-124. If you haven´t done this, try it, follow the exact warm-up procedure, and check again.

I understand what you mean but it happens the same with quick start missions even those starting in flight. I noticed most of the time the engine quits at 1.39ATA. As I can see I'm not the only one who get this trouble:

 


Edited by Jef Costello
Link to comment
Share on other sites

4 minutes ago, Jef Costello said:

I understand what you mean but it happens the same with quick start missions even those starting in flight. I noticed most of the time the engine quits at 1.39ATA

 

There is too much to ask about, without being able to see the track-file. The one final section of the manual, that you can check before eventually opening a bug report, is to check pages 142 and further (engine overheating). It´s possible that you are pushing the engine too hard for too long at too low speed, or any of the other listed reasons there.

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Oil gauges in german plane shows engine outlet oil temp and allied planes probes engine inlet oil temp , that is why german planes have limits at 130C and allied 90C-95C

110C oil temp in K-4 is completely fine.

  • Like 1

System specs: I7 14700KF, Gigabyte Z790 Aorus Elite, 64GB DDR4 3600MHz, Gigabyte RTX 4090,Win 11, 48" OLED LG TV + 42" LG LED monitor

Link to comment
Share on other sites

  • Solution

@Jef Costello Took a look at your last four tracks and found the culprit I think - you've always got fuel/MW selector set to "fuel" (down) position (see page 99 of the manual), which causes slow fuel system contamination with water and methanol - thus making the engine quit after a few minutes.

The selector by default shouldn't spawn in the wrong position in any mission (cold start / air start) unless you've got it assigned to some switch on your HOTAS, the switch sends the signal to the game all the time plus synchronize controls with HOTAS option is on. That's what most likely happens in your setup. I don't remember how this selector is called in controls, but that's what I'd check if I were you.


Edited by Art-J
  • Like 1

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

Link to comment
Share on other sites

12 hours ago, Art-J said:

@Jef Costello Took a look at your last four tracks and found the culprit I think - you've always got fuel/MW selector set to "fuel" (down) position (see page 99 of the manual), which causes slow fuel system contamination with water and methanol - thus making the engine quit after a few minutes.

The selector by default shouldn't spawn in the wrong position in any mission (cold start / air start) unless you've got it assigned to some switch on your HOTAS, the switch sends the signal to the game all the time plus synchronize controls with HOTAS option is on. That's what most likely happens in your setup. I don't remember how this selector is called in controls, but that's what I'd check if I were you.

 

Thank you so much Art, I'm gonna check that, may be I've a control assign to the selector and at the start of the mission it synchronizes the position of this selector to fuel.

Link to comment
Share on other sites

The cockpit tooltip might be confusing, so to sum it up: if rear tank contains MW mix - the selector handle should be rotated UP, if it contains fuel, the handle should be rotated DOWN.

By default, the plane should spawn with handle UP.


Edited by Art-J

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...