Art-J

I recall oil cooler, unlike both coolant radiators, is auto-only and cannot be manually closed to warm up oil faster, unfortunately.

^ All fine and dandy, but irrelevant in this case, as the one and only reason why the enigine quit in second video is the same as in the first one - MW/fuel selector on left side of the cockpit is down (fuel) position while it should be up (MW mix). By the way, manual doesn't say to check it, so even if he follows the manual to the letter, his engine will still keep quitting. The plane should spawn with selector up, so it's probably a controller binding issue.

Playing devil's advocate - I've yet to see an airworthy warbird restored and rigged to factory, period-correct state. They're set up to for safe, relatively cost effective and comfortable modern ops, obviously. In scale and virtual modelling they're considered secondary sources for a reason, with period documentation always taking priority (if available). We can see on previous page that description of horn operation in period doc is unfortunately ambiguous and confusing at best. Is ED's interpretation incorrect then? Might be, but until someone comes up with a better period source that's all what we've got for now. Is it such a big deal, though? Depends. It's possible to fly around well below 7 lbs without horn by dropping RPM to econo cruise values, I do it all the time. Not bothered by incorrect ASI texture either, it's such a minute detail that I only found out about it in August when relevant bug report was posted, even though I've owned the module from the beginning. Granted, I fully understand that for some players these small issues can be proverbial straw that broke camel's back in the grand DCS warbird scheme of things, but as of now Mossie is otherwise fully mission-capable in single- and multiplayer, so there's no need to put in in virtual hangar, in my opinion at least.

Nah, no active FFB devices at all on my side. I've got racing wheel plugged in, but it's powered off by default and thus shouldn't interfere. Now that I think about it, don't remember if I've got FFB ticked in special options, though. Shouldn't have, 'cause I always un-select it but will double check if it got reset after recent update.

Years ago I was wondering about the same at first, but later when I thought about it - if aft tank is supposed to provide extra long range fuel supply in that configuration for all flight including cruise, it wouldn't make any sense if it worked only at emergency power, would it? I didn't investigate the ins and outs of the system deeper, though, 'cause I usually don't use aft tank for fuel anyway.

@lothar29 Putting all cooling related aspects aside, as peachmonkey noted above, in the video your MW/fuel selector is set to "fuel" instead of MW mixture. If your plane was in standard config (ie. aft tank filled with MW mix), that means you were constantly dumping water and methanol into your fuel system. Petrol engines don't run on water , so your DB605 quit after a while. It's been modelled like that since module release by the way and default selector position has always been "MW", so If yours is flipped down after spawn, I would check if something hasn't changed in your control bindings after the last update.

What about the usual culprit number 2: MW-fuel selector switch? Have you checked if it's in correct position when you spawn?

I had the gear thing (right one in my case) happen already on takeoff, ie. failure to retract even when no flaps were used. Haven't played DCS in a week, but I wonder if re-saving my old custom training missions would help? I recall reading it might, although I don't remember if it was in reference to Corsair or MiG-29 shenanigans after latest patch.

Anton got new stock cockpit textures and slightly revised geometry in July last year. Maybe something got changed at the same time in a way these textures get loaded now, 'cause you're not the first person to report not being able to make cutomized textures work with special options.

I think what OP wants to point out is whacky volume balance in Corsair module specifically, compared to all other DCS warbirds, which have their external/AI sounds noticeably more quiet (at least idle and low RPM sounds). That was something that surprised me immediately after release as well. Since we can't tune sounds individually per aircraft, changing global settings isn't great solution really, 'cause it will mess up balance in all remaining modules.

Note, he says he already did both, though and looks like something somewhere in Saved Games causes the problem. H60MTI, it's time for manual trial and error method, unfortunately, folder by folder. I'd start with excluding MissionEditor one. A few guys in other threads reported issues with launching the latest version of the game and a file in that one was the culprit (albeit their symptoms were a bit different?).

Just a reminder - an auto-level mod for Mossie and other warbirds was posted here a few months ago. Granted, it was most likely not IC-compliant and I don't know if it worked OK in campaigns either, but for single player crowd it was better than nothing.

Yes there is, following this guide... https://forum.dcs.world/topic/94816-guide-info-dcs-updater-usage-version-numbers-module-ids/ ... but it's a desperate last resort solution in my opinion. Have you tried temporary renaming/removal of your Saved Games/DCS folder as Sleighzy asked you to do? Repair and cleanup doesn't affect this one, so we have to figure out first if there's something hidden over there which might be causing problems.

You probably read about new tyre and shock absorbers physics model implemented months ago in Mustang, Thunderbolt and Mosquito. Remaining warbirds haven't received it yet indeed.

Did you place any of these customized files in Saved Games folder? Repair command doesn't affect that one, so if source of problem is buried somewhere over there, neither repairing nor module reinstall will help. It's easy to check - rename your Saved Games / DCS folder temporarily, launch the game so that a new clean folder is created and see if problem persists.