Art-J

It does and it should :). Not "jettison" in modern aircraft sense, mind you, but that red knob on top was connected via steel wires to pins holding the canopy, its rails and fuselage together. When pulled, it would release the canopy so that it could simply fall off the airplane blown away by airstream. I don't know if there's a functional key/button command to activate the mechanism, but clicking on the knob works fine.

Rgr that, I see. I thought you figured out some clever way to avoid creating temporary diff.luas and extracting this info straight from Windows. It means, however, that it's not "one minute job" when we add installing new tool, learning how it works (If it's uknown app like for me), launching the game, making temporary assignments, exiting, browsing, copy-pasting the names etc. I'd argue importing-profile method can still be easier and faster. I'm sure it's definitely faster on my PC, but I only have 6 devices to map and own a dozen of aircraft or so. Your method might indeed be better for guys who have all of them.

How does PowerRenamer know what all new GUIDs are and in what order the old files need to be renamed? Just curious, as I've never used it.

Can't say much about the Sabre, 'cause I haven't flown it in a long time, but Mustang for example, with its half broken radiator switches (not spring loaded anymore), broken control stick lock, permanently enabled cockpit lights at cold start (which doesn't make sense on bright daylight), broken oil dilution and recently broken main wheels animation has been clearly deteriorating slowly. 3 first mentioned issues have been with us for 5-ish years at least. Granted, one could say they're not critical because the plane can still takeoff, fly, blow sh..t up, return and land so minimal functionality in combat sim is still there allright, but the fact is module features which worked correctly in DCS 1.2-2.2 era, albeit not major ones, have been broken and effectively abandoned. After many years I finally stopped bothering with making or bumping bug reports because I don't see the point anymore if they tend to be ignored anyway, or noticed and pushed further by NL only every few months or so. I'm talking about warbirds mostly, as they're majority of purchased modules in my virtual hangar. Maybe F-16 / F-18 /AH-64 or other "flagship" customers are more lucky.

In the other forum you mentioned overheating issues (with resulting auto- FFB reduction) during prolonged dogfights. It would be fair to mention them here as well, especially when you use extension (what length is it by the way?)

Gyro AH not self - correcting in any phase of flight has been a DCS problem for many years and affects all warbirds. Brit ones are just affected the most since they lack cage/uncage AH feature that US and German ones have. We've been recently told it might be reviewed in the future. More info here:

^ Repeating the same BS ad nauseam in yet another thread won't make it real I'd say, but hey, you do you. One might argue about amount of torque on Mustang or other DCS warbirds, but it's demonstrably there allright. I left-flipped and crashed DCS Mustang years in almost exact manner as on video simply by forgetting about flaps full down on takeoff and being caught off guard by pitch-up after premature liftoff. Engine and prop effects did the rest. I suspect one can repeat it in DCS by doing what the poor guy on the vid did, which is adding extra elevator up and rudder left, making things worse. He only pushed the stick once he was already too deep in a stall.

Please explain in greater detail what you mean by "it never calibrates correctly".

1) You can reset attitude indicator by rotating the ring around it (it will cage and uncage the instrument, click and drag LMB to do that); 2) In all aircraft in DCS, when realistic comms is enabled, communication command ("\" by default) = shouting out of the cockpit, while PTT push-to-talk command ("RAlt + \" by default) = using actual radio. The latter might be called slightly different in different airplanes and helicopters, but that's the one you need to bind to your joystick and use after takeoff. Keep in mind that radio will have to be turned on in the cockpit and channels will have to be pre-set in mission editor correctly.

Just for the record, have you checked if snapviews are enabled in game options? I believe tinkering with FoV won't work otherwise (although my experience is limited to SP missions and editing one global file - could be the aforementioned server.lua, can't check 'cause I'm not home atm).

No, it will (or at least should) cause cold start on one of parking spots on ramp / apron. There is no option for cold start at the end of the runway in DCS (although I wonder it one could make it work with "takeoff from ground" option, never tried it myself)

Good question ;). I don't remember now, but I believe upper one is CGTC and lower one is Barthek. I might've added Taz's trees v6 medium to CGTC, but I'm not at my PC now to confirm

A major "D'oh" moment for me. Realized why I was getting longer 1st startup times on my config - I effin' forgot to update Defender exclusion list after moving my DCS folder to another drive! Did just that now and all is fine again with loading times.

Ah, it's been reported by players years ago, although I don't remember if devs acknowledged it. Apparently it's just an APU temp issue, next message gets triggered once temp goes below a certain value I don't recall at the moment. A dedicated bug thread always comes in handy, in the meantime, however, using time acceleration is the fastest workaround of this issue .

Not quite. If moment caused by weight of arm, grip and extension combined was the only factor then yes, at least at full deflection. During flight maneuvers, however, motors have to deal primarily with moment you create by pulling with certain perpendicular force applied at certain distance from pivot. Limiter changes neither of these.

As long as you don't touch Saved Games folder, they should stay as they are. Have you also tried disabling the launcher altogether and starting the game wthout it? You can do it by setting relevant parameter in options.lua file to "false", as shown below.

Interesting. I've noticed every first game launch after reboot (and only that one) seems to be quite longer indeed. So it's not a shaders-related symptom as they're already there. Maybe authorization-related? Because of disc space limitations I had to manually move my DCS folder to another drive so I'm not sure if updater needs more time to find things on my PC, though I always thought it only needed to connect to master server to check what content I'm authorized to use (?). Folder location shouldn't be a factor then. All MS Defender exclusions are active by the way. EDIT - problem solved on my part, see post below.

^ If that doesn't work, try excluding whole DCS folder from being scanned by Defender, temporarily at least (though similar issues will repeat every now and then so I'd do it permanently).

Nonfiltered, broken link from page 1 still points to v11. I guess they just haven't updated it properly yet. Filtered one above works fine, though. Interesting.

First and foremost, post your logs next time the game crashes. Without them we don't have any data to base our advices on, we can only guess. Logs might at least give us more clues about what's causing the crash. You can also investigate them to some extent yourself. Google for "DCS log analyser", first result will link you to analyser tool on discord which will try to diagnose the logs for you.

All fine and dandy, but the FoV scaling required for "true" size of cockpit seen on the monitor DOES depend strictly on monitor size and distance from user's eyes (and that's the data various online FoV calculators use). Resolution becomes a factor only when target spotting comes into play. Thus, your custom tweaks, although clearly lots of work went into perfecting them, are pretty much irrelevant for anyone who doesn't have exactly the same monitor size plus desk & seat setup as you. We know you're using 4K display, but what size is it and how far is it? Might be useful as a reference data for others.

Not quite, Channel map was developed by ED, and it shows. It has different overall colour palette and features more historically accurate airbase sceneries. I consider it a better map of two from visual point of view, but Normandy 2, being much bigger, has its own strong points as well. Just wait for a good promo sale and buy both.

Nah, I'm pretty sure it doesn't :). It's been like that since 2014 when I started flying warbirds in DCS, Mustang was the only one available plus Dora and Kurfy were coming. It was the first thing that caught my attention back then (when I couldn't even taxi to runway properly). It has also been a subject of countless "realism" debates ever since, both on this and other sims forums. Relatively Ineffective rudder from propwash alone is just a "thing" in ED-physics code and that's that. Yo-Yo has been programming it that way for more than a decade so I wouldn't expect any changes. One simply gets used to it, in a similar fashion to various FM peculiarities in different flight sims. Recent landing gear changes haven't affected rudder behaviour either from what I can tell.

He probably meant G-1 variant which featured 20 mm cannons indeed, plus old flexible single .50 & .30 mounts in dorsal and ventral positions. Cannon installation turned out to be a flop, however, so most, if not all G-1s were handed over to USSR. There weren't many of them anyway, so, as you pointed out, a much more common 6 x .50 nose should be used if we ever get a flyable G.

Rgr that. I'm not using Quaggle's tool, but good to know