Recluse

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!!!

Using ATFLIR and LMAVS. There is now a countdown timer for the laser firing. It seems it times out before the Maverick reaches the target and it falls way short. I have tried it several times. - When IN RANGE cue is achieved (about 10 miles) (2.7_lmav1.trk) -MIndful of previous reports that the Laser is only good to 8 miles, I waited until range was 8 miles despite the IN RANGE cue being there. (2.7_lmav2.trk) -Wait a little longer firing at about 7.8 miles. Laser times out while Maverick is still in flight and then the missile falls short. lmav_atflir.trk I realize that the range might actually be shorter, but, in that case there is still a bug with the IN RANGE cue showing up sooner. I tried it with the LItening Pod. Same laser countdown, but the Litening Pod seems to give the laser more time to fire and I got hits at ~10 miles when IN RANGE cue appeared (lmav_litening2) 2.7_lmav2 2.7_lmav1 lmav_atflir.trk lmav_litening2.trk

So, for me, I designate a WP and I see a Diamond in the FLIR. I slew, and, like you, hitting TDC Down doesn't give me a Diamond, but it DOES seem to update the designation. If I go SSS right twice to Point Track, TDC DOWN and then SSS right again, it gives me the Diamond. As I said, though it did SEEM to update the Designation upon SLEW-->TDC DOWN even though the diamond did not show up. At least the AGM-65F snapped to the new point. Interestingly when I did SSS LEFT to the MAVERICK page, the diamond appeared in the FLIR! Agreed it is probably a bug.

I did notice something interesting. I Point Tracked a stationary vehicle and attacked with AGM-65F. Unfortunately, the Maverick decided to lock a neighboring vehicle. After the neighbor was destroyed, the targeted vehicle started to move, and the ATFLIR FOLLOWED IT!! I don't recall the Litening pod doing this, so MAYBE the ATFLIR does have better moving vehicle tracking. I originally locked just out of MAV range ~12-14 miles, fired when in range and pulled off target, so by the time the MOVING vehicle was being tracked it was quite close ~4-5 miles

I haven't tried it yet in 2.7 but since this seems CORRECT AS IS, why does the Changelog for 2.7 say: Not sure what was FIXED...

Did you possibly Declutter? Click the SETUP button and cycle through the options for the COORDS on the top right. I tried it and got the coords, but they didn't show up until the target was in GIMBAL Limits (at least the first time). I designated a WP and didn't see any coordinates until the FLIR was actually able to point at it.

Or if you are just using the FLIR, you have to Lead the ship. Go to POINT TRACK just ahead of the ship and when it sails through the Point Track bars, the FLIR will pick it up and continue to track. NOTE: You may have to do this several times to get the lock. SEA MODE slaving is so much easier, but the GIMBAL limits of the Radar are less than the FLIR so as you get closer (e.g. for a L-GBU drop or L-MAV) you might lose your lock. There are some threads with work-arounds to make the FLIR lock primary. Note: I don't know if 2.7 or the ATFLIR change any of this behavior.

Haven't tried it yet, Just took the Hornet up to gawk at the clouds and try the CPL ASL mode. Will get into the Harrier later and report back. Definitely looking forward to the Tarawa re-texture.

I have a Thrustmaster Cougar...but it is aging. I did put Hall sensors in stick and throttle but my stick springs are getting soft and the throttle friction holds are getting sloppy). Also TM RCS pedals. As mentioned, I have the Nozzle positions on the Antenna rotary of the TQS which is a bit sensitive. I am interested in that potential Sticky Zone! I'll keep practicing. I agree 100% with everything above!!! I will play with those settings. My curvature on pitch and roll is around 15 and my deadzone is higher because my stick has a bit of center wobble. Not sure if it was your mission or not, but I have also been using this mission: https://www.digitalcombatsimulator.com/en/files/3301741/ AV-8B FCLP Trainer - Caucasus (rev 2) for practice, but figured I should get comfortable (!!!!) with the boat. I did see Draken's post to an Assets Pack that more closely recreates the deck for FCLP, but I haven't picked it up yet.

This was sort of the reason for my post. When I get the nozzles >70% I cannot control the witch's hat. TRIM doesn't seem to do it, and stick inputs don't seem to act quickly enough. I have tried doing a hover takeoff and trying to just STAY IN ONE SPOT with the witch's hat on the horizon, but it gets away from me every time. Probably just boils down to practice, but I do not feel like I have any control of attitude in those situations. BTW, I was talking about a curve for the Nozzle position not the throttle so it isn't so easy to overshoot 82 degrees.