Tholozor

Check the behavior in WP 011 03 of the -742 for the LTWS behavior for 15C. - LTWS should be initially boxed. - HAFUs should not be displayed for radar-only MSI trackfiles. - The raw hit or ACQ point cue should be the only indicator for radar-only MSI trackfiles. - HAFUs should be displayed for radar-only MSI trackfiles when under the TDC cursor.

Did you make sure to turn the hardpoint power on for the HTS?

Make sure you put the new DCSDTC.lua in the Saved Games\Scripts folder, I had the same problem; it was running the old script.

Correct as-per the flight manual. The Speed Brake Position Indicator technically has 3 positions: Closed, Open, and Diagonals to indicate there is no electrical power to the indicator.

One thing to also keep in mind is that MagVar changes year-to-year, so the variation may be slightly different depending on the year the mission is set to.

The F10 map uses True, the HUD and aircraft instruments use magnetic.

You can always use cockpit liveries in multiplayer, as it only affects the client. I use a custom one that I made for myself that adjusts the tint of the HUD glass and AoA indexer lights.

Yes, but you use the E-bracket for AoA. The VV and bracket could be on the horizon line and the nose would be up at about 8 degrees on the pitch ladder. You'd be on-speed, but not on glideslope. If you're on-speed and on glideslope, the nose would be at about 5 degrees on the pitch ladder.

It's 8.1 degrees of AoA. On a 3 degree glideslope, the nose itself should be roughly 5 degrees above the horizon line.

Exactly, it looks fine as-is.

So you can simulate how real-world operators train. Luckily we have an option; if you don't want to do it that way, you don't have to.

The fuel slider only reflects the internal tank, ED currently has no system in place to refill the external tanks aside from natural fuel flow or just removing the tanks and putting them back on. For the F-16, you can depressurize the external tanks by opening the AR door and fuel will flow into them naturally.

Each station must be programmed. PP1 on station 2 is not automatically the same as PP1 on station 3, 7 or 8.

The problem isn't the course line, the aircraft symbol is displaced between the HSI and SA pages. It's lower on the SA page compared to the HSI.

I believe it's been reported, I couldn't find any threads saying it was correct as-is:

The ATC script is very old, probably dating back to the original Ka-50 days or even Flanker 2. Eastern aircraft generally are able to use QFE, so the ATC was originally designed with that in mind.

@Mistermann Are you trying to dial the altimeter to read barometric altitude as 0 when on the ground (e.g. set the altimeter to the QFE pressure)? Western aircraft/altimeters aren't designed to use QFE, only QNH. Approach plates are written to use MSL, not AGL.

You shouldn't need to use an external calculator to obtain the QNH, it should be provided in the mission briefing in the Weather data block. The calculator you linked also doesn't take atmospheric temperature into account, which does create a disparity between QFE and QNH (i.e. with OAT at 30°C at Groom Lake, QNH at 29.92 changes the QFE to 25.60 instead of 25.46 at 20°C).

Not NITE Hawk necessarily, NAVFLIR functionality came from the AAR-50 Thermal Imaging Navigation Set (TINS) on station 6.

@BIGNEWY I think this thread has outran its course.

The problem exists in the ship damage model, not the Harpoon's payload.

Are you dropping CBU-87 or CBU-97?

The F-16 has a radar altimeter. The power switch for it is on the sensor power panel next to the FCR power switch.

I believe it's this: I believe you can make it go away by switching between TWS and RWS.

@Hell0 What you do depends on a few factors, such as: Has your radar detected the contact yet, or is it a Surveillance/Offboard track? Are you trying to just designate the contact as the Launch & Steering target (L&S) or go hard-lock STT?