ATFlir Question

[tmansteve]

I hope someone can give me some pointers.

 

I load the flir etc with weapons. I set a waypoint to the ground target and when I set waypoint 1 and then select waypoint designate, the tpod is looking into the sky and I cannot get close to the target and wh3n I eventually find the target, I have to keep adjusting the camera as it moves so quickly past.

 

I have watched so many videos on this (Wags, Reapers etc) and use them but I still find it difficult. If the tpod would stay over the target or close to it, then the rest is no problem.

 

Any help appreciated

Edited July 1, 2021 by tmansteve

[Tholozor]

Did you set a waypoint in the editor or program it manually in the jet?

[ShaunX]

36 minutes ago, tmansteve said:

I hope someone can give me some pointers.

 

I load the flir etc with weapons. I set a waypoint to the ground target and when I set waypoint 1 and then select waypoint designate, the tpod is looking into the sky and I cannot get close to the target and wh3n I eventually find the target, I have to keep adjusting the camera as it moves so quickly past.

 

I have watched so many videos on this (Wags, Reapers etc) and use them but I still find it difficult. If the tpod would stay over the target or close to it, then the rest is no problem.

 

Any help appreciated

 

When you defined the waypoint did you set its altitude correctly? In the mission editor you need to put 0 in the  altitude and dcs will correct it automatically to whatever ground level is at that point. 

[Oozler]

By default DCS makes a waypoint about 6562 feet plus or minus. This means the pod is also looking at that point in space. This can be addressed in the mission editor prior to playing the mission if it is one of your missions. Or one can also use the HSI screen and then go in to DATA on the MFD, scroll to the waypoint number in question and then edit (UFC) the altitude on the fly. If one is unsure of what height to set in this scenario, using the F10 map and putting the pointer over the spot will show you it's height above sea level and you can use that. This is on the fly if you are ever in a mission, but basically, it is nice if the mission maker accounts for a waypoint that is on a target being used as a designator and has set the altitude before hand for all players.

[tmansteve]

Damn it,

 

Thank you so much guys for the info. I set a waypoint on the target but didnt set it to 0. Cannot wait to have another go. Its great to know that someone might have the info that can help you to move leaps and bounds.

 

I hope it all works out

 

Cheers

[Harker]

Damn it,
 
Thank you so much guys for the info. I set a waypoint on the target but didnt set it to 0. Cannot wait to have another go. Its great to know that someone might have the info that can help you to move leaps and bounds.
 
I hope it all works out
 
Cheers

Just to make sure it's clear, the point is to set the waypoint altitude to be equal to the ground elevation.

In the mission editor, this happens automatically if you set the altitude to 0 (it corrects it), but if you're setting up a waypoint in the cockpit, through the HSI->DATA->WP sublevel, you need to enter the correct altitude to match the elevation.

[Brass2-1]

Also, the reason the FLIR is not locking onto a point that you designate may be that it’s not in a stabilized “Track” mode. Bumping the Sensor Control Switch towards whichever DDI the FLIR is displayed on will change the track mode.

 

I recommend Chuck’s guide for visuals on the ATFLIR track mode symbology. 

[tmansteve]

Thanks Harker for the extra info and Brass2-1 will get the latest Chuck guide. This is going to be very interesting.

 

Cheers

[Bearfoot]

Wasn't there a bug where if you WPDSG while TDC is assigned to the ATFLIR, the designation goes crazy? Sky, clouds, random point in the ground, etc.

 

Has this been fixed?

 

Work around is (was?) make sure TDC priority is on some other DDI when pressing WPDESG.

[Harker]

Wasn't there a bug where if you WPDSG while TDC is assigned to the ATFLIR, the designation goes crazy? Sky, clouds, random point in the ground, etc.
 
Has this been fixed?
 
Work around is (was?) make sure TDC priority is on some other DDI when pressing WPDESG.

IIRC this was fixed

[Bearfoot]

4 hours ago, Harker said:

4 hours ago, Bearfoot said:

Wasn't there a bug where if you WPDSG while TDC is assigned to the ATFLIR, the designation goes crazy? Sky, clouds, random point in the ground, etc.
 
Has this been fixed?
 
Work around is (was?) make sure TDC priority is on some other DDI when pressing WPDESG.

IIRC this was fixed

Good to hear. It was such a fuss sometimes.