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
Currently does 190 deg/sec. Should be 560+ deg/sec
1 Like
Indeed, surely there isnt enough integration time to get consistent tracks at 70+km.
its ESA radars that have a high total azimuth (bigger than ±70°) and have a scan zone that covers the complete azimuth (EF, Gripen)
the Su-30SM2 will update targets around ±60° of the center of your search pattern, bc that is the electronically scanned area that the radar can cover
1 Like
the difference is that pesas can’t track targets outside of their electronic beam steering whilst on a mechanical axis while aesas can
so it’s fair for that to be modeled in game
That is one problem, another problem is that AESA radars can typically only form up to about 1,000 beams per second. If you add up the number of beams spent updating tracks in WT the radar has basically no beam capacity left for searching.
no
thats just not true
its probably an issue of computation on the N035 and N011M
there isnt really a reason why you wouldnt be able to do that with a PESA
1 Like
Surely the useable beam fraction is nowhere near 1000 though? Not sure what one individual T/R module can do, it’s not my expertise but i would have expected it to be like something like 50 modules per update, which would give you 20 beams, or 10 + 500 for scanning.
that would make more sense, was just basing it off the fact that none of the aircraft pesa’s irl can do that, but then I remembered ground based PESA’s can
This is a code limitation. There is no (existing) way to change the area which ESA updates are covering based on where the beam is pointed, only based on where the radar itself is pointed. Because tthe typhoon, gripen, the radar can perform a 200 degree scan across its entire field of regard, this means that either the ESA coverage would have to not work at all for the sides while in a 200 degree scan, or it has to overperform. If the 200 degree scan didn’t exist, this wouldn’t be an issue. That’s why Su-30SM2 doesn’t have a full ESA coverage (as its maximum scan is 120)
tldr gaijin sucks at coding and that’s why.
1 Like
lmao
Seems like the list can be updated with Rafale DI and Rafale EI from Indonesia now
3 Likes
This matter has already been submitted as a report. Link
Gunjob said that they created an internal report on this matter. However, they also mentioned that they would hold off on the implementation because it would make the code too complex.
@Gunjob Right?
and you might want to go test it right now
bc the N011M Bars dosent do that anymore
Right now there is a single value for ESA scan zone updates, so in order for a the full section scan (200°/180°) on the ECRS’s & Raven to work the ESA zone must be that large. This implementation is consistent even in the “ESA” only scan sector selections as all selectable sectors operate at the mechanical speed and not the full speed ESA speed of 560°/s.
For a more realistic simulation a number of changes to how ESA radars function in game would need to be implemented. There is no way to do it at present that doesn’t just make it wrong in the other direction.
3 Likes