Art-J

Ha! Used to deal with this goo years ago at uni during flight mechanics lessons and when adjusting arms and areas while writing BSc thesis. The whole stability and controllability stuff was not fun to put it mildly. There's no way in hell I'm touching it with a ten-foot pole ever again . M3 devs will tweak things to their own liking anyway... In either case, there might be more to it. Weathervaning vs prop slipstream issues discussed in taxiing thread are tied to rudder simulation as well.

^ Well, Corsair is a bit of a the-other-way-around outlier here, 'cause its rudder has a much greater surface area than the fin, so I would expect the plane to be very responsive to initial rudder input and have a poor directional static stability in controls-free state. Still, with virtual rudder released and centered firmly (as in the case of majority of flight sim pedals without FFB), we're back at fixed-controls directional static stability state. Should dampening be so unimpressive then? I don't know. Vertical empennage being unusually ahead of horizontal one doesn't help with figuring it out either.

@Romo Have you figured out what exactly in Rhino software was causing the problem? And if you have, what was the solution?

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.

Same was happening to me during first Corsair flights after installing last week patch. With everything seemingly centered, plane required full left aileron trim just to stay somewhat level, it was also loosing all directional stability when slowing down for landing and once it failed to retract right main landing gear even though I didn't hit any ground object that might cause damage. First check of the forum if other users were reporting the same returned nothing, so I disabled my mods, ran a repair (not even full one, only the fast one) and enabled mods. Problem disappeared (for the time being, at least). I guess something got messed up during that loooong and slow patch download and installation process. Try repair youself, maybe it'll fix the issue for you as well.

Re. the armament, the dead horse that has been beaten numerous times on this forum, apparently Priller's book is the only anecdotal source claiming pods were used on -K, and there's no evidence of 151 being used in frontline units as Motorkanone either. Thus I wouldn't expect anything 20 mm being added. Cockpit refresh, on the other hand, why not? Albeit, if you're not fussed about multiplayer and integrity check, have you tried Sab0t's excellent 4k mod?

DCS has always been simplified/limited in this regard and doesn't differentiate between ground properties in winter or summer, wet or dry conditions, so there's no such thing as "frozen", "pepared/unprepared grass" etc. Maybe with a bit of exception re. grassy aifields on 3 WWII maps. Real life examples are irrelevant then - a more detailed implementation is needed (someday maybe?) and for now all we can do is being more careful and avoiding taxiing onto the dirt in anything newer than WWII planes. With that being said, gear collapse when taxiing seems too much - in other DCS jets one usually just gets "stuck" without such extensive damage.

Encouraged by the taxiing-related thread, which I don't want to derail, I finally tried the ground crew repair command to see what happens when it's used with Corsair, compared to other DCS planes. Something seems to be sketchy indeed. In other DCS warbirds upon spawn in single player mission, crew acknowledges the command, but nothing happens then and that's that. Only in Corsair, however, the 170 sec countdown does start (with all the messages + lifting and lowering of the A/C animation + relevant message in post-mission screen), which suggests the plane was somehow damaged somewhere already from the get go. I can ignore the landing gear showing unloaded state and sinking into the ground during lowering - I presume it's probably iffy animation and animations do not indicate what happens in physics code anyway. BUT, I also believe the repair cycle would/should not start at all if the plane was pristine in the first place, right? These are observations made today, based on cold-start missions (one stock and one custom) in latest version of the game.

Spawn damage and taxiing issues are not related simply because we unfortunaely still have all the latter when landing after air-start mission (when the former doesn't exist). Also, I'm "oblivious" because I've just never experienced it - but again, I haven't tried the ground crew repair process. If the process breaks the wheel then yes, it's a bug that should be fixed. It's good that you bumped that other thread because looks like ED hasn't implemented M3's fix in yesterday's build for whatever reason.

^ True. They still obstruct quite a bit of view on both sides, though! Damn annoying from my point of view, but at least we rarely need to open them fully.

I haven't flown 39 in a while, but by default you can do it in mission editor, in one of the tabs of unit options. There should be a "dismount gunsight" window there that you need to select.