Tholozor

Per title, 'TRIM' no longer appears on the ADV line while the T/O TRIM button is held and the stabs reach 12° NU. TRIM_ADV_not_present.trk

Partially fixed after today's update. The bearing and range is shifted over, but the AACQ legend still overlaps with the symbol denoting the Bullseye is out of the scope of the tactical region.

For some additional context, the following example (VFA-136, 2004 on CVN-72) shows the console backlighting is definitely green when the cockpit lighting is not in the DAY position (evidenced by the IFEI lighting being green). I am unaware whether or not the console backlighting is capable of more than one color, or simply has on/off states.

In addition, the same is also true for HARMs.

TACAN will show DME information for VOR/DME (or DME-only) stations on their paired frequency. Most notably, the VOR/DME station at Beirut (KAD) on the Syria map is paired to 73X. A track will help see if the behavior you're describing is intentional.

A track would be helpful here. TWS has restrictions in place depending on the bar scan and azimuth setting. - 6B: Only 20­° azimuth is available. - 4B: 20° or 40° in azimuth are available. - 2B: 20°, 40°, 60° or 80° in azimuth are available.

@SickSidewinder9 Full explanation here:

TMS Down will only perform CZ if the TGP is SOI and is in SLAVE mode.

Looking at the track and testing it myself I've boiled it down to a simple description: - A/A weapon SET parameters cannot be invoked in RWS if L&S is present. STT/RSET logic doesn't matter either, a track can be designated L&S in RWS and it will prevent SET parameters from being invoked with WSS. If the trackfile ages out (e.g. removing the L&S), WSS parameter invoking returns. I can't find relevant information in the manual that definitively explains the logic to support one way or the other, so if it's a bug or correct is outside my knowledge unless an SME chimes in with more info.

Already reported:

It was a little difficult to understand exactly what it was you were trying to convey in the original post, thank you for the clarification! May need a track file to see exactly what conditions are present to see if the behavior is erroneous. ARSA should always be disabled if the range scale was manually adjusted at any point (and re-enabled with RSET), so I'm curious if perhaps it needs to be re-enabled for the SET parameters to invoke when a weapon is selected. I'll take some time and read through the manual and see if I can find something definitive.

To my understanding: - Subsequent presses of the Weapon Select Switch towards a weapon already selected will only step the active station on the aircraft, and will not re-invoke the SET parameters. - Dropping STT on a contact does not remove its designation (L&S). - If the ATTK format range scale has been adjusted manually; Automatic Range Scale Adjustment (ARSA) will be disabled unless the radar goes into STT, or RSET is pressed. - Automatic Range Scale Adjustment should only be active in STT (also TWS, but can only increment the scale). - If RSET is pressed with no target in STT, L&S designation is removed and ARSA is re-enabled.

Not something that players can do at this time.

TOI? You mean SPI? (Sensor-Point of Interest)

Was that video recorded from a cold start or a hot start?

My personal preferences: NAV (HUD option on EW page boxed prior to fence-in) LDDI: HUD or ADI (depending on day or night), FPAS (for transition from climb to cruise), or STORES (if I need to do additional weapon configuration after establishing cruise) RDDI: ATTK (generally 6B on HPRF at 80nmi for airspace sanitation, situational) MPCD: HSI or SA (usually HSI through climb phase and switching to SA after establishing cruise) A/A (HUD option on EW page always boxed) LDDI: AZ/EL (sometimes FLIR) RDDI: ATTK (usually no more than 4B, usually INTL but MPRF at 20nmi and below) MPCD: SA A/G (HUD option on EW page always boxed) LDDI: STORES or weapon display, sometimes FLIR (especially if mission is anti-shipping for VID) RDDI: ATTK or FLIR MPCD: SA or HSI AAR (HUD option on EW page unboxed for declutter) LDDI: HUD or FUEL RDDI: ATTK (for easy actuation of SIL option) MPCD: HSI (for ground speed readout)

It's not that there's a physical stop that prevents the wing fold handle from being pushed in before the wings are spread (the manual specifies that nothing prevents you from doing so), it just warns you that you should wait before pushing it in, or else the wing fold transmission will be damaged. If anything, this should be a Wishlist item as part of the damage model.

- "Platform" should be called when passing through 5000 feet to follow DATA directions for airspeed and descent rate down to 1200 feet. - Improper landing configuration: flaps must be set to FULL for proper approach. Aircraft is also too heavy (gross weight should be 33,000 pounds or below). Aircraft should be fully configured and on-speed by 6 miles (regardless of ATC or CPL settings). - After the first usage of CPL fails (see above), the aircraft drops into CSS ('A/P' advisory on the left DDI), use Paddle switch to disengage.

The 'A/P' advisory also tells me you still have CSS autopilot mode engaged. Ensure to pull the paddle switch to disengage all autopilot modes before setting the aircraft for landing configuration, or the aircraft will fight itself.

AFAIK, S-J is considered its own Master Mode like NAV, A/G or A/A, and has its own configuration for displays.

CZ is available on the FCR.

The Hornet (along with most U.S. fighters) doesn't have acceleration cues in the aircraft. IRL, tankers have recommended airspeeds based on the aircraft they intend to refuel, and the receiving aircraft generally follow specific closure rates based on that airspeed. In the case of the Hornet, the recommended closure rate is 2 knots above the tanker's airspeed (for the KC-135, the recommended airspeed range for refueling Hornets is 200 to 275 knots).

The guidance control unit code select panel on GBU-24 should permit the first digit being 1 or 2 (the second basically never used), and the three remaining digits can be 1-8, so 1111 is a valid code for Paveway III, but not Paveway II.

It was added in this patch: https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.9.0.46801/