Art-J

I got that pattern as well on the very first mission I loaded to check out v 2.0 . Murphy's law an all. Screen below. This is how "Broken cumulus no rain 1" preset looks like when clouds quality is set to "high". What setting do you use on your PC? There seems to be an issue with that single layer only, but it's being used in a couple of other presets as well, isn't it?

As noted in Dora thread, mission file can override player's settings in special options tab, including takeoff assist and autorudder. It's been like this in DCS for years. Stock taxi and takeoff training missions for both 190s are good examples as both have takeoff assist forced on whether you want it or not. It's very likely that custom mission you played had this override set up as well.

Your description of what you did during troubleshooting is confusing. What rob pointed out above is - aircraft folders with customized diff.lua files, located in Saved Games/[...]/Config/Input, if deleted, cannot "regenerate" during reinstall, as neither reinstalling nor repair command can bring them back. Unless some 3rd party software is involved? So we're not sure what and how you've done with which folders really.

^ Indeed. None of the warning lights seem to be working. That's unfortunate, beacuse this repaint is impressive otherwise.

It wasn't a question of insufficient research, the original Leatherneck dev team simply decided to add it for gameplay reasons, just like UPK gun pods, which weren't used on real Bis either. But it's all too off-topic here and was discussed many times in -21 section of the forum, back in 2014 when module was released.

It seems track reliability is also dependent on one's hardware (mostly peripherals). Thus, the same track can work OK for some guys and be useless for others even when recorded and played in the same DCS version.

^ I can only assume temp changes were slower / easier to manage (?) in RL, because when you think about it, P-51 was the only US WWII fighter with full auto cooling flaps. All the others, whether army or naval ones, were full manual or auto/manual hybrids.

Crumble, if you looked close enough, you'd notice cockpit card texture was made based on dash 8 non-water-injected version of the engine and not what "ours" should be in 1D Corsair, so it's incorrect anyway. M3 guys are still tweaking their engine code, so I suppose even they can't answer your question for the time being, as some parameters are going to change in upcoming patches.

Sigh.... Nah, you didn't, that's the point, at least not in both no-wind-taxiing tracks. Granted, I watched only these two to take the problematic wind out of equation. There's nothing in them comparable to the video, which shows that plane's inertia in itself, at a taxiing speed comparable to a jogging man, is sufficient to groundloop, even with engine off. It corresponds more or less to how the other single engine DCS warbirds behave, except Corsair (and I-16,which I don't own so can't comment on it). Your tracks, however, show different behaviour and highlight one of the issues I pointed above - you need to throttle up to military power for a moment (40-45" @ 2700) and then keep it at cruise power (30" @ 2700) to swing the tail around. That's simply not right. Let me post a short track of 109, doing something similar to the Corsair vid. No peripherals plugged in, so only mouse and keyboard were used. Even though I didn't keep the left brake on and just tapped it after shutting off the engine, the plane kept tightening the turn, as any taildragger with castering tailwheel would and should. Now, If I tried to do the same in DCS Corsair, it would stop straight, that's the issue. I don't mind imperfect tailwheel animation if it indeed turns out to be general DCS limitation that we have to deal with. Tough luck. There's something iffy with inertia (or rudder effectiveness?) at low power and taxiing speeds, however, and I hope devs will find some time to revise it again in the not-too-distant future. 109_turn.trk

No you can't* and that's not what this thread was initially about. All the talk anout the wind derailed it, albeit one can assume two SEPARATE issues discussed here might be somehow connected in the code. The issues are: 1) Inability of the tail wheel to caster freely while unlocked, which makes making tight turns with diff brakes (ie. taxiing out of parking spot to perpendicular taxiway) impossible unless you use full rudder + stupid amounts of power to literally scrape the tailwheel sideways across the ground. Simply put - tailwheel always remains locked either fully or partially (ie. it kinda unlocks but to about 30'ish degrees only). Watch the video of the real thing posted by Super Wabbit on the previous page. Wind or no wind, It's impossible to do the same sort of turn in DCS Corsair right now. * Makind mild turns with rudder only as in DCS Mustang is perfectly doable indeed, but that's not what we're talking about here. 2) Some excessive weathervaning caused by adding wind component to the mission. What wind speed threshold maxes turning impossible is still to be determined. I would also add a third issue of tailwheel getting stuck hard in the mud if one incidentally rolls off the runway/taxiway on some maps, which makes the plane very difficult to get moving again, but It's a different issue and I don't want to derail the thread myself.

I haven't noticed specific 580.97 thread yet,but you'll get more attention by posting in crash-related section of the forum: https://forum.dcs.world/forum/482-game-crash Keep in mind providing logs is crucial, because it's impossible to investigate anything without these really. In the meantime, you can also try to use DCS log anaylzer to try to narrow down the cause by yourself: https://forum.dcs.world/topic/343412-discord-dcs-log-analyser

Hoss, the module never had separate push-to-talk command, so I'm surprised it was picking up your VA in the first place . Should be no changes here. I'm away from my gaming rig so can't check implemented changes now, but reading other threads, I can see it's going to be a challenging experience.

Rudel posted excerpt from manual indicating how it' supposed to work now (?) but I find it even more confusing really

In either case, we're getting a -5 Zero (whether it's really 5b or maybe 5c is not quite certaint for the time being?) vs non-water-injected -3 Hellcat. These two are not THAT far apart in relative performance and they'll be even closer given similar experience level of online players on both sides.

Yup, guys have been reporting it for a while in F4U section of the forum, no ETA on a fix yet (at least to my knowledge):

The name of this very forum section did :D. But indeed, WIP shot seen above clearly shows extra 13.2 mm guns which shouldn't be there on b variant.

I've never played some of the default instant missions for P-47 because they override my snap-viewed personal FoV settings. I've read it's beacuse of some leftover file ED put in these missions. Now, If I play my own mission afterwards, i expect the game properly loading my own view settings and for Thunderbolt it does. That being said, I remember when for a few years we needed to load D-25 and D-30 Mustang missions in correct order to avoid loosing all custom controls, same for clipped and non-clipped Spitfire. I'm glad this bug was fixed eventually. Maybe ac5 discovered a new but similar issue which doesn't go away unless game is restarted? I do use snap-view customized FoV in my Corsair and I haven't yet experienced missions resetting it to default even though I switch between training and my own ones multiple times. The only time it happened to me was when I switched from American Corsair to British MkIV one, because the latter uses separate camera settings and thus I had to separately customize it as well.

If it's the one I think it is, you'll only stumble upon it when pilot's body is on and flight stick is hidden. Otherwise you'll never see it. I also believe it got fixed after few years in -C and "only" affects -ZA now (?)

Yes, that's what principle of operation of any trim tab in any aircraft is, no matter whether it's articulated by wheel, hat switch or whatever. Thus, in these planes which feature trim tabs and have control surfaces directly connected to control sticks, yokes and pedals, the latter want to move when trimming - unless pilot is strong enough to keep the controls fixed in place of course - then he will "only" feel force changes. FFB sticks should move a bit then for us gamers as well. If they don't in some modules, it means FFB implementation in FM is not yet complete, or FFB software of device itself needs further development as well.

Hey, it If it works it works. The 50% jump shouldn't happen in the first place, though, so something's fishy. MFG crosswinds here, set to full linear without curves, deadzones or anything. They modulate smoothly from 0% as they should so I'm puzzled why your Saiteks are acting up.

Ha! Fast and easy if you know what the new IDs are supposed to be, but on new PC with fresh Win 11 you just don't. The only way that comes to my mind is loading DCS, making single change to each controller in each aircraft so that a bunch of diff.luas with new file name get created, then exiting and doing the renaming. I'd hazard a guess, however, that it's going to take even more of tedious clicking than using built-in "load profile" option.

It ain't so . You old diff.lua files copied from old computer have old USB GUIDs in their names. New computer means new GUIDs, thus your new Windows doesn't recognize old file names. You have to do something to rename these old files so that new PC recognizes them. There's more than one way to skin this cat. The most idiot-proof is importing files one by one (aircraft by aircraft, controller by controller) using "Load profile" button in controls menu. It can take a while though, especially if you own lots of aircraft modules (multiply number of controllers by number of aircraft and you'll see how many files need to be imported). It's the only one I use, however, 'cause I'm too "programming-challenged" to write anything that would do it automatically for me. Not a big deal anyway, I can do 20-odd minutes of tedious clicking, one doesn't buy a new computer every year, right? For more info take a quick look at attached guide one of our experienced forum brethren posted here years ago (don't remember which one and aparently he was too shy to sign his work ). DCS_New_Computer.pdf

You should rather set both brake axes as sliders rather than "just" axes. That applies to all aircraft and all types of axes which are meant to work as 0 / 100% and not -50% / 0 / +50%. So throttles, RPMs, brakes etc. With sliders you won't even need such extreme curves to brake gradually.

You mean like DCS 190 Anton? Its needles are super wiggly below 1000 RPM (together with the whole cockpit) but they smooth out at higher RPMs. Yup, it might be an interesting animation example to consider.