Tholozor

This is working as intended. TWS will automatically assign the highest-ranked trackfile as the L&S (note that this is not a lock like STT, only a designation) unless a different trackfile has been designated as L&S. The NWS/Undesignate button on the stick will step the L&S through all valid trackfiles (this function is also present in RWS with LTWS enabled). The only way for L&S to not be present in TWS is for no valid trackfiles to exist.

Cold start or hot start? If cold start, the helmet needs to be aligned.

If you're referring to the Long-Range Laser Lineup System, it should only be visible at night:

The MK option can only be used to create a mark point of the aircraft's current overfly position, or ownship designated TGT position. You'll have to make your own TGT over your ally's TGT.

If I had to guess, the system is only displaying correlated trackfiles or SURV tracks, and not radar-only trackfiles. I don't know if that's correct or not since all trackfiles should be MSI trackfiles, at least in the context of the Hornet itself (SURV tracks may have different logic). Does the same thing happen if you replace the AWACS with a different kind of donator like another Hornet? To answer one of the earlier questions regarding the priority list, number 1 is highest.

The HMD's default range at which it will display HAFU symbols is 35 miles, you can change it from the MIDS SETUP submenu of the HMD page in the lower-right corner.

There was more in-depth discussion in the linked thread, you can find out more there.

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.