That radar in C-RAM mode operated differently than in Air surveillance mode.
It C-RAM mode it operates on much shorter range, but does scan the whole hemisphere instantly.
And for example Giraffe AMB has 1s update in C-RAM mode, yet it is still used.
so you confirm it updates instantly, you also seem to forget nothing in game is going to that far out where surveillance mode is the default, meaning the C-RAM mode is and should be the default or changeable considering it has the ability to be adjusted software side as per the specs of the radar
Type 03 Chū-SAM is nice but…the real question is…Will it work as intended or will it be treated the same way the Tan-Sam is currently treated with all loads of bugs and missing features and the way the Type 93 SAM was horribly treated in the past???
Please fix the Tan-Sam Kai…still horrendous to play. I want to say im grateful for the Type 03?? but, the way they implement Japanese vehicles always a let down…
lmao you know full well they wont because ppl like you simply accept the way they do stuff and they refuse to fix things to how they should be, go use the SPYDER and tell me its “right” and tell me how great of a system it is when its modelled so incorrectly it performs worse than a standard mechanical system or saclos system
and its why it needs to be called out more often, SPYDER has bug reports since launch day and not a single has been fixed but telling others to bug report issues when they treat there own bug reports like it doesnt exist because reasons, its why ppl lose there minds over simple problems
IM serious because i actually know how useless all spaa is by killing them all day every day in SRE. Your only duty is to shoot down ordinance, and CS5 is by far the best one at that in the whole game
I still don’t think having to place a bunch of giant vehicles on a map with zero places to hide them making it trivial for enemies to spot it is even remotely acceptable game design.
Aside from the fact that SPAA is severely lacking in it’s capabilities and gets absolutely shit on by a helicopters and such.
Even if by a miracle the SPAA can actually defend the airspace, I bet it will be no time at all before CAS gets their privileged position back with more absurd weapons that ruin the game as they have for the last decade.
For MPQ-64, it should still be implemented however. I think the current code allows for the TWS ESA part to have a different sector size. Would make each scan cycle have more accurate TWS updates.
Though I think the reason why TWS ESA isn’t implemented for most ground radars is because they are rotating. And how they simulate that is by having a “fixed” radar with 360° horizontal coverage. So there’s no “front” of array concept in-game unless the array has a fixed position (hence why the Pantsir/TOR/BUK, etc have it on their fixed arrays), with the front of a fixed array being related to the turret position instead. So if TWS ESA was added to “rotating” radars now, they would have continuous update of all trackfiles in a 360° radius (or if sector limited, it is pointing always in the same direction), regardless if the radar is even pointing in the relevant direction.
Spyder is an interesting one, having actually 4 fixed arrays irl, but in-game I believe it’s just simulated as one singular 360° rotating radar with 4 evenly offset beams. For this radar though, they could just add TWS ESA, because of its configuration.
So I think for TWS ESA to work on rotating arrays, Gaijin needs to couple the radar scan pattern with the physical rotation of the model of the radar antenna. Then they can get a “front” and do correct TWS ESA updates. Or at least some way to shift the “front” with rotation. But I can see that coupling model and scan direction may cause some spaghetti (net)code issues, especially the faster the radar rotates.