[REPORTED]A/A radar cannot STT outside of 30nm OB 2.5.6.54046

[creme_fraiche]

The Hornet radar has trouble locking things up outside of 30nm. Steps to reproduce:

 

1. Attempt to STT lock a hot aspect target from greater than 30nm away

 

Expected result:

STT lock should acquire and hold

 

Actual result:

Radar goes to "MEM" state and eventually drops STT lock.

 

Track is attached.

 

RWS SAM (not sure if this is the name for it) mode can successfully bug a target, and TWS works for launching missiles. Both fail when you try to STT.

 

I tested on both Syria and PG (just in case) and its the same behavior.

radar_syria.trk

Edited September 10, 2020 by creme_fraiche

[Swift.]

I am seeing the same on NTTR too.

 

Edit, seems the range is more like 25NM

[Santi871]

Look at the PRF.

 

Target was detected on HPRF, radar was on a MPRF pass when STT was attempted so it uses MPRF. Target was far outside of MPRF range, so it fails (max MPRF range is/should be 25-30 miles or so).

 

So the bug is that the radar is using the instantenous PRF to acquire STT instead of the PRF the target was detected on. For now, a workaround is avoiding INTL or waiting until the radar is in the PRF the target was detected on then pressing the TDC.

[Wesjet]

I can confirm this as well in a recent multiplayer mission I had two MiG-29s approaching hot at roughly 40nm and the lock failed each time immediately going to MEM and then releasing until I was under 30nm. Due to the timing of my attempts, the first successfully held lock occurred at 26.7nm - so it is somewhere in that range.

[Harker]

Look at the PRF.

 

Target was detected on HPRF, radar was on a MPRF pass when STT was attempted so it uses MPRF. Target was far outside of MPRF range, so it fails (max MPRF range is/should be 25-30 miles or so).

 

So the bug is that the radar is using the instantenous PRF to acquire STT instead of the PRF the target was detected on. For now, a workaround is avoiding INTL or waiting until the radar is in the PRF the target was detected on then pressing the TDC.

I remember seeing this some time ago. Is it it reported and known by the devs? It's a pretty big issue, since it breaks the radar in such a way.

[Santi871]

I remember seeing this some time ago. Is it it reported and known by the devs? It's a pretty big issue, since it breaks the radar in such a way.

 

Yes, I've reported it.

[wilbur81]

Radar 'MEM' Bug?

 

In this track, every time I lock an aircraft (whether with AACQ or TDC depress) the lock goes into 'MEM' and then drops the track rather than holding an STT. Thoughts? I have the latest O.B.

 

RDR MEM.trk

 

Edited October 13, 2020 by wilbur81

[Wesjet]

See if this covers it - previously reported:

 

https://forums.eagle.ru/showthread.php?t=285643

 

Basically if the target is flying towards you and you towards it, switch from Interleaved to High PRF and it should be OK. What can happen is the target is detected under high PRF, but the lock occurs with medium PRF and therefore fails. Manually toggling to high or medium as needed solves some of it, for now.

[wilbur81]

See if this covers it - previously reported:

 

https://forums.eagle.ru/showthread.php?t=285643

 

Basically if the target is flying towards you and you towards it, switch from Interleaved to High PRF and it should be OK. What can happen is the target is detected under high PRF, but the lock occurs with medium PRF and therefore fails. Manually toggling to high or medium as needed solves some of it, for now.

 

Interesting. I'll check that out. Thanks, Tiburtius. :thumbup:

 

** Just checked your thread: That is exactly the behaviour. Thanks for that. Hope they get it fixed soon.

Edited October 13, 2020 by wilbur81