Nealius

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:

S-3 and S-3 tanker skins are broken again. Continuation from this locked thread after they had been reported and fixed: Baltic Dragon's and Reflected's liveries, only available in their payware campaigns, are not working. Tomcatter's liveries, also used in some of Reflected's payware campaigns, are also not working--mainly CVW-8 but others have missing elements as well.

S-3 liveries are broken again. A couple work fine, but most--including those that come with paid campaigns--do not.

This is false. 19 October 2023 update (2.9.0.46801) completely fixed the replay tracks on human controlled aircraft. The "unexpected end of track fiber" error didn't start consistently until summer of 2024. Multiplayer tracks seem to have had a separate CTD issue in the December 2023 update. Point is, replays worked reliably regardless of SP/MP or scripts for two months, and continued working on SP regardless of scripts for about eight months. The defeatest claims that they "never worked" or that "they can't be fixed," or that the cause is "scripting" have zero evidence to support them. On the contrary, there is ample evidence showing that they DID work and they CAN be fixed. It's just hard to find that evidence because everyone here has such short and selective memories they never bother to search, and searching is often sabotaged by ED's tendency to merge threads and delete useful comments in the process.

I might be late to the party but I recently discovered you can tilt the free camera (RCtrl+F11) clockwise or counterclockwise with the 3 and 1 keys, respectively.

It was with the taxi directors, yes. And I've been here long enough to know that even if we do provide track files things won't get looked at, usually because they're "too long" or involve "scripts" which somehow invalidates the whole bug report. But then when you provide a no-script short track it sits with 0 downloads for months, completely ignored.

Recent update has changed fog altitude to max out at the lowest cloud base height regardless of ME height setting.

Visibilty distance still seems messed up. With it set to equivalent 20nm visibility, returning to the carrier Mother isn't visible until 5nm or so.

Unlike a lot of languages that have one or two standardized romanizations, languages in this region don't. I've seen 4-5 different spellings for the same place across the ALT map, the MAP map, real-world MGRS maps, and Wikipedia. Getting all these names to conform to a standard is impossible when said standard doesn't even exist.

Last update screwed with the bindings. I lost my antenna elevation bindings as well and had to redo them.

Lots of issues still remain unfixed as well, and recently the IFLOLS calibration was broken. Two Hornets cannot be connected to Cats 1 and 2 simultanously, significantly slowing down launch operations. Deck crew have stopped moving with urgency and slowly walk, significantly slowing down launch operations. AI launching on the bow cats get stuck on the cat if other aircraft come in for recovery, breaking cyclic ops. IFLOLS is consistently about two balls lower than actual glideslope. Others are having issues where the IFLOLS isn't usable at all due to excessive light bloom.

Usually "one-way" airfields have a reason for being one-way: mountains, cities (post-WW2), etc. These don't have any logical reason for being one-way.