Why I’m seeing a buff implying bug discussion about the SPAA that should suffer in my german plane thread?
well… you sure ? because this looks entirely random in this case.
it got closed because a forum suggestion already exists
https://community.gaijin.net/issues/p/warthunder/i/Dj1BHjmnDynQ
Yes, as this has already been passed to the devs. There isnt a need to duplicate it via a report.
either way i hope it comes soonish together with the spice bombs for israel
Taking it back to the Typhoon.
Have the devs got any plans in mind for the CAPTOR-M given that critical information for it isnt available, such as Scan Rate?
The Blue Vixen placeholder is fine for now, but would be very much interested in seeing a far more capable radar for it sooner rather than later. Especially as I doubt we’ll get CAPTOR-E anytime soon for it
2 Likes
CAPTOR has been and will continue to be set-up with all publicly available information. Reports are welcome for any inaccuracies that can be supported with public materials.
and what for information that isnt publically available?
Is Gaijin willing to make guesstimates?
For example, we have this source
Spoiler
that states “which allows extremely high scanning speeds” but doesnt state what that speed is
clearly the guesstimate is that its the same as blue vixen
1 Like
They aren’t right now, but they gonna need to be soon. We’re at the tail end of modern stuff of which declassified details exists, and it’s only gonna get worse from now on. If they don’t change their stance soon, all avionics will largely stagnate in terms of capabilities
Better but still not correct
Scan rate, Flame has good info for from the looks of it. Likely wont be a big buff, but it should increase when it gets bug reported and actionned.
The major ingame issues as I currently see them are:
- Repeating bars kill high barcount radars like CAPTOR-M. This NEEDS to be fixed as it effects both the radars ability to track targets effectively and the overall situational awareness.
- Priority track should be added, this will further mitigate the track issues of the radar.
- Roll stabilization on the blue vixen (and therefore likely the CAPTOR-M) is electronic iirc. The CAPTOR-M should have no track issues from rolling maneuvers (already implemented on the Rafale).
Theres other info we dont have public sources for yet (unfortunately) that arent useable, but do point us towards things we can look for. Those are shots in the dark tho regarding if we’ll find acceptable sources for gaijin, and some info still eludes us overall.
Im just not totally convinced that the scan rate wasnt increased from Blue Vixen. I just dont see how 70° / sec is fast enough for the interleaved mode and why they would develop a radar capable of moving at 333° / sec if its only going to use less than 1/4 of that capability. Just seems wierd for me.
Moving != scan
Where did I state that it did?
But why develop a radar that can move nearly 5x faster if you arent going to use that speed for a higher scan rate
Because scan speed is limited by light speed and necessity to send and receive many echoes
scan rate is limited by the radars range. Just a physical limit of having to wait for the return (multiple times infact as one ping usually isnt enough)
The question is if it would be sped up IRL if you reduce the scope size
So why arent ALL mechanical radars equally limited? Foxhunter has easily double the current scan rate of Blue Vixen. Many other radars also have greater scan rates to that of Blue Vixen.
Gunjob mentionmed foxhunter is bugged and much to fast rn.
Could also have to do with bar height for the radar. Ive got some unfortunately unreportable estimates that the bar heights are too low. If CAPTOR-M increased the amount of area it was scanning, that could possibly justify why it would need a longer dwell time as well.
Im still dubious personally that it is the exact same scan rate as Blue Vixen and not even slightly faster.
Because its basically bigger Sea Vixen?