Nealius

I argued the same many years ago to no avail.

Depends on what you did in the wires. It's just a location. It should be explained in the manual, but wouldn't be surprised if it isn't considering the current state of DCS documentation.

+1. Deck crew walk too slow, and they tend to walk back into the landing area after the 2nd jet traps, so the third jet ends up trapping with a foul deck, that isn't reported as a foul deck, because the LSO doesn't see the deck crew as units on the deck.

The most challenging thing I find so far, other than making taxi turns to the left (she likes to go right instead), is coordinating turns. Left turns seem okay, but right turns have significant adverse yaw that the pedals won't take out. At some point after adding more rudder I go from an uncoordinated turn, to the nose pivoting right as the airframe continues traveling straight.

Apache came with a Brit livery (and a bunch of others) on release. The lack of liveries in this release makes it feel a tad rushed.

It's right click for up, left click for down. In this case it's the airframe that's a bit different by having the "on" position down instead of up.

Stable level flight seems to require more trim taps than the Huey does. The nose attitude likes to wander up or down, and if you don't catch it immediately with a trim correction, it will run away from you. There's also a weird spot right about where I guess ground effect would start, or perhaps just prior, where sink rate suddenly accelerates.

Right, because all non-Russian speakers check the Russian site and translate it. This should have been on the English changelog, and there should be an explanation as to WHY there's a restart required. All other software tells you why when they require a reboot.

This is normal. Track files only work when played back on the same version they were recorded on.

Hopefully this will get resolved with further updates. My 4070TI Super with 16GB can't run the Apache in VR without overloading VRAM and causing headset artificacting. It's easily resolved by setting textures to medium, but needing more than 12GB of VRAM in a card is just rediculous and needs optimization. There is absolutely no need for such large texture sizes.

If "stepping on toes" (other map has this area) is considered a valid excuse, then Normandy 2.0 and Channel would have sections deleted as well.

Why model the uncommon when everything else models the common? The goal posts are being moved so much to fit what's convenient that a wishlist item seems pointless as well, if the arguments for not being consistent across all modules are going to be so arbritary.

Shouldn't these self-correct over time when flying straight and level? The old analog ones in the warbirds should, but in DCS they don't, which IIRC there's a bug report out on those.

For other ED modules, as well as previous changes to the A-10's FM and GAU-8 performance, SME testimony is considered "hard facts". Why is different logic being applied here?

In addition to what Gierasimov asked, tracer ammunition is not commonly used in modern US jets. SAPHEI (no tracers) would be a typical combat load. The only two exceptions I can think of are the Tomcat and Eagle variants, which have/had red tracers.

Good news is I figured out the comms issue: If you spawn on ramps November, Oscar, Sierra, Yankee, or Zulu, the comms tree defaults to the heliport as the F1 entry. Voice Attack profiles are programmed to press F1 as that should always be your spawn airfield.

With the amount of terrain detail bottlenecked by how fast you can stream internet? Even MSFS couldn't get that to an acceptable level, and they're orders of magnitude larger than ED. No thanks.

IIRC the A-7 was the first to have a CCIP as we know it today.

Appears to be a "hitbox" issue. The hitbox for the heliport is in red, airfield in blue. The heliport hitbox is prioritized over the airfield hitbox, and covers a majority of the airfield. This hitbox does not exist on the F10 map. This is also affecting radio usage, as spawning anywhere on the ramp within the red circle results in being unable to contact ATC on 360.20, while spawning outside the red circle works fine.

That seems to be part of the problem. Clicking on Kandahar (TACAN area) causes the heliport info to pop up instead of the airfield info. In the F10 map they're properly separated.

In the ME Kandahar's UHF is listed as 300.20, which does not function. F10 map info and functioning UHF is 360.20. Updated title; Clicking on Kandahar airfield in the ME shows heliport info. Clicking on the airfield in F10 map shows airfield info as it should.

It's still decoupled in-mission as well. Last night I flew in/out of Kandahar with winds set 2kts across the board and the Viper DED never showed higher than 3kts between 3400ft and FL200.

33, 1600, and 6600 were all at 2kts (using the decoupling mod for 1600 winds to not double), 26000 was 7kts. 9kts shouldn't have even been possible given the highest value was 7kts, and with Kandahar at 3500 it should have been well within the 2kts between 33 and 6600.

Maybe if it was a ghost. No AI traffic. Whatever it is, it's probably going to be as elusive as that old A-10 pitching on final bug.

Iran and the PG area does.