Thorp

I haven't spent much time using the Lantern, and I will agree it takes a lot of patience. I read somewhere that the Lantern is only effective at 15 miles to the target coordinates. Locking a target vehicle in which a box appears around the target is limited to 10 miles. Lack of camera feed contrast will cause locking issues.

I am a DCS RIO with more than a few flight hours, but I'm still learning the do's and don'ts. Idea A to toggle datalink is an okay idea within reason; it's your call to clear the clutter. But datalink provides accurate information that helps with spacial awareness. It's your call. At least toggle it on periodically as to not be blind-sided by avoidable scenarios. I would say that your idea B, using Pulse Search to identify targets by range on the DDD, is a good idea within certain parameters. You'll certainly have an easier time identifying which targets are closer on the DDD in Pulse Search. When targets are flying in close formation it can be tough to separate them on the DDD and TID and the computer will often combine formation spikes as a single brick (that can look slightly bigger than normal, oddly shaped, or fade as 2 separate bricks). The main issue with Pulse Search is that it does not pin information to the TID (neither does Pulse Doppler) and Half Action drops all information until a target is locked. If targets are 30+ nm away, I find it reasonable to either use RWS because it populates the TID the fastest and you can judge which DDD brick matches the TID formation and see closure on the DDD, or you may have enough time to use TWS Manual/Auto so you can assess and then hook the specific target you want on the TID directly (this is extremely slow). The pilot also benefits from RWS & TWS TID readings if they can take the time to glance. The downside to the Doppler searches (PD, RWS, & TWS) is they can be notched especially when the bandit is trying to defend from the AIM-54 missile you launched at 45-70 nm which should be pitbulling a hot target by the time you reach 30+ nm if you cranked 55-65 degrees after launch. When the targets are hot, notching is not a huge threat because they'll only notch if they are trying to defend and if they do, they'll have to go cold or beam which likely puts you on the advantage. (But this is where my knowledge flounders because if I have 2 cold bandits that are going to nose hot again, they will naturally notch when turning back hot unless I'm in Pulse Search which limits locking to only 1 target anyway). In the instance that you're outnumbered and terribly close to the squadron of bandits, you'll want to either bug out or send missiles to ideally force them on the defensive and off your tail. At 30 nm, AIM-54s can splash but it's not too likely and the bandits get awfully close if not already firing missiles at you before your missiles are close enough to threaten them. TWS Auto will allow guided AIM-54 launches or you can risk bypassing the missile loft for a straight line bore-sight shot by switching to ACM mode in the pilot seat or flipping the switch on the bottom right of the left vertical panel (PH ACT). (Low altitudes drastically reduce the travel distance potential of AIM-54s). Furthermore with TWS hooks, I find switching from a hook to STT is more successful when the STT button is pressed as soon as or shortly after the hooked target is spiked on the DDD. Remember to keep an eye on the TID closure rate and alert the pilot to adjust the flight path to avoid notching, and if the notch is unavoidable switch to P-STT so you don't lose them (only to chaff can they be lost except for terrain occlusion).