GTFreeFlyer

I had previously shared a link to my kneeboards in various other threads. If you have been using my version, please update them to the ones I posted just now. Rudel posted the engine performance charts that we should be using, and I've updated them into my checklists here. Enjoy https://www.digitalcombatsimulator.com/en/files/3345803/

Great to know! Thanks for sharing. A couple of the guys in vCTF-58 were testing this out not long ago and came to the same conclusion.

Spoiler alert! Answers are in the manual. https://www.vmfa251.org/pdffiles/Corsair Manual.pdf

Awesome stuff Just don’t fall into the habit of setting cowl/oil flap positions and memorizing them. They need constant attention while eyeballing your instruments during a scan. Adjust them as necessary to keep the temps good. You can be conservative and leave them open more than needed if you aren’t worried about drag and fuel consumption, otherwise you want to close them a tiny bit at a time, wait a minute, see what the temps are doing, and minimize drag as much as desired. Also, the checklists call for 2400 RPM for landings … if the realism matters to you. What’s most important though is finding what works best for you and sticking with it I’m glad you got your bird running nicely. Cheers! …edit: Also, don’t memorize MP for landing. Adjust throttle for desired descent rate. Use elevator trim to adjust desired landing speed (90kts-ish). You should be hands-off on the elevator stick for final approach. The elevator trim will keep the plane locked in at your airspeed. If you are coming up short or sinking too fast, the correct remedy is throttle, not elevator.

Good info, Bull! However, just wanted to note that you can't even get close to the published numbers with rich mixture because the fuel burn will be way off, if that's a concern to you. Have a look at this and you can see the effect of rich vs. auto-lean:

Great idea! However, I don't know how to look up those values with lua at the moment. If you can provide that info I can try to integrate it. Also, I'm a big fan and advocate for pilots conducting instrument scans properly, especially in this warbird. I think moving some of the data from the instrument panel to the upper corner will teach bad habits, and might be a "cheat" for the mission you want to make which includes scoring. You might end up climbing quickly, but what good is the pilot if they never had to look at the instruments and handle the aircraft properly at the same time? Just my 2 cents. Cheers.

Here you go guys. A quick SP air start with a script I made to view real time fuel burn, fuel efficiency, airspeed and more. Spoiler alert: It is actually pretty close to the published charts. Also FYI, the image below is just a cover image. Diagnostics in the mission are not as pretty. It's just the standard text overlay you are used to seeing. https://www.digitalcombatsimulator.com/en/files/3346516/

Duplicate thread. Lots of discussion already. Have a quick look at the long discussions in the other threads. In short, no. Things have changed since the training missions were made. You need cowl and oil flaps open otherwise you’ll overheat.

Need a track file. You likely did damage to the engine beforehand and the engine driven fuel pump failed, if your temps were in fact okay. Did you hear engine knocking sound when you pushed the throttle up? Come back with a track file next time and I’ll gladly take a look for you. FYI, your intercooler flaps do nothing except add drag during takeoff. You need them to cool the carb air only when the blower is running. Without the blower, you aren’t generating heat in this area. You can leave them closed.

If you don’t feel like deep-diving into the actual manuals, try this for quick reference: 1. Know the engine limitations: You can find them in my kneeboards here. Set your MP and RPM accordingly. https://www.digitalcombatsimulator.com/en/files/3345803/ 2. Keep cylinder head temperatures below red line: Cooling for this is controlled with the cowl flaps. 3. Keep the oil temperature below the red line. Cooling for this is controlled by the oil cooler flaps. 4. Wait until your thick-sludgy oil reaches 40C and thins out before going above 1000 RPM after startup. 5. If you end up turning the blower on (above 5-6 thousand feet!) then cooling for that is with the intercooler flaps. 6. Keep a good scan of your instruments, always watching the temperatures.

Had a chance to watch this. It's the same issue everyone is having. Oil coolers not open enough, and you cooked the engine. Here's the NTSB preliminary report Oil temp was in the high blue zone, practically touching red line for the majority of the first lap. It was so close to the red line that I was unable to tell whether is was red lined or not. Maybe half the needle width was in the red, and the other half in the blue. You possibly accumulated damage here. Your oil coolers were open about 25%, and the inter coolers open a little more than that for the entire flight. You never touched them again for the entirety of the track file, after initially setting them. This likely indicates that oil temperature was not part of your instrument scan. Solution: Open the oil coolers more, about 50% or so and it will keep the needle in the mid blue range. If you see your needle the in the high blue and your oil coolers can be opened more, open them. You can even get the needle in the lower blue range. Intercooler flaps don't need to be open when not using blower. You can leave them fully closed here without consequence and eliminate the associated drag. You were not using blower, which is correct. No harm leaving the intercooler flaps open, but your engine just works a tiny bit harder to overcome the unnecessary drag. First two takeoffs: You pushed MP too high and heard the engine knocking sound, thereby accumulating damage. You reacted quickly though, and pulled MP back, which bought you some time, but the damage had already been done. Your RPM and MP changes were quick and abrupt at times, causing the needles to briefly overshoot their limits. Be smooth. Count 2-3 full seconds between the endpoints of any control when you are adjusting it. One the 2nd landing, you oil temp was a tad lower, but still in the high blue zone near the red, noticeably not touching the red line. Again, oil flaps need to be open more. 3rd takeoff: Oil temp was too close to red for a comfortable takeoff attempt. Don't forget to look at the gauge before takeoff and wait until it cools down a little. Much better on the takeoff throttle here. No knocking noise heard, but shortly after takeoff, the oil warmed up just slightly and touched the red line, and that was the end of your engine. In the current model, there's no buffer. It acts as an instantaneous trigger. Great patterns and landings though! If you do the exact same flight with only two corrections, everything will be fine: 1. Oil flaps open 50% or more. 2. Do not exceed 2700 RPM, 54 MP on takeoffs. When on the deck, push your RPM to maximum before opening the throttle. There were times you opened throttle to 50+ MP, but RPM lever was still pulled back from the last landing, and then you pushed RPM up. The order is backwards and puts additional stress on the engine because you are trying to take bigger bites out of the air with high MP. Flatten that blade pitch, then throttle up. Other recommendation: Your entire 3 flights were done on the main fuel tank. Make sure fuel selector is on reserve tank for takeoffs and landings. This will bite you in the future. When on main tank, as soon as your fuel gauge hits 50 gallons, engine will quit and you'll have to quickly switch to reserve. You don't want to have to do this when low and slow, ready to touch down. Cheers!

You can check your saved games/tracks folder to see if it auto saved. Otherwise, you’ll have to re-fly it. Also, there are already a few threads with this same topic. You just created another one. One of them has been open for a while and has lots of discussion. I’m betting your issue is something already experienced, discussed, and resolved. Have a look in the other threads as well. You didn’t mention opening your oil flaps, so you may have cooked the engine. That’s all I can offer at the moment based on the info you gave above.

Post a track file and someone will help. I enjoy a little investigation myself

Wrong thread. Plenty of other threads for that.

The fuel gauge includes the reserve. If you saw it at zero after your engine quit, then you were empty on the reserve as well. When on the main tank during a flight, you’ll see the fuel needle drop to 50 gallons and then the engine will quit. Quickly switch over to reserve and it will fire back up and you can use the remaining 50 gallons in the standpipe.

Whoa! This became a sticky. Very humbled. Thanks to whoever was responsible I updated the mission file. Minor update. Forgot to change the briefing image in the last update. It's fixed now. Enjoy.

Again, engine settings for takeoff will be found in the POH. Check out the link. Scroll down to the takeoff section if you don't want to read the whole thing. You can also install my kneeboards and follow them while in cockpit. This will help get you going as well. https://www.digitalcombatsimulator.com/en/files/3345803/

Couple things here: First, you are exploiting a bug that let's you go above 2700 RPM, which will be fixed soon. Don't go past 2700. Stick within the engine limits. You'll find these on placards in the virtual cockpit, as well as in the manual and actual POH. This bird requires you know the operating limits, so learn them and drill them into your head. As for everything else, it just seems that maybe you're still learning about warbirds and engine management, which is great! We've all been there and you've chosen the correct path I'll give you my observations to help out: After takeoff, set cowl, oil, and intercooler flaps as desired. You don't have to close them just because you think you need to. It all depends what is happening with your temperatures. I didn't see your engine cut in this video, but I'm willing to bet it is because you closed your oil flaps, then oil temps went into red line and you cooked the engine. Also, you don't need to do anything with the intercooler flaps unless your blower is on, which it's not for takoeff (I hope!). Leave those closed so you don't have more drag than needed. There's nothing in the checklist about setting your trims to neutral after takeoff. Leave them alone, and slowly trim as needed for hands off flight at your desired flight condition. I noticed as soon as you took out the right rudder trim, your slip indicator was showing you needed more right rudder, so you would have been better off leaving the rudder trim in, and slowly taking it out only as needed depending on what the ball was showing. As for the shaking, you may have broken something in the engine. You were at high manifold pressure and pulled your RPM back VERY quickly. This would have overstressed the engine big time. Manifold needs to be pulled back before pulling the RPM back. Very quick movements with RPM and throttle put additional stresses on the engine due to high accelerations and decelerations. Treat it gently, and she'll treat you nicely as well. Whenever you move from one setting to another, give it a full 3 second count from one endpoint to the next. This bird takes some studying, and learning the basic principles. All of the above can be found in the POH. Read the actual POH linked below, and it all applies to the DCS module as well. I've read thru this thing almost 5-6 times now. It's invaluable. Also read thru the manual included with the module, just so you know some additional DCS-specific things. https://www.vmfa251.org/pdffiles/Corsair Manual.pdf Just keep at it. You're doing great

Screenshot from actual footage of carrier qualifications and training back the day. Also, all checklists say 6 deg right trim for takeoff. Just FYI.

Just in case you weren’t aware, another thing you can do in the meantime is hit M key (I think that’s the default?), and it will turn off mirror reflections and save you a few FPS as well.

The outside air is also much warmer at lower altitude, so it’s two-fold: Less airflow plus warmer air. Yup, crack those flaps open

Haha, the opposite of the thread I posted where I said the shaking occurs too early. Try running the Moza profile as direct input, not telemetry, and not integrated. There is no telemetry coming downstream like other modules.

Also make sure you are using rudder properly and keeping the ball centered. The side of the fuselage is an extraordinary air brake.

I recorded a beautiful flight this morning, but having trouble with the track file export. I was even toggling the gunsight on and off for you whenever I was able to feel any stick shaking. This issue is something on my end for sure, nothing with the Corsair. I haven't saved a track file in many years. I'll get it to you eventually. Maybe someone can help me figure this out: After a flight I try to save the track file, and then I get an error saying that it cannot open C:\Users\[myname]\Saved Games\DCS\Tracks/LastMissionTrack.trk. That file does not exist in that folder, so I have placed another track file in that folder, renamed it to match, and then DCS is able to save the track, but what it really does is just make a copy of the existing LastMissionTrack.trk along with the new filename I gave it. It is not the actual track file from my last flight. It is currently autosaving any mulitplayer track file, but nothing for single player, even when I click Save Track after the flight is over. I'm stumped. While I figure this out, I can give more details: The stick shaking appears to start almost right at 3.0 G's, but there is still plenty of margin before a stall or buffet occurs. I thought it was tied to G's, but when I got slow and pulled back (All my movements were very slow and smooth while I was testing here), the shaking started closer to 2 G's. So now it makes sense that perhaps the feedback is tied to AoA, not G's, which I like, but it is just triggering a little too early in my opinion. In other modules, you'll feel the stall buffet onset, and then just a little tiny more pull on the stick will cause the wing to drop on you. In the Corsair, once you feel that stall buffet in the FFB stick, you can continue pulling, and pulling more on the stick before the stall occurs. Hope that makes sense. I'm running the FFB mode in Moza as Direct Input, since I get zero feedback when running in telemetry mode. I also don't get telemetry effects to my simshaker yet, but I understand that's really not a priority here so I'm not worried about it. Thanks! (I will keep trying to get a track file to export, and will send it when able).

There are a few of us making, or have made trim boxes for our home simpits. Please make sure the axis commands will still override any keybind so that the hardware stays synced up with the virtual knobs. Trim reset is a great idea for keyboard/hat switch users though! Just want to make sure this isn't overlooked if implementing this.