Nealius

JFS starter sound introduced after RB fixed sound synch issues over multiplayer. Reported nearly a year ago:

"Study level" means the only documentation is real manuals--if you can find them or can legally access them. Then when something goes wrong you have to guess whether it's a WIP implementation, incorrect implementation, software bug, or user incorrectly interacting with the software, and when brought up on the forums you just get shot down with "our SMEs said..." or Rule 1.whatever which put an arbritrary date on "legal" real-world manuals.

Still not fixed, nor acknowledged. SC-lights-Caucasus.trk

P-51D, Spitfire, and Bf109 were the only three effected on my end. All other props, including the Yak, were fine. No injectors here.

Was the sound update only for the TF-30s? The B Tomcat sounds still sound the same as before the update.

Mine does....the PTT on my HOTAS has to be mapped to the same as the PTT in-game or it won't work.

It works for you with the VAICOM PTT bound to RAlt+\? I haven't used VAICOM since we got the commands to cycle through the comms menu, but for me when I press RAlt+\ the PTT switch moves, receive/transmit light indicates transmission, I hear a click, but no comms menu ever pops up. The Mossie manual still says RAlt+\ for realistic communications as well. Found the problem: Update enabled Easy Comms by default. @NineLine why are updates messing with user settings like this? Our settings should remain untouched by updates.

Partially, I suppose. I haven't tried hailing ATC to listen for a response, however RAlt+\ does not bring up the comms menu despite the PTT switch in the cockpit being animated as pressed (and the radio light going off until released). I checked the P-51 and P-47 as well, same problem. In the jet modules comms work as advertised.

For years RAlt+\ was the functioning keybind for radio communications, with \ only functioning for ground crew while on the ground in the Mosquito, other warbirds, and all other modules across DCS. Now RAlt+\ is not functioning in the Mossie despite having an audible click when pressed, and \ has become the default radio communications menu.

If beta testing isn't being done on end-user equivalent builds/rigs then their testing isn't exactly valid....

Pilot: "Why do we have to fly left-handed while raising/lowering the chas.....underca.....f***it gear?" Engineer: "Sounds like a you problem."

You guys should try the K-4. Literally no consistency in switch position in relation to function, and a number of them don't even have labels

Oh, global issue then. I've only ever noticed it on Nevada so far.

Basically as per title. It's like the sun sets into the ground itself:

Perhaps an overgeneralization. Most switches except the battery and two magneto switches (going off memory) in the Mosquito is reversed from an American perspective. With only three switches not conforming to the standard of the other umpteen, one is apt to say "every switch is backwards" while not meaning that literally every switch is in fact backwards. People have a tendency to change "most" into "all," and "hardly ever" into "never," etc. Drives me nuts when people aren't more specific and/or accurate in their communication.

It's visually distracting, and lingers right in the middle of the instrument panel, unlike a one-line verbal "fuel-check" that lasts one second, if that. "It's not a problem for me and the limited selection of testers we asked therefore shouldn't be a problem for everyone else" (otherwise known as bias) isn't valid reasoning for invalidating our gripes. Muting unfortunately doesn't hide the W popup on fuel check or the low altitude check, though logically it should, and might actually be a reasonable workaround for those of us who don't want it to pop up at all.

How about verbal fuel check but nix the UI popup. It's the sudden UI popup that's most distracting while flying and completely ruins replay tracks on top of that. We can go through the Jester menu to set divert on our own anyways once the action settles down, so there's no need for a UI popup the moment he asks for a fuel check. It should be verbal only for the pilot to then decide what to do later, not at that specific moment, and waiting for the "W" UI to disappear is a pain.

Flight plans are not visible in F10 map, and flight planning is done BEFORE entering the aircraft. With magnetic declination varying up to 8 degrees across the entire map (e.g. Kola) doing the mental math isn't that simple. The ruler in the Editor and Planner should have magnetic heading visible as well.

In low-light conditions, particularly overcast, the HUD collimator or reflector gunsight glass for all modules becomes horribly opaque and gray, making it nearly impossible to judge terrain, obstacles, or line up on targets. It's even worse in VR. Here's one example in the Hind, 2D. It's much worse in VR.

The new weather system is unable to create weather commonly found (especially in Marianas) where there's sunshowers or scattered showers with scattered or broken clouds, and good visibility. The closest preset to this would be "Rain and Overcast 1" however it is too overcast, too heavy rains, and too poor visibility for sunshowers.

The menu is an improvement, as is the context button. However he's way too chatty with no concept of brevity or efficiency, nor a sense of timing for things like the fuel check, which interferes with mission critical tasks.

It's one thing to be disappointed by delays, but DDOS'ing ED in response to the delays? C'mon people....

That's essentially what we already had before shifting to a 6-week patch cycle, which was only practiced for two or three patch cycles before this planned one which was at a 4-week interval. I seem to remember we used to have a bimonthly patch cycle, which then changed to monthly, which then changed to 6-weeks, but my memory on that is fuzzy.

Except for the latter half of the PTO the Japanese didn't have any good pilots. Instead of rotating the good ones out to train new ones, the Japanese military kept throwing them into the fray until they were all dead. This combined with Japan's traditional education style of "don't think for yourself, do exactly as you're taught," the majority of Japanese pilots had no knowledge or experience in tactical employment.