Tholozor

The MC-130J variant will have AAR capability. Edit: Sniped!

This may also include the weight of the pod adapter pylon.

Already reported, affects a few different pages:

He's saying "intervisibility," which is just a militaristic way to say "line of sight."

If the INS goes to IFA RDR when the knob is placed in IFA, there is no GPS available (or line of sight to the satellites is blocked), and the aircraft is attempting to perform an in-flight alignment.

Program Files\Eagle Dynamics\DCS World\Mods\aircraft\AH-64D\Doc

If we look at some of the data from this thread, you'll find the existing E-2 in DCS is basically still an E-2C under the hood:

That's LANTIRN.

Already planned:

Different branches, different requirements.

The F-16 uses PDLT instead, it doesn't have the same mechanization as MSI.

Verify the BATT switch was set to MAIN PWR?

A track reply would help us see what exactly you're seeing, but I'm going to go out on a limb and suggest you Cursor Zero?

Work In Progress:

You can create a custom cartridge profile with all your CMDS settings and load it in MP. The 'FILE' option at the top of the DTC menu is actually a button that will allow you to import a user-made profile.

Countermeasures are loaded through the data cartridge function now. Editing the lua is no longer required.

Specifically, aircraft system time since generator power-up, displayed in minutes and seconds (MMSS). Only displays with weight-off-wheels.

Is it the same reticle as this?

Have you tried inverting the brake axes?

AFAIK, the 300ft metric is applicable regarding horizontal position error. ACAL for vertical error provides either GPS-only, DTS-only, or BOTH options for vertical position (BOTH being the default, and the MMC picking whichever of the two is more accurate based on specific parameters). ACAL-provided vertical position error shouldn't ever be more than 100 feet from what I'm reading (unless a system has failed).

Looking at the first screenshot, you forgot to Cursor Zero (denoted by the CZ option on the HSD).

I concur with Razor's findings; in SCAN RAID, the L&S should be centered on the scope, which becomes a 10nmi by 22° field. The max range value is incorrectly adopting the L&S range. The scale of the scope in SCAN RAID scope is correct, just offset by 5.

The frequency is set in the mission editor per unit, the default being 127.5.

Interesting, I thought that had been addressed in this patch: https://www.digitalcombatsimulator.com/en/news/changelog/release/2.9.15.9408/ Maybe the problem is more-so dependent on the amount of wind.

Correct, check the description.lua and ensure the filenames match.