Tholozor

Turning the radar altimeter off will remove the low-altitude warnings, but AFAIK it shouldn't disengage CFIT-protection warnings that come from TAWS.

Without a track, we can't know if it's a problem on the sim's side or the user's side.

The datalink pod is only used for man-in-the-loop remote control for weapons like the GBU-15 and AGM-130, it has no functionality regarding aircraft-to-aircraft/Link16 datalink.

This is normal. "Video" pages have their own independent settings. "Text" pages have a shared setting:

Check all the links in the threads provided; RAID/FOV provides no function for Laser Maverick, but it doesn't matter as far as the software is concerned: the weapon pulls priority.

Same as this:

The mission date is set to 1987; GPS is not available. If there is no GPS, the IFA position on the INS knob will command the in-flight alignment procedure instead of AINS.

Not a bug:

Nice, I remember that one from the thread about the faster cursor speed. You can also see there seems to be a spacing between the forward slash and where the hundreds value would be for the bullseye range.

Yea, (gotta love fat-fingering the keypad) and the identifier is also wrong, but ultimately not related to this. PG has a number of NAVAIDs that need corrected according to some IRL navigation charts.

Do you have an additional track? I only see the one.

Already reported in the F-15E forums:

@supanova I watched your track, and I never saw you press ENT on the ICP for LAT or ever dobber select LNG on the DED for the NORM alignment.

Currently, the AACQ legend will overlap with the bullseye-to-cursor readout in the top-left corner of the ATTK display. I found this quite odd, even after seeing documentation showing both in the same area without mentioning any type of swapping/priority logic, so I did a little digging for real-world examples. I found helmet camera footage from the U.S. Hornet East Demo Team (video source) which just so happened to have the ATTK format pulled up. It also has the bullseye-cursor data shifted slightly to the right compared to the position in DCS. Full disclaimer, I am aware the video was taken in 2010, so a later OFP may have changed the position of this data block after the version the DCS version represents. This example was the oldest I could find that had the ATTK format present on a Legacy Bug on video, if anyone has older examples, please feel free to share. Since the DDIs don't display the full raster on a digital recorder, I took various frames and warped them to the same orientation and overlaid them to present a more complete picture of the ATTK format. The out-of-display bullseye symbol can be seen just below the spacing between the bar scan and current bar legends.

Keep in mind that the Caucasus map is roughly representative of the region circa 2008.

Are you able to post a track? Everything works fine on my end.

Check your in-game audio options for what device is set to 'Headphones.' Any audio that would play through the pilot's headset (i.e. radios, cockpit voice alerts, etc.) are played through whatever is set to this device.

These lights only illuminate under specific conditions: RCDR ON should illuminate when the recording system is running (not implemented). DISP should illuminate when the countermeasures are in semi-automatic mode, and ready to dispense with pilot consent. SAM should illuminate when the aircraft is locked by a surface-to-air missile system. AI should illuminate when the aircraft is locked by another aircraft's radar. AAA should illuminate when the aircraft is locked by anti-aircraft artillery (Vulcan, Shilka, etc). CW should illuminate when the aircraft is painted by a radar in continuous wave (usually a type of missile guidance). You can also verify the lights will illuminate with the Lights Test switch.

This is actually a recent correction of an old bug. TACAN channels will now show distance to DME stations on their paired frequency. It just so happens that channel 107X is paired with the VOR frequency 116.00MHz, which just so happens to also be the VOR/DME frequency at Damascus.

The coordinates on the aerodrome data don't correspond to the centerpoint of the runway, they correspond to the approximate foot of the runway (in your example, the foot of runway 25).

The first time GBU-24 is equipped and utilized by the aircraft, it will behave normally (weapon release initiates IN ZONE when the ball intersects the VV, and LTD/R is automatic). After rearming GBU-24s (track uses unlimited ammo to demonstrate, but the issue also manifests when rearming via ground crew), the following will happen: - IN ZONE cue is ignored, and will drop immediately when weapon release is pressed. - LTD/R will not automatically fire. - LAR zone is not displayed on the HSI. GBU-24_second_release.trk

Removed.

If the pilot depresses the RAID/FOV switch prior to entering TWS (and while an L&S exists prior to TWS), the radar will enter SCAN RAID immediately upon entering TWS. SCAN RAID should only able to be engaged if the radar is already operating in TWS with an L&S present. SCAN_RAID_primed.trk

One of the latest updates made TACAN able to receive distance information from paired-frequency stations. Depending on what navigation aid stations are present on the map, some TACAN channels may conflict.

FLIR is an infrared sensor system, which would be immensely helpful looking for people at night.