Nealius

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

Caucasus no-mod track added: CASE II in what is clearly CASE III visibility. case2.trk

CASE II minimum conditions are defined as 1,000ft ceiling and 5nm visibility. Overcast and Rain 3 preset is marked 3-5km visibility in the METAR, which when converted is 1.6~2.7nm visbility. This precludes CASE II and should be CASE III. With preset Overcast and Rain 3, clouds set 5,577ft, the carrier comms call for CASE II when they should be CASE III. While there are occasional pockets of CASE II weather, by the time an aircraft commences and arrives within 10nm, the carrier is in the soup. Unfortunately CATCC/Airboss does not switch to CASE III when mother enters low vis/rain, forcing the player to do CASE III with no LA lights, no comms after Platform, and an NC LSO grade. CASE II instructed by CATCC: Mother is currently in CASE II weather... However after commence... 3.4nm out: About a mile out, certainly not CASE II with the poor visibility caused by rain and the soup beyond (which we entered right as I trapped): The LA lights weren't even on, so lineup was insane even with ICLS. Good luck doing a visual pattern in CASE II like that. Otherwise I really enjoyed the new rain effects.

Same for Kola, however I cannot get the moving map to work at all. The cross stays on start position despite everything powered on as per checklists.

I don't know if it's a Forrestal issue or global DCS issue, but LA lights don't appear until 0.5nm in night CASE III, making lineup a pain.

Same on the Forrestal and even shore runways. It seems something with the lighting engine across DCS as a whole has reduced visibility, with carriers being hit the worst. With runways I can at least see them from 2nm out, but the carriers I can't see landing area lighting (centerline) until 0.5nm, after calling the ball on a CASE III pass.

Not working here either. I could have sworn I saw somebody have it functioning in VR, but could be misremembering. Works fine in 2D, but in VR, just as Reflected said, I enter click mode but there's no cursor to click with.

I thought this was a localized issue to the supercarrier module but it appears to be a global issue, as it affects Tarawa and Forrestal as well, so elevating it here. At some point during 2.7 we got cockpit illumination from carrier lights. Some time in 2.9, around April perhaps, that cockpit illumination disappeared and now we have black tubs while everything else around us is illuminated. Forrestal: Tarawa:

Right-clicking on the desired screen should take you up to that screen.

And still waltzing through the landing area as aircraft are trapping. Doing a section recovery, the idiot deck crew walk back out to the cats after the second aircraft traps, then when the third aircraft calls the ball they leisurely walk back to the sidelines, fouling the deck. As you trap you end up flying right through them.

Demos will vary based on who's doing it, but the official routine with their parameters (speed, G, altitude, etc.) and descriptions is publically available in AFMAN11-246V1, downloadable direct from USAF e-publications site. Despite it being public and unrestricted I cannot post it directly here since it's post-1980.