Nealius

Yes, but does that mean that DDR only had SA-3s and SA-5s? Were there no SA-2s or other systems in the DDR?

The thickness I can deal with, the tallness though is an issue, particularly on grass strips that should be cut much, much shorter.

I imagined that would be the case, especially for SA-2s, but all I can find are SA-3 style setups with the four pads fanning out from a central track radar position.

Looking through all the SAM site infrastructure I can't really identify what type of SAM system they are supposed to represent. The West German side only appears to have a single type of setup: Two raised berms for radar and 3 launch pads connected to each radar berm. It looks similar to a Hawk site to me, but the Hawk system has four radars yet we only get two raised berms? The East German side seems to have two types. One is fairly obviously SA-5, but the rest appear to be SA-3 in design. But again we only get one raised berm for the radar when there should be two. Where are the SA-2 sites? AAA/Fire Cans? Surely there were other SAMs and AAA sites particularly in East Germany.

Why do we even have spawnable points on gliderports/grass areas anyway? Those shouldn't be available for anything other than WW2 props and it isn't a WW2 map.

Each blade of grass is about as thick as my thigh too.

Did no one test this or think this through? Having them scale smaller as the user zooms in and/or giving the layer transparency so the user can actually see what's under it is common sense...

Did you get signal charlie?

What are your delivery parameters? Last week I did multiple bombing practice sessions dropping Mk82s in DT mode. Dropping in pairs, 6 passes (12 bombs). Run in from about 20,000ft above the target, 3-4G pull down, 20-30deg dive angle, 5-6ish G safe escape. My CEP was within 50m on all drops.

I'm not getting the bloom affect but I haven't been able to pinpoint why. The only thing I can think of is the "darker and less glossy" texture mod I'm using, because the bloom is still there on Forrestal, just not the CVNs for me.

Even at 1.2nm can be dicey. It's kind of weird because 1.2nm (IIRC) is within the prescribed procedure yet if you follow prescribed procedure of max 30 AoB in the groove turn while on-speed in DCS you will overshoot the LA every single time (WoD 27kts down the angle). I always need a more aggressive 35-40 AoB during the first 90 then I can settle into 30 in the last half of the groove to avoid a "wings" grade.

Yes, I downloaded and installed those luas on 11JAN25. The fix was posted 05JAN25 (at least according to the User Files date). I can try again though. I can't tell where those "US NAVY" ones are as they aren't in my Saved Games nor are they in any campaigns.

Definitely one of the more challenging aircraft in the entire DCS ecosystem. Usually after 20 hours I’ve mastered stick-and-rudder on something like the Bf109 or Spitfire but this beast is something else with the unique trim system and extremely laggy VVI. Without any inner-ear feedback it’s quite difficult to fly given its instability in pitch. Going heads down for five seconds to set the weapons panel or turn off exterior lights often ends with the nose pointing anywhere but where I left it when I thought I had her trimmed out. Good practice for recovering from unusual attitudes. Landing feels a lot better, though on-speed AoA has a much higher pitch angle than what I’m used to. My brain hasn’t caught up with that yet.

Found an old video on Yo-yo’s Youtube showing a rewind feature and it indeed was a new WIP system for replays. My point about them being mostly fixed in 2023 until recent “end of track fiber” issues still remains true.

Yep, using that fix, and copy-pasted the "updated" VS-24 skins from the recent patch to double check it wasn't my Saved Games liveries overriding the campaign liveries. A coulple of yours appear to be fixed but there are quite a few that aren't: VS-24 AJ hi-vis and lo-vis are both showing default gray 727. VS-21 NH lo-vis has missing textures on the rudder and horizontal stab VS-28 hi-vis and lo-vis are both showing default gray 727. VS-38 NE lo-vis has missing texture on the whole thing except the engine nacelles VS-38 NE (no lo-vis or hi-vis naming) is showing default gray 727 Baltic Dragon's Bloodhounds 700 and 702 are also showing default gray 727, and his 701 is missing a default.lua file entirely.

For a "rare" thing it happens every time I fly near or over an airfield in Afghanistan...

Even the Mudhen, which had development ceased before Afghanistan, has a functioning map at all zoom levels. The Kiowa's map functions at all zoom levels as well. There's no reason ED modules shouldn't have this by default when 3rd party modules have them from the get go.

Recent campaign update says they're fixed but they still are not. Both Baltic Dragon's Raven One skins and Tomcatter's CVW-8 skins are still showing as default 727.

Not really, since the fog height setting still effectively does nothing when you set a value higher than cloud base height. Fog height should reflect the numerical setting in the ME regardless of where the clouds are, particularly if one is using it to create haze rather than fog. Doubly so on maps at higher elevations like Afghanistan where sub-10nm visibility is fairly standard for the region.

I believe the mod makes all glass clear, as if you didn't have a canopy at all, though it's been at least a couple years since I tried it.

I read your post and it does not indicate anything about fast forward/rewind, and my response has every relevance to both your comment and the question posed by the person you were responding to. Furthermore, ED has stated here on these forums and/or in a newsletter that they were working on including fast forward/rewind features, which again debunks your claim that they "can't do anything" about fixing them.

This is really a DCS-wide issue that affects a lof of modules, but some are affected more than others so maybe it can be tweaked on a per-module basis, but in overcast settings the collimator lens is way too opaque and reflective, turning everything within that lens space into an amorphos blob. It's impossible to discern targets through it, and in some cases it's not possible to pick out ridgelines against higher terrain behind them. You can also see in this screenshot the trees are easily distinguishable out the left and right sides of the canopy, but where the collimator glass is it's just a dark blob with some smudges. In addition to making it difficult to employ A2G weapons it makes low level flying more precarious than it should be in daylight when one considers both the transparency of an actual collimator and the human eyes' ability to adjust to lighting conditions.

Yep, .dds files are from the November 2023 links and the description.luas are from January 5 link. They were working fine for me back in February.

Still seems to be an issue with many default Hornet liveries. VFA-87, for example, is still blank.

Looking through the S-3 tanker skins that came with the campaign, 700 and 702 appear in the mission editor but 701 doesn't due to it lacking a description.lua in the file structure. Skins are also broken again, displaying as the default unmarked 727. Already filed a bug report here: