Technically side facing radars? Although they’re very small and are likely closer to approach warning recievers if i had to guess.
Nevermind, i looked through the original source amd the side radars were mislabeled on this copy, they are phased arrays for communication by looking at the original i believe.
Actually wait yeah no there are detection aesas there, they’re just numbered wrong on this one for some reason. Yeah it has 360 degree coverage.
Yeah so it’s around the same estimation that was made in the Captor E E-scan speed buff from 2 days ago. Do you think such a document would be accepted as a primary source for a bug report ?
The F-35, 15EX, and F-22 radar are what I’m refering to, at least in the US. I mainly mean the high performance AESA/sensors in general though.
I meant a general decompression of just 0.3 higher (14.7), followed by a quarantine BR of 15.7 for the EFT AESAs, Rafales, Su-30SM2, J-10C, and 14.7s, probably soley occupied by base EFTs.
I never said the opposite, but scanning speed for ESA design really differs from a PESA to an AESA. I think the PESAs should get a slight buff overall and the AESAs should get an even bigger one since it’s pretty much how it’s supposed to work IRL anyway. This topic was opened especially for gathering sources that might help to buff the other AESAs that we already have in game.
You know how Tornado’s radar and F-8E’s radar have different scan rates?
That’s going to exist among different AESA radars as well.
If you want to buff a specific radar in-game, you need documentation [unrestricted] for that specific radar that says the scan rate.
Mine? Yeah, issue is without knowing the intervals in a beam cycle it can be quite a wide range of speeds. And bug reports usually need precise figures.
Again, gathering sources and documentation is the point of the topic here.
Well yes and no. AESA radars all have their differences in terms of searching pattern and FOV but overall share the same main operating principle. It’s commonly admitted that AESA radars have a massive edge on any mechanical or PESA radar since they can create several beams with their antennas to scan their entire field of view, which isn’t depicted in the game. A way of fixing this would be to simply increase the scanning speed that’s all I’m saying. But there’s really no way to justify the fact that the RBE2 AESA and J/APG2 (repectively on the Rafale and the F-2) should have the same scanning speed as the radar equipped on the SU-34.
AESA dont usually create multuple beams for tracking, see my post here on it.
Multi-beam forming is possible, and is often used on AESAs for jamming or communication or such. But not for tracking/searching, except for in some low accuracy early warning systems like you find on some ground installations.
ESA is the scanning method.
P/A is other factors.
Xeno Quaza is going to have more knowledge than I on this subject as well.
Scanning method doesn’t equate to speed. Speed has to be programmed.
Just instead of motors, it’s a different method of moving signals.
Hey everyone, I have a question I can’t answer myself, so any help would be great: Since the last update (Spearhead), there have been problems with the AESA/PESA radars, which were only partially fixed. I only have one aircraft with this radar (Kfir C.10), and I’ve flown it a lot. I know the radar in TWS mode isn’t fixed yet (it’s very buggy, loses track, etc.), but I don’t know if the other aircraft (Rafale, Su-34, Su-30, etc.) have this problem yet. Were all the AESA/PESA radars nerfed to make room for the ones coming in the next update? Or was it only the Kfir that was affected? Thanx for your attention
Yeah so, uh, the issue ESAs had is something I noticed almost immediately. How TWS ESA works is it has the radar point at the target’s last location, but the thing is there was an additional limitnon the range it would do this. Unlike other filters which are angular or other proportional forms, this was basically a hard box around the target’s last known location of like, 2 kilometers. So for targets moving faster then like 0.6 mach they’d leave the target area before they’d actually get outside of the beam’s scan width, which was causing issues.
This was what was fixed this recent update. Other issues ESAs have is just cause they’re not actually really any better then mech scans otherwise. And in some cases they even have worse doppler filters. It isnt something unique to the C.10, all ESAs in warthunder are very very similar in most of their parameters. All that really changes between them are modes/scopes/speed.
So if I understand well, there is no inherent upgrade in terms of pure E-scan speed between AESA and PESA radars ?
Correct, there is no inherent speed advantage from being an AESA.
That being said, fron my understanding, nato AESAs should be faster then ru PESAs on average, particularly in mode interleaving operation. Due to them using FETs instead of TWTs, allowing for faster modulation of output frequencies. But this isnt strictly speaking due to them being passive or active.
I don’t really understand how FETs would be a replacement for TWTs in that case (sorry, I’m really early in my studies in terms of electronics, and I’m pretty bad at it so far).
