NeedzWD40

@Amarok_73 has done a good job of explaining the why, but I'll try and answer as well.
The PRIMARY box under the PRESET EDIT menu is only an indication as to what the primary radio is for that preset. It simply highlights the radio, frequency, settings, plus puts an arrow next to it. It's for a quick at-a-glance overview of the preset for awareness/coordination. Suffice to say that it's entirely contextual in how/why this functionality is used, and normally in much busier commo environments than we simulate in DCS.

In here, I've edited my first preset to be called A-CHAN and the callsign to be ACH. In addition, I've replaced all the frequencies with custom ones. The PRIMARY is still VHF for that preset, thus VHF is highlighted and arrowed. However, I've gone through the top row for each radio and tuned them to the frequency in the preset, which is indicated under the left side with V U 1 2 H. This all means that right now, all my radios are tuned to the first preset as indicated. Unless I tune the radios differently (EUFD, COM preset, COM manual setting), they'll stay on that frequency until changed -- there's no deleting of a radio from a preset.
This is entirely an organizational thing: Instead of PRESET 1 I might instead call it BDE HQ, whereupon the frequencies preset are all the available frequencies that brigade headquarters is on, but the primary might be the VHF radio. I might have PRESET 2 as my inter-flight frequencies, where FM1 is the primary radio used, and so on. The idea is that instead of punching in numbers to tune radios each time, you simply select a preset for a known party (ie JTAC), select their primary radio, then select the appropriate mode. This applies whether you're speaking of datalinks or commo. The PRIMARY just makes a fancy highlight so you don't end up calling Juan's Taco Joint for a fire mission because you selected FM2 instead of FM1.
The second half is the EUFD, where the DL rocker comes into play. All five radios can be used for the datalink and each crewmember can independently select a radio for the datalink. Your crewstation is an open box indicator, while the other crewstation is a diamond. For example, the pilot can use the VHF radio to send a datalink message to brigade, while the gunner can use FM1 to send a datalink target to nearby flight members.
TL;DR: Presets are just a way to tune radios for both commo and datalink. Select your preset, select your radio, select mode at the bottom, and voila: radio tuned to that frequency. Use EUFD DL rocker to select radio for datalink, RTS to select for commo.

Behavior in this track: Friendly unit is lasing on code 1688. Take off, then arm and press MSL on WPN page. SKR will not work; displayed in white and with a ?, indicating an invalid condition. Deselect missiles on page, WAS missiles instead, seeker acquires. SKR becomes valid ACQ source and is operable and selectable. Set self code to B, bring up George interface, get him to a different target, lase. Missile mode to RIPL. Fire first missile, then next missile goes live and ACQ cross goes to second missile SKR source. Fire. De-WAS missiles, SKR no longer valid and displays SKR? in ACQ box.
ETA: Checked my references and this is correct behavior. If the missiles are not actively tracking (WAS'd, valid laser source), then SKR cannot be a valid ACQ source.

AH-64D ACQ SKR.trk

What's your burst setting set to?

FCR data is invalid as a sight. It has no targets detected (or another invalid data state, like position too far from C-SCAN initial position) and therefore cannot provide ranging or positional information for weaponry.

I don't recall if it's a specific wishlist item, but a similar tab as other aircraft have (Ka-50, A-10C, F-15E) for control measures/points/targets is something I've inquired about before. We'd need a function to disable or modify the automatic target/control measure mechanic currently in place as that eats up the entire table(s).

You must sight select FCR before using AGM-114L.

A group that has "On Road" routes have a section in the mission file called spans that detail each line on the path along the road, illustrating where the group is going. It serves no purpose in the game, only the editor. If there are many groups with lots of on-road routes (and conversely, lots of spans), you can overflow the mission file which leads to it not loading and giving you errors.
 

Have you checked the Core Spawn documentation and demo missions? I don't use MOOSE so I only know how to do it via the vanilla scripting mechanics.

Yes, this is correct. It's why the RFHO is a powerful tool: one aircraft with an FCR can scout ahead and find targets within that 6km limit, then pass that data to friendly aircraft further away. The T-90's ATGM is maxed out at ~5km while the BMP-2 is about 4.5km. Neither should be a large threat with the appropriate strategy and planning.
This will still be possible. The difference is you're intended to be doing it as part of a team, not lone-wolfing it.

Check and ensure that game flight model isn't turned on.

Try turning on Unrestricted Satnav in the mission options.

There's still a chance that the missile won't lock onto the intended target, depending on what the seeker grabs (which can get into complex sub modes that I won't go into here). If vehicles are moving close together, it might grab a vehicle in front or behind the target indicated by TADS. Currently the problem is a bit exacerbated by excessive INU drift, but even if your INU is under a fresh reset state, it's still a potential issue depending on target separation.

You can either lase way off in the distance to max out the range or set a long manual range to slow the rate down. Narrower FOV and long range setting will slow down slew rate considerably, while wider FOV and closer range setting will be much faster. Further, if you aren't already, use the first lasing detent for a pulse or tap the second detent and don't continually lase until you need designation to keep the slew rate from bouncing out of control.

Check the A-10C II manual, page 783 (or A-10C manual, page 646). It has a breakdown of how DCS JTAC works.

It looks like the CPG was set to NVS FIXED, making TADS unavailable as an acquisition source.

According to the creator, yes with some caveats:
 

What? You've got it all wrong! Here:

Sight select TADS first, then you can toggle between SAL and RF.

Have you tried one of the rotaries on the throttle?

My guess is that we won't be seeing any new rocket types until a suitable solution for handling rocket zones is implemented. According to the mini-updates, the M274 is intended for now, with additional warheads later.
 

George now defaults to only using the laser. Use AI helper short press left to cycle his weapons.

If as the pilot: it won't be possible to action the RF missiles until the FCR or datalink are in place. You will have to rely on George/CPG to shoot the RF missiles.
If as the CPG: Sight select TADS, then action missiles, then on the WPN page, select where it says "TYPE" to toggle between RF and SAL missiles.

First column is frequency callsign; second column is cipher, crypto variable, and power.

SAL HELLFIRE requires a terminal designation that must be held until impact, but it isn't required for the entire duration unless launching in LOBL. That's why without an initial lase, you get a "Lase" message on the HMD, indicating that laser energy should be on by that point for missile acquisition. There are nuances that aren't reflected in the game, particularly the advantages of the 114K we have modeled, but those are negligible within the current iteration.
If you launch with laser energy detected by the missile (LOBL), then you must maintain the laser for the duration of flight. Otherwise, LOAL will allow you to only lase in terminal. Technically speaking, even with LOBL, the missile should reacquire, but I've found this to be spotty at best.
TL;DR: Yes, George must stay on target until the missile impacts as he will shut the laser off when you ask him to scan again.

I believe it's linked to the TSD autopage functionality. The default setting is "search" so anytime a searching radar is detected, it's supposed to autopage up the TSD. I don't know if the alternate settings work yet or not, but you can find them under the TSD UTIL menu.