Jump to content

Recommended Posts

Posted

And for those that hate FB with updated info too

 

  • Thanks 1

https://magnitude-3.com/

https://www.facebook.com/magnitude3llc

https://www.youtube.com/@magnitude_3

i9 13900K, 128GB RAM, RTX 4090, Win10Pro, 2 x 2TB SSD, 1 x 15TB SSD U.2

i9 10980XE, 128GB RAM, RTX 3090Ti, Win10 Pro, 2 x 256GB SSD, 4 x 512GB SSD RAID 0, 6 x 4TB HDD RAID 6, 9361-8i RAID Controller

i7 4960X, 64GB RAM, GTX Titan X Black, Win10 Pro, 512GB PCIe SSD, 2 x 256GB SSD

Posted
1 hour ago, Holbeach said:

I have had 5 engine stops today, all on approach to the carrier..

It's never happened before.

I though of mixture, which I never touch, for simplicity. 

Here's one that didn't put me in the sea.

Should the MP read 30 with the engine stopped?

..

F4U carrier U strip 4 prop stop .trk 1.74 MB · 3 downloads

Your oil temperature is way over the maximum limits. When flying slow, like when on carrier approaches, make sure to open your oil cooler flaps about 30 to 50%. Your engine blew here because it overheated. Other than that nice landing btw 🙂 

  • Like 1
  • Thanks 1

CPU: i5-13600k // GPU: RTX 4070 // MoBo: B760-PLUS // RAM: 32GB DDR5-6000 // Stick: VKB Gunfighter Mk. III with SCG grip // Throttle: VKB STECS Mini // Pedals: VKB T-Rudder Mk. V

 

Posted (edited)
20 minutes ago, GTFreeFlyer said:

Here is a post from M3 today for those who haven’t seen it:

 

image0.jpeg

The problem is whether these are "You have X minutes until kaboom. Period." or "You have X minutes and it MIGHT kaboom." Because those limits got exceeded in the field, (if it came down to "following the book" and "not get shot down," I know which choice I'd make) and most pilots just got a stern talking-to from the ground crew while the engine was torn down for maintenance/repair afterwards.

And that's my whole problem with how engine heat has been historically modeled in flight sims: They inevitably make it an artificial hard wall where exceeding the book is going to kill you, rather than exceeding the book is just going to piss off your crew chief and HE'LL kill you when you get back to base.

A much more realistic short-term response would be loss of maximum power. Total engine failure might happen in extreme cases, but isn't necessarily a given. Most of the worse effects were the result of stress and damage over a period of time, not just one sortie (thus engine tear downs if the power limits were exceeded). IIRC in lab conditions an R-2800 was run for DAYS at maximum power without ill-effect.

Edited by Saxman
Posted
49 minutes ago, Ghostrider 147 said:

Your oil temperature is way over the maximum limits.


this is why a track file is so useful when diagnosing issues .. don’t get mad when someone that wants to help asks for one. 👍

  • Like 3

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted
51 minutes ago, -Rudel- said:

And for those that hate FB with updated info too

 

Maybe put this important piece of information in the Corsair section, rather than under an obscure title as 2025 Post Release Updates in the general M3 forum? It'd be also a good idea to post module-related information on the DCS forum also. 

Posted (edited)

The question is, is the 5 minutes time limit (It's more like just over 4 minutes from my tests) a total time for that flight, or 5 minutes at a time.  If so, some direction on how long we need to wait to go back into WEP to reset the timer would be nice.  From testing going into and out of WEP MAPs and adding up the time, it's a total of 5 minutes in the short term and the engine loses significant power and will seize if you do not back it off. 

I tried using WEP for 4 minutes and then going to low power cruise for about 10 minutes.  Then back into WEP.  It lasted another 4 minutes and I got the low water light just before the engine losing power.

Hopefully this is just a simplified modeling step because it seems solely tied to MAP and time.  I have not even tested if landing and refueling resets the timer.  If it does not, then it's even more artificial.  But, with the WEP-Cruise-WEP test, it seem like it does slowly reset.

Edited by Rhayvn
  • Thanks 1
Posted

I have been trying to practice carrier approaches & have found that my engine  quits most of the time after just one or two approaches. I see that the cylinder head temperature drops very easily with the rpm at 2400 & the manifold between 20 & 30 usually. I don't know what I'm doing wrong. I've tried both leaving the cowl flaps alone after spawning into the carrier landing mission & also continually adjusting them , but the engine always seems to quit. I had to give up for now on the Corsair School campaign carrier qualification mission since the engine doesn't last long enough for me to do 5 landings (not that I could do that many anyway, I'm new to this, but the engine thing makes it doubly hard). Here's a track.  Thanks in advance for any tips.

F4u engine quit.trk

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   1 member

×
×
  • Create New...