Recluse

OK. The trick is to transfer the SOI from RADAR to FLIR once the RADAR has you on the movers. YES it is a PITA, but it can be done relatively smoothly with manipulation of SCS and SLEW Here's a quick TRK I just recorded...not from that mission. Did you mean DESERT CONVOYS? I couldn't find CONVOY HUNTER I will try that mission and see if I can get a TRK/Video. In this TRK, I transferred the SOI from RADAR to FLIR and switched targets in the Convoy by slewing the FLIR out, going to PTRK and capturing another vehicle. Once the FLIR is SOI, you can repeat as necessary. I took a quick look at DESERT CONVOYS, and it is true you don't have the luxury of a lot of time to mess with this. OOPS... I re-watched, and the FLIR snapped back to the initial target vehicle instead of capturing a new one. Have to mess with it some more.. GMT_FLIR_AGM65F.trk

When you designate the convoy on the GMT, and you load up the FLIR, you should see it slaved to and tracking ONE of the vehicles which you can then prosecute with AGM-65F. Gets more complicated with Laser weapons as you need to HANDOFF to the FLIR, which is where the issues come in. But you should easily be able to attack a vehicle directly from GMT lock.

Use the GMT Radar, Luke!

Yes, but ALSO the coordinates the JTAC gives you are USUALLY not a SPECIFIC TARGET but the general area where there may be multiple vehicles, so even if he gives it to you in PRECISE format (which that MOD allowed), you still can't really blindly drop a JDAM on the PP coordinates.

This is a mod that I once used to make the JTAC give you the COORDS in a format suitable for JDAM (or PRECISE waypoints) but as mentioned, it probably isn't too useful for PP attacks. This was from back when JTAC only gave GRIDS, so it probably isn't needed now, if it even still works..

JTAC coordinates are RARELY directly on the target, so it would be best NOT to try PP mode, so YES it is preferable to find the target and use TOO mode. You can create a Waypoint from the JTAC coords to get you close, then slave the TPOD to it to search for the specific target. One of many tutorials on entering WPS. Of course, we can also enter GRID coordinates now.

OK. I just tried and all was fine. I didn't need the WP INC as I used a WP Desg as the initial target point, then slewed the pod so the EHSD already had it. Keeping the TPOD/LASER on the target throughout, or at least in the terminal phase is key.

OOPS Posted while you were posting. Save a TRK file and we can see what is going wrong possibly. Just released: I haven't tried yet. The need for WP INC LONG to feed coordinates to the INS before pressing DESG is new. Wasn't necessary before

YES that one. It is too far down. It should be co-located with the Bar on the Left side more or less, or else the radar is pointing almost straight down (or as far as GIMBAL limits allow). Look at the position of the caret in the screenshot where Contacts are showing up.

Check your Radar Elevation. I can't zoom in enough on the screenshots, but I don't think I see the caret on your blank radar screen, but I see it when there are contacts. Maybe you diddled the FLIR with the Antenna Elevation knob and got the Radar Elevation messed up. It happens. Ask me how I know

Ohhhhh that stinks!! I guess i should have tried it

Laser Designator is 2nd Detent IIRC. So if you are using that for the PICKLE it may interfere, on the OTHER HAND, since you are using it to release the weapon, then just HOLDING IT DOWN might be even easier than trying to juggle two buttons!

They are investigating according to the BUG REPORT tag. Many people have this issue. Meanwhile, you can use Manual Lasing. Box the TRIG box on the FLIR and hold the TRIGGER down until Maverick Impact. The laser will fire as long as you hold the Trigger (unless they changed something in 2.7 for this too). I haven't tried manual lasing in 2.7 but it should work for BOTH ATFLIR and LITENING. You could also just load up the current STABLE version of 2.6 and all will work fine (of course no ATFLIR and you lose the other enhancements to 2.7)

Hmmm.. I haven't seen this. I usually flip the LTD/R switch immediately upon setting the PRF Code and enabling the TPOD. I haven't noticed the countdown starting until I pickle. I also only seem to see the short laser timeout with the ATFLIR and the Litening seems to work OK. Possible there are other variables that affect our respective observations. Either way, I think it is a definite issue with AGM-65E. I think the problem doesn't exist with GBU because the flight time is generally shorter and the Laser doesn't even start firing until the terminal phase, so we might not notice a short laser timeout.

It definitely does. Steps and video page stays up so you can prosecute another target. As long as you have multiple Mavericks of the same type. It won't auto switch from an F to an E for example.

In a recent Video by RedKite, he said that the ATFLIR is used for Carrier based aircraft because it is rated for the stress of Carrier Landings, while the Litening is used for Land Based Marine Hornets.

Thanks!!! Looking forward to crashing touching down light as a feather on the new FCLP object

YES to your point about IMMEDIATELY SCS Right to SCENE TRACK. This is what I do. In most cases, I don't even bother to Undesignate, I just SLEW and re-designate. Only exception is if I want to use the MAVERICK seeker to fine tune a lock that isn't quite snapping to the point on the FLIR. In that case, UNDESIGNATE allows the Maverick sensor to be moved independently. (At least ONCE while it remains Ground Stabilized) But in WAGS' video on the ATFLIR, he initially does a TDC Depress (and HOLD, I believe) to SLEW in INR MODE. In the current implementation, under those conditions, more often than not, the FLIR aim point drifts all over, so I always go to SCENE

Just tried it. Not sure now since there is also the DRIFT bug that makes the INR mode drift all over the place rather than stay put as in Wags' video. I undesignate and it started drifting. Not following the VV, not SNWPLW, just drifting, so I don't know.

I believe I have noticed that the ATFLIR will REMAIN ground stabilized when you Undesignate rather than the Litening pod which goes to Snowplow. (Litening USED to do this) Target lock breaks but the pod stays looking at the spot. Not sure if this is AS INTENDED or an accident to be remedied. Have to try it in case I am not remembering correctly.

Have a look at this thread: One thing you should also consider is using the GMT for the initial lock For AGM-65F, it seems to work (for me) just fine with GMT only since the range is sufficient to be inside Radar Gimbal limits. For Laser weapons where you need to get closer, you have to hand off to the FLIR so it becomes the active sensor with it's larger GIMBAL limits. In my very limited experience, it seems the ATFLIR does a better job than the LItening at getting Point (AUTO) tracks. With either pod you need to slightly LEAD the target when in POINT/AUTO track modes. GMT Radar works much better and Faster, and it gets the FLIR on target if you DO want to switch sensors.

Not to steal imacken's thunder, but I also see this. Track Attached. - Initial WP Designation: DIAMOND shows up. -SLEW to another target, TDC DEPRESS. No Diamond -SSS RIght to AREA track. SSS Right to Point TRACK SSS RIGHT to go back to Inertial, NOW I see the diamond, but it wasn't there on initial TDC depress. -SLEW to another target, TDC DEPRESS, NO diamond Video also. Sorry the Voice-over is very faint.. but it follows the bullet points above. LItening_noDiamond.trk

Thanks for the confirmation. Interestingly, the Litening has been behaving for me CONSISTENTLY at all ranges while the ATFLIR is not. (TRK included in my Bug Report )

Finding issues (bug report submitted) with the ATFLIR and AGM-65E, When fired with an IN RANGE cue and longer distances, the Laser countdown ends while the missile is still in flight causing to to go stupid and fall short. Also encountered a bug (reported by someone else) where INR mode drifts around, but SCENE TRACK works for the same purpose. Other than that I think the ATFLIR works better with moving targets and seems to work better in conjunction with the AG Radar.

AGM-65E self lasing from the aircraft has been a feature of the DCS F/A-18 since the introduction of the Targeting pod. At first it required using the TRIG to manually lase. Auto Lasing by using or holding the Pickle button came a bit later. It has worked more or less fine since then and the IN RANGE cue has always been relatively accurate regarding the missile range when the missile is initially cued to the target designation. AGM-65E generally had better range than the AGM-65F (in DCS anyway) though the laser seemed to be capped at 8 miles. Nonetheless, when the AGM-65E laser seeker goes solid, it means it has picked up and is tracking the laser spot. What is NEW in 2.7 is the countdown timer. As shown, it continues to work fine with the older Litening pod, but with ATFLIR, the laser cuts out too soon. Thanks!!!