P-51 is the most environmentally friendly aircraft in the world

since I bought the module I must have checked those settings about a billion times, and they were always on simulation mode. I even reinstalled 'cause I thought something was wrong, but still no difference, and btw, A-10 and Ka-50 are fine...

Is this a custom mission? Each mission can have its own difficulty settings, which override global ones, unless you force usage of global settings for every mission (not sure if responsible checkbox is fault free completely, I had some inconsistencies with it in the past).

it was the free flight over poti mission, from the instant action menu. Anyways I've consistently experienced the same engine behaviour in every mission I've flown, even in MP...

Fly again, abuse it, then exit the mission after you have decided it should have died long ago, save a track, attach it here.

ok, will do tomorrow. Thanks ;)

Ok so here are some tracks and tests.

Track 1: basically what I have shown in my first video.

I start by abusing the throttle up and down several times, then I run at max throttle, ~150 kts, all temps are over the limit, at the end I do a short run at low RPM/Max MP.

Track 2: this time I do a low level flight, minimum RPM/Max MP both with and without WEP. Then I lower the flaps and fly at 100 kts still with minimum prop/max HP, temperatures raise to the gauge limit. As you will see the track is very long. No problems with the engine.

Track 3: here I run at max throttle / max rpm at low altitude for about 10 minutes, then I engage WEP for another 10 minutes. I keep temperatures within normal limits, although I totally exceeded both WEP and Military time limits. I'd expect some problems from engine stress, but nothing.

Again, vanilla install with all settings in SIM mode and the checkbox to enforce settings to all missions. The mission used is "Free flight over Poti".

Now some personal considerations from my tests:

- I have been able to lock up the engine ONLY under these two conditions: High MP with High Temps.

-High temps alone never cause problems. That is the case of track 1, where I am at about 14k feet and the MP at max throttle was around 47~50. Even though the temps were maxed, nothing happened.

-Conversely, in track 3 I fly at WEP but I keep temps reasonable by manually opening radiators. Again, no failure.

-Other types of abuse, such as slamming the throttle back and fwd, overspeeding the engine, cold starts then immediately full WEP etc. don't cause any problems.

I am running DCSW (latest version) on Win7 64-bit. Intel i7 2600K, Ati Radeon 6950 2bg, 8gb of RAM. Pretty standard system, works with every other sim, including DCS A-10 and Ka-50 without issues.

-Other types of abuse, such as slamming the throttle back and fwd, overspeeding the engine, cold starts then immediately full WEP etc. don't cause any problems.

I'm baffled. Just two days ago my engine stopped running because I took off from the taxiway immediately after starting my engine, without warming up first. I've likewise experienced failures merely from diving steeply without throttling back to prevent over-revolving. I don't know what's going on on your end, but I'm guessing that there's either a problem with your installation, or perhaps one of your program settings.

That "override mission settings" option--doesn't that only work if the mission itself doesn't have its own "override options" setting? It's been a long time since I've messed with it, but if my memory serves, the program prioritizes mission settings over options settings--I think the override only works when settings aren't specified in the mission?

Have you tried to watch the tracks I uploaded?

Seems like everyone dropped dead the minute I posted proof of what I was saying :huh:

Should I open yet another bug report / ticket / thread about this? Honestly...

Now I'd love to see proof that those tracks I posted actually play correctly on your systems and your engine shows the correct behavior, and after that I'd like to PLEASE get some assistance from the devs since I've spent way longer trying to prove I'm not crazy than actually enjoying this product.

Thanks.

Ok so here are some tracks and tests.

 

Track 1: basically what I have shown in my first video.

I start by abusing the throttle up and down several times, then I run at max throttle, ~150 kts, all temps are over the limit, at the end I do a short run at low RPM/Max MP.

 

Track 2: this time I do a low level flight, minimum RPM/Max MP both with and without WEP. Then I lower the flaps and fly at 100 kts still with minimum prop/max HP, temperatures raise to the gauge limit. As you will see the track is very long. No problems with the engine.

 

 

Track 3: here I run at max throttle / max rpm at low altitude for about 10 minutes, then I engage WEP for another 10 minutes. I keep temperatures within normal limits, although I totally exceeded both WEP and Military time limits. I'd expect some problems from engine stress, but nothing.

 

Again, vanilla install with all settings in SIM mode and the checkbox to enforce settings to all missions. The mission used is "Free flight over Poti".

 

 

Now some personal considerations from my tests:

- I have been able to lock up the engine ONLY under these two conditions: High MP with High Temps.

 

-High temps alone never cause problems. That is the case of track 1, where I am at about 14k feet and the MP at max throttle was around 47~50. Even though the temps were maxed, nothing happened.

 

-Conversely, in track 3 I fly at WEP but I keep temps reasonable by manually opening radiators. Again, no failure.

 

-Other types of abuse, such as slamming the throttle back and fwd, overspeeding the engine, cold starts then immediately full WEP etc. don't cause any problems.

 

I am running DCSW (latest version) on Win7 64-bit. Intel i7 2600K, Ati Radeon 6950 2bg, 8gb of RAM. Pretty standard system, works with every other sim, including DCS A-10 and Ka-50 without issues.

bkthunder:

Only today was I aware of your post. I will give your tracks a try and report back ASAP!

I have had a few engine problems, but not many because I try to carefully manage power and temperatures. In the beginning though, I broke a few engines :-/

Seems like everyone dropped dead the minute I posted proof of what I was saying

I've never doubted that you experience what you say you're experiencing. I just cannot understand why, because my own experience differs so greatly. My engine fails at the drop of a pin if I don't juggle everything just so--too hot, too cold, too high RPM, too high MAP, etc. My only idea is related to what ZaltysZ was saying--I think you need to create a new test mission yourself, with the options forced to max difficulty within the mission editor. I suspect that the override option in the options menu isn't working as one would think it should. All of the missions I fly have always had options forced to max diff. from within the editor, so that might explain the discrepancy.

Seems like everyone dropped dead the minute I posted proof of what I was saying :huh:

As was said, I'm pretty sure we all believed you were actually seeing an anomaly, however after exhausting all of our ideas... there isn't much we can say. Are you saying a fresh re-install had no effect? Of all the people posting on here I haven't heard of anyone having these specific problems.

Looking forward to the day when you can gripe about engine management issues with the masses. :)

Here's my 1st try... a very simple climb at max continuous, radiators closed...

killingTheEngine.trk

Ok, I played your track and the engine failed properly.

I also repeated your same maneuver in the mission "free flight over poti" and I had the same result on my system (yay!).

I also tired a run with WEP enabled and the engine locked up after 3.45 minutes (no warning signs this time, but seems realistic for a sudden lock up).

What I still don't get it is why I am getting these results, I mean, I haven't touched anything since when I recorded the tracks, also, those tracks were recorded in the very same mission where now I am getting engine failures....

So here's what I did, I restarted DCS, and voila', no failures this time... I'm puzzled.

Ok, I played your track and the engine failed properly.

I also repeated your same maneuver in the mission "free flight over poti" and I had the same result on my system (yay!).

I also tired a run with WEP enabled and the engine locked up after 3.45 minutes (no warning signs this time, but seems realistic for a sudden lock up).

 

What I still don't get it is why I am getting these results, I mean, I haven't touched anything since when I recorded the tracks, also, those tracks were recorded in the very same mission where now I am getting engine failures....

 

So here's what I did, I restarted DCS, and voila', no failures this time... I'm puzzled.

Can you establish any relation between those symptoms and the latest 2 patches?

The latest patch did do something really weird to the sounds, the UH-1H sounding better to me, but the P51d sometimes producing a very weird sound (?)

Let's hope it is something that went wrong, and will get solved on the next patch!

Can you establish any relation between those symptoms and the latest 2 patches?

The latest patch did do something really weird to the sounds, the UH-1H sounding better to me, but the P51d sometimes producing a very weird sound (?)

Please post in this thread:

http://forums.eagle.ru/showthread.php?t=106768

Can you establish any relation between those symptoms and the latest 2 patches?

The latest patch did do something really weird to the sounds, the UH-1H sounding better to me, but the P51d sometimes producing a very weird sound (?)

 

Let's hope it is something that went wrong, and will get solved on the next patch!

Actually no, I have always had those problems with the engine model since the P-51 came out of Beta. Still very weird, it's almost as if the engine model got "switched on" when I played your track. BTW how did my tracks play on your system? Try to take control and see what happens then.

Actually no, I have always had those problems with the engine model since the P-51 came out of Beta. Still very weird, it's almost as if the engine model got "switched on" when I played your track. BTW how did my tracks play on your system? Try to take control and see what happens then.

Sorry bkthunder, yesterday I didn't find the time to test your tracks, but I will try again tonight and will report back!

Ok, bkthunder, you're absolutely right in your observations.

Only the first track, when I take control, will lead to an engine failure, just like in the other track I recorded and posted above in this thread.

Your two other tracks never resulted in any sort of damage, even interrupting the track and taking control.

I restarted DCS, loaded the Free Flight over Poti, and repeated the same mistakes continuously, playing with the throttle and prop rpm, setting coarse and MP at max for a loooong period, and nothing ever happened to my engine :helpsmilie:!!!!

What's going on here?

Ok, bkthunder, you're absolutely right in your observations.

 

Only the first track, when I take control, will lead to an engine failure, just like in the other track I recorded and posted above in this thread.

 

Your two other tracks never resulted in any sort of damage, even interrupting the track and taking control.

 

I restarted DCS, loaded the Free Flight over Poti, and repeated the same mistakes continuously, playing with the throttle and prop rpm, setting coarse and MP at max for a loooong period, and nothing ever happened to my engine :helpsmilie:!!!!

 

What's going on here?

Thanks for taking the time to test this out :thumbup:.

So apparently there might be two "issues" here:

1. I am experiencing random on and off behavior of the complex engine model, that's referring to track 1 where my engine doesn't fail in a long climb, but it fails on your system. SO here we might have a bug of some kind, maybe related to some personal system settings or some other stuff.

2. tracks 2 and 3 act the same on both my system and yours, indicating that the engine model doesn't take into consideration factors such as RPM vs. MP and rapid throttle movements.

Maybe the engine model isn't so complex after all?

Can anyone else please try out the tracks and report back? We might be on to something which the devs could use to improve the sim ;)

tracks 2 and 3 act the same on both my system and yours, indicating that the engine model doesn't take into consideration factors such as RPM vs. MP and rapid throttle movements.

Maybe the engine model isn't so complex after all?

Again, I don't doubt that you are experiencing these problems (and I've already written my suspicion as to why), but I can say that--on my end--the engine model most certainly does take into consideration factors such as the RPM-MAP relationship and that firewalling the throttle suddenly at the wrong time can cause over-revolving and engine damage. I've done it.

Again, I don't doubt that you are experiencing these problems (and I've already written my suspicion as to why), but I can say that--on my end--the engine model most certainly does take into consideration factors such as the RPM-MAP relationship and that firewalling the throttle suddenly at the wrong time can cause over-revolving and engine damage. I've done it.

Echo38, I will continue to test, but I have been able to reproduce bkthunder's tests on my DCS install, and using different situations for start (including takeoff from Batumi).

I am yet to see something happening to my engine even after long periods running it at full MP (sea level) and RPM full coarse, or playing around with the MP and/or Prop levers for also long periods, wildly moving them back/forth...

I am almost sure about having had to take a lot of care with my engine some versions ago (?). I'd say something was modified in this area (?)

Again, I don't doubt that you are experiencing these problems (and I've already written my suspicion as to why), but I can say that--on my end--the engine model most certainly does take into consideration factors such as the RPM-MAP relationship and that firewalling the throttle suddenly at the wrong time can cause over-revolving and engine damage. I've done it.

So you've tried track 2 & 3 and you get an engine failure?

Yo-Yo, why is ignition timing dependant on throttle and not on RPM? Does the speed of the flame front depend so much on boost pressure?