reported ATFLIR auto & LITENING II point track mode

[AstonMartinDBS]

Even if this problem has already been marked as "correct as is" in this thread, I don't think that this behaviour is correct.

I just can't get a valid lock even though the distance to the targets is far below 8 NM and the contrast is very high - neither in WHOT nor in BHOT.

 

Settings:

• Map: PG
• Date/Time: 21st June 2016, 05:15
• Clouds: High Scattered 3
• Testrun 1 level flight @15k ft, ATFLIR: FA-18C ATFLIR AUTO issue 01.trk
• Testrun 3 level flight @6k ft, ATFLIR: FA-18C ATFLIR AUTO issue 03.trk
• Testrun 4 level flight @6k ft, LITENING II: FA-18C LITENING PTRK issue 01.trk

Edited April 18, 2021 by AstonMartinDBS

[dorianR666]

the 8nm constant is for daytime and 5:15 is considered nighttime i believe. contrast itself has no impact sadly.

[BIGNEWY]

I will ask again, but the last time I checked with the team it was considered correct as is. 

 

thanks

[AstonMartinDBS]

1 hour ago, dorianR666 said:

the 8nm constant is for daytime and 5:15 is considered nighttime i believe.

Even when I was right over the target (< 1 NM), I wasn't able to get a track.

 

1 hour ago, dorianR666 said:

contrast itself has no impact sadly.

I already know this. @Harker confirmed it in the other thread.

Edited April 18, 2021 by AstonMartinDBS

[AstonMartinDBS]

Same issue with the LITENING II since 2.7 btw (see attached Track).

 

I can't believe that this is correct, because this would mean, that the TGPs are not useable for tracking moving targets at certain day times...

FA-18C LITENING PTRK issue 01.trk

[dorianR666]

16 minutes ago, AstonMartinDBS said:

Even when I was right over the target (< 1 NM)

i see

well that certainly is sus

[BIGNEWY]

the team have done some work on this for a future patch

 

thanks