thats true
to have an example:
the target to the left of the radar scope will be constantly updated
which it probably shouldnt at all, since iam using a small scan zone and am prioritising the two targets on the right
3 Likes
How long does it remain visible, because if im not mistaken, it should remain for a few seconds (up to 8 maybe?) because of IOG tracking (or whatever its called)
how about su30sm2 more crazy can see the target of azz
no the Su-30SM2 cant do that
indefinetly
becasue its updated by TWS ESA, exactly like on the AESA EF
it can, I have that’s why I knew it
I mean wouldn’t that just be “track outside scan volume” ?
Physically speaking, nothing really prevents it…
then replicate what i have done in the gripen
what he’s saying is that it shouldn’t update instantaneous outside of the ±70 degree zone which is fair.
It should be more like a mech scan tws where it just predicts the targets velocity for a certain amount of time b4 it gets updated again
On his Gripen example it doesn’t seem to ?
Or am i missing something ?
that wont give you the 10 updates per second (or whatever it was for TWS ESA)
so even then its overperforming
and as a result you would either get slower updates on all your targets or if you want you only want to have prio on some targets then it wouldnt update at all
1 Like
Gaijin have nerfed the scan rate of all the search modes to account for the time it takes the dish to rotate and do track updates outside the search zone. It there’s no a perfect representation of real life, but it is kind of close.
1 Like
that dosent matter once the target is detected
it will just get constant updates through TWS ESA after that
if they wanted to do that they would have to reduce the ammounts of updates TWS ESA provides for the EF and gripen
Yeah, the track update rate is higher than it should be in that regard. However, in real life the antenna can quickly rotate to update tracks and return to the scan pattern. Gaijin can’t model that properly so rather than interrupting the scan pattern they have just reduced the scan rate so that it roughly equals the average scan rate with interruptions.
that one target on the left will get constant updates
you can do the same test in the aesa EF
and then compare it to a gimbaled ESA that dosent have a scan area that is the complete gimbal limit
for example the Su-30SM or Su-30SM2
TBH the track update rate on all AESA radars is likely over-performing in game.
1 Like
except it dosent
scan rate dosent matter for AESA radars after target detection at all
every target will get updated 10 times a second no matter the scan speed
afaik the eurofighter is supposed to scan a bit more than twice as fast as it does currently within ±70 degrees, but because devs cannot be bothered to model that, they have put a scan speed that represents the update rate for a ±100 degree zone for all modes regardless if the search zone is less than ±70 degrees
you mean for AESAs that can mecanically rotate having a target outside its current scan zone ?
For a fixed one 10 updates a second seems fairly OK tbh
I know, but it shows that they have at least attempted to mimic the interruption to the scan.
Yeah, the track update rate should be a bit less frequent for targets outside the current scan zone, but Gaijin don’t seem to be able to model two different update rates on the same radar.
And I suspect the update rate for all AESAs is likely over performing in game anyway.
3 Likes