not a bug ATFLIR - Is this a bug or just me ?

[ShaunX]

I have a waypoint set at the start of a road I know an enemy convoy will be travelling along.

 

I un-stow the ATFLIR camera and then undesignate twice again for snowplow mode

 

With the HSI I select the waypoint and WPSDG to designate the waypoint. Targeting point automatically slews to the waypoint and shows the designated target diamond.

 

So far so good.

 

Now, although Chuck's guide states that I can now use the TDC to slew the targeting pod reticle, that doesn't work and the cursor is fixed at that waypoint.

 

I castle once towards the FLIR DDI to enter Area Track mode. Now I can slew the cursor with the TDC.

 

I carefully trace the path of the road until I find the moving convoy, place the cursor over the lead vehicle, and castle again towards the FLIR DDI to enter Auto Track mode. Arrrhhh! The targetting cursor pings back to the originally designated waypoint and now I'm cursing at the cursor !

 

Am I missing something ?

[Frederf]

Double undesignate enters both VVSL and then again to enter a mode that doesn't have an explicit name. It's "OPR" but a stabilized vector at infinite distance. I'm going to call the FLIR states: slaved, INR/direction, INR/point, SCENE, and AUTO. What you're calling "snowplow" I'm referring to as INR/direction. I'm going to use sensor control switch (SCS) to mean castle.

 

From slaved (WPDSG) state you have three options to have a slewable FLIR picture

1. With FLIR selected, TDC depress to command a new FLIR target designation. It will be essentially at the previous slaved waypoint since FLIR LOS was already pointed at it. Mode will switch from slaved to INR/point.
2. With or without FLIR selected, undesignate x2 to enter INR/direction. FLIR will drift off waypoint since FLIR is fixed in direction. Slewing (with FLIR diamond'd) is then possible in this INR/direction state.
3. With FLIR selected, SCS right for SCENE.

The reason that the FLIR LOS returns to the waypoint when you use option #3 and cycle through the modes is because the target designation has not been changed and FLIR is still slaved to the waypoint-target in the blank-labeled slaved-to-target mode. As long as you TDC depress while in SCENE or AUTO (or INR) before you SCS right rotary back to the slaved-to-waypoint mode then FLIR will remain as you rotary through the INR/SCENE/AUTO modes.

 

So try the following:

• WPDSG
• SCS right once (or twice) to scene (or auto)
• slew
• TDC depress
• slew
• SCS right twice (or once) to return to blank/INR

Omitting the step "TDC depress" has behavior that advancing past AUTO in the rotary selection will cause the FLIR to resume the slaved-to-target-waypoint behavior.

[Jenson]

I think in Chuck's guide, it refers to lightning pod instead of ATFLIR, I read the old version and no idea if it has ATFLIR in the latest update. 

 

After WPSDG a waypoint, if you want to move the ATFLIR crosshair, press undesignate button to enter "snowplow" mode then quickly press TDC depress to lock current aiming point, then it's free to slew the crosshair now. 

Edited September 10, 2021 by Jenson

[ShaunX]

6 hours ago, Frederf said:

Double undesignate enters both VVSL and then again to enter a mode that doesn't have an explicit name. It's "OPR" but a stabilized vector at infinite distance. I'm going to call the FLIR states: slaved, INR/direction, INR/point, SCENE, and AUTO. What you're calling "snowplow" I'm referring to as INR/direction. I'm going to use sensor control switch (SCS) to mean castle.

 

From slaved (WPDSG) state you have three options to have a slewable FLIR picture

1. With FLIR selected, TDC depress to command a new FLIR target designation. It will be essentially at the previous slaved waypoint since FLIR LOS was already pointed at it. Mode will switch from slaved to INR/point.
2. With or without FLIR selected, undesignate x2 to enter INR/direction. FLIR will drift off waypoint since FLIR is fixed in direction. Slewing (with FLIR diamond'd) is then possible in this INR/direction state.
3. With FLIR selected, SCS right for SCENE.

The reason that the FLIR LOS returns to the waypoint when you use option #3 and cycle through the modes is because the target designation has not been changed and FLIR is still slaved to the waypoint-target in the blank-labeled slaved-to-target mode. As long as you TDC depress while in SCENE or AUTO (or INR) before you SCS right rotary back to the slaved-to-waypoint mode then FLIR will remain as you rotary through the INR/SCENE/AUTO modes.

 

So try the following:

• WPDSG
• SCS right once (or twice) to scene (or auto)
• slew
• TDC depress
• slew
• SCS right twice (or once) to return to blank/INR

Omitting the step "TDC depress" has behavior that advancing past AUTO in the rotary selection will cause the FLIR to resume the slaved-to-target-waypoint behavior.

 

Just tested your solution this morning and it works perfectly. I really appreciate the detailed explanation and feel like I've got full control of the ATFLIR now.

 

Thank you Sir !!!

 

We could do with that explanation in Chuck's guide

 

 

 

[CarbonFox]

Sorry to hijack the thread but is there a way to get the ATFLIR to return to forward looking position like in the A-10C with the china hat switch?

[Tholozor]

40 minutes ago, CarbonFox said:

Sorry to hijack the thread but is there a way to get the ATFLIR to return to forward looking position like in the A-10C with the china hat switch?

Undesignate to go to "snowplow" or double-press Undesignate to go to VVSLV.

[CBStu]

WOW this thread blows my mind. I thought I had the FLIR kind of figured out and then I started a new campaign and I 'think' it is using ATFLIR now. Which is driving me crazy. It reminds me of Photoshop which is tremendously capable but so dang complex one needs a class to make any use of it. It also reminds me of the old saying, I don't need to know how to build a clock, I just asked what time it is. Eventually I hope I will gain some minimal skill w/ ATFLIR  and then I hope to he11 they don't update it w/ XXFLIR. Oh, and regarding the buttons along the sides of the screen, why do they tell me which mode I am in now rather than what mode that button would switch me too if pressed. I can see on the screen what mode I am in now. It would make things a lot easier if the button were labeled for what it will switch to.