missinig info P-51 engine quits.... a LOT

[Boomer_G-Loc]

It happens during the P51 vs P51 dogfight instant action in the Caucasus region.

1st time it was about 30 seconds into the flight right after the merge. I didn't see  him fire at me, but assumed I had been  hit. 

After that, it kept happening, but only seconds into the game (like 2 or 3 seconds after start).

Each time I would do an emergency landing into a field. And I don't know if the game allows it, but on the way down, I'd try for an emergency restart,  but get absolutely nothing. 

When starting the gameflight, the engine is already at the default game starting throttle setting, and again, this is now happening within the first 2 - 3 seconds of gameplay. 

All my engine gauges appear normal when it happens,  only thing I see happen is the  ammeter drops from normal to zero when the engine quits, but all else seems normal, unless I'm missing something deeper here....

I started saving and reviewing the tapes, and the opponent is not shooting at me, so I am not hit at the  merge. 

Can someone tell me what's going on here?

I have the 2.7 DCS version that is  *not* the open beta one. 

Thanks, 

[Steel Jaw]

Are you pulling negative g’s?  The engine is carbureted.

[Boomer_G-Loc]

No, either straight & level, or starting to turn towards opponent 

[Paganus]

Check for a crossed controller mapping. Something that will shut it down quickly like the magneto or fuel cutoff.

[Boomer_G-Loc]

I checked all those in the cockpit views,  all switches were in operating position. 

Will the cockpit view not represent the actual condition?

I have not mapped engine controls to my current stick.

But I will review the file. 

[Paganus]

Does it only happen in the one mission, or all P-51 missions?

[Art-J]

2 hours ago, Boomer_G-Loc said:

I checked all those in the cockpit views,  all switches were in operating position. 

Will the cockpit view not represent the actual condition?

Well, there's still a months-old bug in P-51 with carb levers moving but not actually working if operated by mouse, but that in itself shouldn't kill the engine, it "only" reduces your power somewhat.

What Paganus means is - there are always multiple duplicated assignments in default controls table and unless you spend some time browsing through it and deleting them, you might be cutting off your engine with some button press without knowing about it.

In either case, posting a replay track would help a lot, otherwise we'll be running in circles here.

[grafspee]

5 hours ago, Steel Jaw said:

Are you pulling negative g’s?  The engine is carbureted.

It has injection type carburetor, it has no float chamber, negative G does not effect it in any way, so no abrupt cut outs under negative G, engine will cut out eventually due to fuel starvation, fuel tank's sumps not designed for negative G operation, but no abrupt cut outs.

[MAD-MM]

8 hours ago, Boomer_G-Loc said:

It happens during the P51 vs P51 dogfight instant action in the Caucasus region.

1st time it was about 30 seconds into the flight right after the merge. I didn't see  him fire at me, but assumed I had been  hit. 

After that, it kept happening, but only seconds into the game (like 2 or 3 seconds after start).

Each time I would do an emergency landing into a field. And I don't know if the game allows it, but on the way down, I'd try for an emergency restart,  but get absolutely nothing. 

When starting the gameflight, the engine is already at the default game starting throttle setting, and again, this is now happening within the first 2 - 3 seconds of gameplay. 

All my engine gauges appear normal when it happens,  only thing I see happen is the  ammeter drops from normal to zero when the engine quits, but all else seems normal, unless I'm missing something deeper here....

I started saving and reviewing the tapes, and the opponent is not shooting at me, so I am not hit at the  merge. 

Can someone tell me what's going on here?

I have the 2.7 DCS version that is  *not* the open beta one. 

Thanks, 

Maybe check where your RPM Lever is when you air spawn, it is located next to the Throttel. Possible inverted Axis there?  Usually this destroys your Engine pretty fast when the  Lever is in Idel RPM and the Engine is running full Boost with the Throttle. RPM Lever should be also fully Foward like the Throttle.

[Mr_sukebe]

OP, you sure that you didn’t overheat the engine?  It’s VERY easy to do, bizarrely so when the Spitfire seems to be near impossible to overheat, despite using the same engine

[Doughguy]

its unusual that your engine would die if you spawn in mid air if you do not make any adjustments and just fly straight level.

the system starts with a default setting and takes  a few seconds to read your inputs (eg throttle axis etc) and adjust to these unless you make adjustments on your own.

make a quick editor mission for simple flight, check, and save a track so we can see.

anything else is pure guessing.

[grafspee]

2 hours ago, Doughguy said:

its unusual that your engine would die if you spawn in mid air if you do not make any adjustments and just fly straight level.

the system starts with a default setting and takes  a few seconds to read your inputs (eg throttle axis etc) and adjust to these unless you make adjustments on your own.

make a quick editor mission for simple flight, check, and save a track so we can see.

anything else is pure guessing.

If he has sync controllers option checked it will sync all inputs as mission starts, this can lead to unaware inputs applied.

But wild guessing is just pointless, track is very much needed.

Edited December 9, 2021 by grafspee

[Ercoupe]

On 12/9/2021 at 5:13 AM, Mr_sukebe said:

OP, you sure that you didn’t overheat the engine?  It’s VERY easy to do, bizarrely so when the Spitfire seems to be near impossible to overheat, despite using the same engine

Yeah, that was my thought when I read the post. Are you watching your red lines? Keep your eyes on your rpm's and manifold numbers. Go over the red line and your prop will stop dead!

[Lixma 06]

On 12/9/2021 at 1:10 AM, Boomer_G-Loc said:

1st time it was about 30 seconds into the flight....After that, it kept happening, but only seconds into the game (like 2 or 3 seconds after start).

Nothing could overheat in that short time - sounds like a controls conflict or mis-mapping (fuel cut-off?). All speculation without track file.

[Florida]

On 12/8/2021 at 8:10 PM, Boomer_G-Loc said:

It happens during the P51 vs P51 dogfight instant action in the Caucasus region.

1st time it was about 30 seconds into the flight right after the merge. I didn't see  him fire at me, but assumed I had been  hit. 

After that, it kept happening, but only seconds into the game (like 2 or 3 seconds after start).

Each time I would do an emergency landing into a field. And I don't know if the game allows it, but on the way down, I'd try for an emergency restart,  but get absolutely nothing. 

When starting the gameflight, the engine is already at the default game starting throttle setting, and again, this is now happening within the first 2 - 3 seconds of gameplay. 

All my engine gauges appear normal when it happens,  only thing I see happen is the  ammeter drops from normal to zero when the engine quits, but all else seems normal, unless I'm missing something deeper here....

I started saving and reviewing the tapes, and the opponent is not shooting at me, so I am not hit at the  merge. 

Can someone tell me what's going on here?

I have the 2.7 DCS version that is  *not* the open beta one. 

Thanks, 

I was constantly having that problem, and panicking, when I finally realized that my Mixture was randomly going to Idle Cut-off. I still have the problem - no idea what is causing it - but I now have a switch on my throttle with 'up' being RiUN and 'down' being Idle Cut-off, and a button for Full Military Power. And as soon as I hear that Merlin cough, I just click on 'RUN' to fix it.

I also thought that I may have a duplicate binding I didn't know about, so I went to that binding and deleted everything connected to Mixture, including the keyboard commands. It still happens randomly, but not as bad. Tell the truth, I'm beginning to suspect my X-56 throttle control, because I have also had both gear activations and flap activations with no physical inputs. ..both controls are on the throttle control.

Edited January 31, 2022 by Florida
Thought I misssed something...

[Sarge55]

I recall many years ago when using my old X-52 that there was an issue with ghost commands as they were called. That maybe what you have going on. 

Are you using the X-56 software to program any of the controls?  IIRC I had to use the saitek software for a couple of commands to simulate an extra axis or something  

So it could be the X-56, just a thought…

Edited February 1, 2022 by Sarge55

[NineLine]

Please supply tracks of the engine quitting. 

[jamante]

On 1/31/2022 at 1:32 PM, Florida said:

I was constantly having that problem, and panicking, when I finally realized that my Mixture was randomly going to Idle Cut-off. I still have the problem - no idea what is causing it - but I now have a switch on my throttle with 'up' being RiUN and 'down' being Idle Cut-off, and a button for Full Military Power. And as soon as I hear that Merlin cough, I just click on 'RUN' to fix it.

I also thought that I may have a duplicate binding I didn't know about, so I went to that binding and deleted everything connected to Mixture, including the keyboard commands. It still happens randomly, but not as bad. Tell the truth, I'm beginning to suspect my X-56 throttle control, because I have also had both gear activations and flap activations with no physical inputs. ..both controls are on the throttle control.

 

I have the same 3 random problems using my X56: mixture going to cut-off, gear retraction on take-off roll, and random flap activation.

I Also have the 2 fingertip buttons (labeled H and I on the throttle) mapped to chase and cockpit view. I get random jumps to the chase view in DCS and also MSFS.

 

[71st_Mastiff]

same

 

P51D30 engine just quits, instant missions,  seems to be some issue with the oil and water coolers not working in auto mode again,  when using the key binding customization assigned.

de-Brief state engine failure, but all steam gauges show nominal.

Screen front UI is green in the hanger, 

track I guess to big but at the end I'm rammed by a 109 K, didn't even engage me; just rammed right through my wing no damage to the 109 K4.

 

https://www.mediafire.com/file/y0jtv6573o8n97g/28p51d30.zip/file

 

 

 

 

 

 

Edited October 31, 2022 by 71st_Mastiff

[AJaromir]

Yesterday I did fly P-51D for hours, without issue. Only once when the oil was not warm enough for take-off. In debriefing was "engine jammed". But that was pilot's mistake. I also was able to run it on full WEP for 10 minutes. Until the engine is not too hot or too cold, it will run smoothly for a very long time.

Edited October 31, 2022 by AJaromir

[NineLine]

3 hours ago, 71st_Mastiff said:

track I guess to big but at the end I'm rammed by a 109 K, didn't even engage me; just rammed right through my wing no damage to the 109 K4.

So what is the issue, the engine or the 109?

 

[71st_Mastiff]

8 hours ago, NineLine said:

So what is the issue, the engine or the 109?

 

P51D30

 

I found only that when you use custom keybinds they seem to work but the oil and water cooler are not actually returning to automatic.

and I don't see the oil & water inlets working.

the mention of the BF109K is it didn't engage me it just rammed right through me.. BF109K not taking any damage. but removed my wing as it went through me.

 

 

Edited November 1, 2022 by 71st_Mastiff