Nealius

Just checked myself, and yeah the Mk20 does not have an altitude fuse option at all. However, the Hornet (and Tomcat, and Harrier) should be using the CBU-99 anyway as that's the thermally-protected Naval variant of the bomb. No idea how the USAF guys are supposed to use their Mk20s, though, if there's no altitude fuse option.

Does temp and baro pressure affect rotor spool up times in a similar fashion as it does with engines? The real-world video appears to be winter. DCS video is spring/summer, and most likely warmer.

Is it possible you have the wrong fuse set in the payload menu? The airburst fuse has a much different nose section than the default fuse that was standard pre-update. It does not have timer options, and has an altitude function drop-down menu.

Doesn't really help that the real-world terminology is a bit of a mess, and varies by country. Currently "AA" seems to mean anything that's surface-based anti-air, including both ballistic projectiles and guided missiles. In the US services I heard rumblings of moving away from "AAA" to "ADA" (Air Defense Artillery?) but a cursory search only shows the US Army using that term. There doesn't seem to be an agreed upon definition of the terms, and no mention of "AA" vs. "AAA" differentiating between projectile size; that was done by affixing "light" or "heavy" to the acronym of choice, e.g. light AAA or light flak for 20mm etc., heavy AAA or heavy flak for 88s. That's in general usage, though, while guns like the QF 3.7 are offically named "AA" for whatever reason. Ignoring the acronyms and country/linguistic variations, all are classified as "anti-aicraft gun," so something to that effect might be a better category. Which really makes more sense as a broader category anyway since cannon, auto-cannon, small-bore, large-bore, rifle, etc. are all ultimately "guns" in the end.

22JUL hotfix, still doing CASE II when visibility is CASE III. Surely I can't be the only one who does carrier ops in weather other than CAVOK high noon.... OVCRA3.trk

Would be nice to have it consistent with the current system on the Viper and Hornet, where the head is invisible within reasonable constraints, but appears once the camera position is well outside normal movement range.

I suppose you could scribble in the coords of the markpoint then overwrite one of your 1~24 points (assuming 25 is Bullsey; might want to keep that one).

Can the TGP be slaved to OA points? I've only ever used them for pre-planned pop-up symbology so far and don't recall any systems slaving to them.

IIRC External wing tanks should be CATIII, so I leave it in CATIII and just punch the master caution to reset.

The way my dumb butt would probably do it is put the TGP on that reference point, then fly within 5nm of that reference point and look out the window, then draw a mental circle about that distance around the reference point. If I have a bearing as well, I would set the course line on the HSI and overfly the actual target to get a visual reference, and perhaps an OFLY markpoint, but OFLY markpoints in DCS always seem to be off by a few miles.

Go into cockpit view, press ESC, go to an external view, press Resume. It will hide the wheel from external views, but if you go back to the cockpit it will pop up again.

With the last couple of updates I noticed that the ED modules have player's head movements recorded and played back during replays, and the pilot model head appears once the camera reaches a certain distance from the neutral head position, making for fun GoPro style footage with a moving pilot instead of a statue. I know the Phantom has a "selfie mode," but that requires extra keybinds, while the ED method uses the standard F1 cockpit view with no need to map more keybinds or enter any kind of special mode. It would be great if we can get the ED-style, no-extra-keybinding method in the F-14 (and all 3rd Party modules, really) too.

Do you launch DCS from the new launcher? If so, it keeps enabling Easy comms by default.

I have a suspicion that canopy shape affects the visibility as well. The Tomcat with it's thick front canopy glass likes to cause raindrops to pool while at landing speeds, which makes rainy carrier traps a bit more nerve-racking than usual.

It does. Look at your wings. The rain effects are hard to notice unless you have some kind of near "object" to see the distortion, like your wings, a cloud, etc. Note raindrop distortion on leading edge, missiles, nose, horizon. In video you can see individual drops moving. Visibility/shape depends on airspeed.

The gunner export lua and dll?

Published SOP for Andersen IFR when carrying external ordnance (most of us probably do in DCS) is depart 06R/L arrive 24R/L regardless of wind. Fortunately 24R/L ILS always works. I can't find this restriction for VFR, but I follow it anyway to avoid the massive FPS issues on the 06R/L approach.

*cries in curved taxiways*

That's also what I've been doing, at least with Mk81/82 slicks and high-angle dives. For anything else I use the calculator.

Last I recall I had to re-input one of the entry fields for the coefficient to populate if I selected the weapon.

I play on Quest 2, wired, and frequently have connection issues every 20~30 minutes or so while flying. Long freeze/stutter in the headset, as if the connection is lost breifly for about 2 seconds, then back to normal.

Two potential issues: 1. Drag coefficient was still 0 in the bombing calculator. 2. You didn't fly the reticle bank indicators for release (they showed your wings banked right instead of staying level).

Where was it reported? I don't see any threads and it wasn't listed in known issues on the changelog.

purple.trk