DSplayer

Try uninstalling them and seeing if this occurs still. It sounds like a mod conflict of some kind that's causing this issue to occur.

Do you have any mods installed?

They're talking about using Loft delivery mode with the LABS and not the WRCS AGM-45 mode.

Module developers, even ED, can't just manifest something out of nowhere. The F-35 that is in service today doesn't even have HARM or AARGM integrated yet. With absolutely no information to work on unlike other instances, ED can't just make the largest assumptions to put the HARM or AARGM on our F-35.

Provide a source for HARM integration into the F-35 with symbology and how it works, thanks.

They discuss the F1 in depth throughout the majority of the video as well as showing WIP images of the F1M cockpit at 2:43-2:47. fausete also discussed F1M development in February in this thread on page 3

The F-4's RWR definitely requires some practice and prior knowledge before hand in order to get the most out of it compared to the F1EE's. Listening to the new guy audio/using Handoff and recognizing what PRF radars have is definitely something people have to do to get the most out of the ALR-46.

Hey guys, I made a website for those who use or want to use Handoff for the ALR-46 but can't remember which radar is which. It has all the radars that are detectable by the ALR-46 and are mostly labeled and sorted nicely. Please keep in mind the site is very much still WIP. The link is included in the manual btw so you guys can also access the link through the ALR-46's page if you want. Here's a link: https://officialdsplayer.github.io/F-4E-RWR-PRF-Library/ Suggestions are welcome for anyone who has found issues or has any ideas on how to improve the site!

Hi, there appears to be an issue with cockpit texture mods in general for all modules (ex: English Cockpit mod for the Mirage F1) that causes them not to work at all so until then, I would wait for a fix or word on something changing. If you don't want to wait, I believe the file structure that I had used is similar (but not the exact same) to the one used in the DCS Root Folder but it would be in some place like Mods/F14/Textures. There you can use OVGME (which I advise since this mod is pretty extensive on what it changes but you would have to modify how the file structure is a little bit), or you can manually install the mod by placing the folder I described earlier and replacing the files there with the ones from my mod.

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?