I might try to do a compairions of the volumetric scan rates of top tier radars at some point. Should get a better depiction of why some radars “feel” slow/bad while others “feel” fast/good.
I dont think scan speed in itself is a good metric to compare, since a radar that scans at lets say 120°/s but with a bar height of 1° would scan less in the same time period as a radar scanning 60°/s but at a bar height of 3° assuming they’re scanning similar azimuths.
Also, where did the Ground radar mode went?
It was on the Dev, but got lost on Live
the woes of a rushed update
AI.24 vs PS-05A
Scanspeed 160 deg/s vs 65 deg/s
Transiver power 2000 vs 600
Angle of half sensitivity 2.6 vs 4
Max distance of TWS (my own expirience) - 110 km vs 80km
Main beam doppler notch velocity in scan 15 vs 30
Main beam doppler notch velocity in track 15 vs 20
Target in TWS - 20 vs 10
PS-05 better only in azimuth limit
Honestly, it looks like the top-tier radar and mid-level radar have been swapped.
I know that speculation etc isnt a valid source, but Gaijin has explicitly stated previously that they try to go for best estimate if no sources are available.
Therefore, let’s go with what is known, and try to derive a reasonable value from that:
The Captor-C aswell as M are capable of interleaved A/G and A/A operation, aswell as keeping track of individual targets while resuming the regular TWS scan as the bug report stated previously.
These features by themselves necessitate these things to happen at the same time:
Now given we want to split these three about equally, and it updating ground and air reasonably quickly, i.e. every three seconds or better (already assuming conservative performance here), we arrive at it having to cover its 140° × 120° scan area (Captor M has ±70° azimuth and ±60° elevation) at least once per second. Now lets go with an absurdly unrealistically low requirement of simply scanning once from left to right, and once from top to bottom, no further sweeping. That means it still has to cover a total of 260 degrees of movement in one second.
Ergo, the worst possible performance it could reasonably be thought to have is 260°/sec
Mind that sources that are public, and that you yourself reposted as part of the bug report on Data Adaptive Scanning, suggests, at minimum, a scan rate of 333°/sec. This bug report was accepted.
Claiming there aren’t any sources or indications of a faster scan speed or better performance than a glorified blue vixen, and then giving it at best like 1/5th of its lowest publicly reported scan rate isn’t exactly fair. Nor is saying “its fine in its gimped state because I am doing ok with it” constructive.
That is not at all how radars work. You don’t ever scan the entire field of regard in a single scan pattern. You scan a set number of bars (usually between 1 and 8 which are each a couple of degrees apart). For example these are the scan patterns used by the Foxhunter radar on the Tornado, you’ll notice they don’t scan anywhere near the entire field of regard. If you want to scan an area higher or lower in the field of regard you move the scan pattern up or down. It scans 11.7° out of a 120° vertical FoR.
I said word for word that scanning the entire area by doing just one sweep left to right, and top to bottom, is hilariously unrealistic. I’m aware that the Captor, like any radar, scans in bars. I chose to simplify to highlight just how hilariously bad the radar is compared to what it would have to be.
If we assume a 4 bar scan for simplicities sake, we’d already be up to the ballpark of 400 degrees per sec assuming a wide scan, and reducing the area to a narrower one necessitates several hundred degrees per sec regardless so not even that could be reason for their fantasy number
There is only a Red Baron tribute skin, known as Baron Spirit, not one for Erich Hartmann
I’m fairly sure the Foxhunter 2G is easier to notch than the Blue Vixen and its derivatives
Where are you getting those sort of numbers from?
Having a radar scanning at 400°/s (or even 333°/s) would likely severely reduce the maximum range due to dwell time requirements.
The 333°/s number is very likely the maximum movement speed during the “jumps” not the normal scanning speed.
There may be a case where the radar range would not be sufficient for detection of fighter sized targets at the specified range of the Meteor missile.
Assuming we use the combat range of 200km (which the manufacturer states the misisle has a range in excess of 110nm)
Then the radar performance in game is not sufficient to utilise the extended range of the meteor misisle and as such can be considered to be underperforming by a significant margin.
If the max mouvement speed is infact 333°/s and past mech radars like the foxhunter have been able to acheive TWS scan speeds of 120°/s, it implies there shouldnt be much issues with the radar scanning at atleast 120°/s tho no?
Isnt this basicly the exact same TWS scan patter the EFT got?
If it has to cover 4 bars that are a large portion of its maximum area, since I did say a wide scan, and needing to do so within one second, necessitates such a high scan rate. It can still dwell on specific targets in between as needed.
Mind that the radar is very high power, with very good signal processing, it doesn’t need to dwell as long as some early cold war radars to get a good picture.
The 333°/s being the maximum during jumps and not achieveable in normal operation is indicated where? Do comment on how else you think it achieves the known performance and multi-mode operation
If I had the opportunity to choose a radar for the Typhoon between a copy of the PS-05 and a copy of the AI.24, I would not think for a second about the PS-05 option.
Public figure is 185km detection range against a fighter sized target (2,5 square metre RCS) when TWS scanning
(current ingame detection range of it is a joke)
It’s proven to be minimum of 160km for 5sqm rcs and up to 300km for large transports/airliners (up to 100sqm)
Captor M - Wrong/Missing Gimbal limits
https://community.gaijin.net/issues/p/warthunder/i/zkVEnTq99Az4
Scan speed, AI24 is bugged, should be only 80deg/s
Transceiver power again bugged should be 1250 in HPRF-VS for ECR-90 (but I cant change that as its a datamined value)
Max Distance is 120km for ECR-90 in TWS in MPRF
Both notches on AI24 only work their best in look up, in look down unless you’ve already got the target in a range gate it won’t see it.
Number of targets tracked should be 20 on ECR-90 and its not just tracking 20, it should only display 20 while tracking atleast 256 in the background (like BV)
That report appears to be confusing CAPTOR-M (which we have in game) with CAPTOR-E (which we don’t).
It is also showing a photo of an F-18 instead of a Eurofighter.
