DSplayer

Yep, the Mk49 does track the SA-6's TR just fine. I sort of poorly worded it, but I was discussing how and why the Mk37 was able to track all 3 SAM sites (SA-2, 3, and 6) in their experience but using the Mk49 variants couldn't track all 3 sites (Mk37 is able to track all 3 sites' search radars but the Mk49s are only able to track all 3 sites' track radars).

Considering what's happening, I believe you're targeting the Flat Face search radar (listed as FF in the tables) that can be used by SA-2, SA-3, and SA-5 sites. This radar can only be targeted by the Mk37. If you're trying to target the SA-2 Fan Song tracking radar, you have a choice of Mk 22, Mk 25, and Mk 50 (these seekers provide tone and needles and track against the SA-2 TR). Track radars would have to illuminate the general region where the Shrike is flying. The radars in the parentheses on the tables provide tone and needles as well as track, while the ones that only have the radar listed without the parentheses track without tone and needles. In practice, the ones where the missiles don't provide tone and needles should be ignored when trying to target a SAM site. I listed them in case people would like to know why the missile tracked some target they weren't intending to hit. Feel free to post a short singleplayer track if you're having trouble. Unfortunately, the Shrike is very much WIP, and that will cause things like that to happen.

The F-4's manual has a great resource with the seeker heads that track and provide tone for each SAM radar in-game (https://f4.manuals.heatblur.se/stores/air_to_ground/missiles/shrike.html#seeker-heads). In terms of MP performance, you kind of have to be sure the SAM site is illuminating the rough area where the missile is traveling or else it won't track due to the lack of DCS sidelobe modelling.

I don't think your current computer would be unable to run the MT threaded version of the game. What happens when you try running the MT version?

I believe the reason why only one of the two Shrikes tracking the SA-6 is due to the 2nd missile being just flying high enough over the target relative to the radar beam of the SA-6 for it to not track. The reason why the Mk49 Mod 0 and Mod 1 give tone based on the SA-6 search radar (and thus give the associated search pattern period) is because it also gives tone against the search radar even though they don't track the search radar. If you do engage the tracking radar, however, you'll get a constant tone. This incongruence between what tracks and what gives tone is because HB has their own radar frequency values and ED has their own radar frequency values for each radar. Right now some radars, like the SA-6 SR don't have the same frequency/band so you'll get tone against it with the Mk49s even though it won't track. These issues have all been reported already. Until it gets fixed, the current Shrike table in the manual provides what radars the Shrike tracks against with and without tone.

Did you run a repair/verify game file integrity?

I mean this situation is just the seeker switching targets to track the flares and not the helicopter anymore. It's entirely within the realm of possibility, especially with non-imaging infrared seekers like the 9X.

I think this would be better reported in the Weapon Bugs section but I think this is normal behavior considering you're engaging an Apache in the front aspect.

Does this still occur with your MFD/cockpit mod installed?

I gotta preface that I can't speak on how it works 100% within DCS but theoretically, it could provide for certain circumstances like attempting to fire an AIM-9 that hasn't been completely cooled down yet which could cause a reduction in detection range or target obfuscation by the aircraft or some aircraft has some arbitrary limitation on something. There might be more benefits to the current system but there definitely are cons related to it. The missile definitions (such as those within aim9_family.lua) do provide the basic max seeker slew, max trackable target aspect, etc. as a base but I believe aircraft devs don't have to exactly follow this. For example, the detection range for the AIM-9B when mounted on the Mirage F1 was higher than it should be compared to other aircraft.

Rb74 is a direct copy of the AIM-9L rn and since this is prelaunch, it would be on the launch aircraft's side so that indications are provided if the missile can track the target or not. Technically IMO the current way of how it is implemented does allow for more freedom since some aircraft may implement some things differently with how they interact with the missile but it would allow for these bugs and inconsistencies to happen.

Did you try with the latest version of the mod?

Will look into it. Edit: I am unable to notice any corruption of the bombing table.

How will the NLP/ABAs be implemented on this map? Will the center dividers and other preparations required for them to operate as airfields be in place already or will they be normal roads by default?

It's from the 1986 TO 1F-4E-34-1-1 page 1-165. Later in the manual in the Procedures section it doesn't make the distinction that it is DMAS aircraft specific so it does look to be applicable for the AGM-65D on our when mounted on the LAU-88A/A such that it can slave missiles on the same pylon to a common missile LOS.