Fix CLAWS radar rotation/scan speed please, bug report got accepted 5 months ago when the CLAWS was still in dev server and there has been no change at all :(
AN/MPQ-64 Radar Scan Rate Too Slow // Gaijin.net // Issues
Also the radar is supposed to be X-band, but i dont really care. I care much more about the unrealistically slow radar scan speed above.
Incorrect Radar Frequency for the SLAMRAAM // Gaijin.net // Issues
A quick fix. Thank you.
For those interested in what the issue looked like: Click
Ah damn. I actually liked that assist sound. It was like a metallic clang.
yea lol, I thought it was an actual feature and not a bug
Regarding Naval Forces and the recent major patch which introduced this new damage control option, please do something about the current bug which allows AI controlled ships to extinquish fires in less than 2 seconds. This essentially makes them immune to all fire damage, the fires simply cannot ever spread or cause any damage to crew, ammo or magazines.
Ive created a bug report about it here.
https://community.gaijin.net/issues/p/warthunder/i/dJMtkGMgTmr7
This is a major problem, because majority of the ships in Naval battles are these AI controlled ones.
Huh, is it the 3rd time being fixed?
Icl for a good 5 minutes I thought it was a new casing ejection sound effect but after I realized it wasn’t I didn’t hate the sound.
Can you actually leave the assist sound? I liked it
No
I too would like the sound to come back, it’s actually quite nice
Range is also wrong
I’ve been looking some more into the sentinel, but as I’ve noted also on that linked report, X-band is I/J-band, just using a different naming convention. But from further research, the frequency is at the edge of 10 GHz, so it should be I-band (8-10GHz). I don’t think it really matters though.
I did find more info on the radar, but it’s sadly not really positive:
The 30rpm should be corrected, though in-game it currently scans at 30 rpm already because it’s using 2 beams. Now, I don’t think it should have 2 beams (probably misinterpretation of the term “back-scan”), rather just the one forward, as it only has one antenna array (the secondary radar mentioned is for IFF), so functionally not much changes either again. The rest what is incorrect are sadly only nerfs, the radar can only search a 22° zone at a time at 30rpm (2s for 360°), meaning it should take 3x that, 6s, to search the full -10-55° sector (trackfiles should however be maintained within full limits). Beamwidth is smaller than currently (3x3° → 1.8x2°), but again doesn’t matter much. And it should not have TWS ESA seemingly, as the electronic back-scan is only good for an azimuth of ± 3.5°, it’s only there to increase dwell time.
Yeah, it kinda reminded me the famous Garand rifle ping… :D
And I liked that too…
C’mon Gaijin, you keep a crapton of bugs around for years. Can we keep this one as a feature? :)
i dont know if the range is right or wrong but i feel like its fine as is. I only needed to detect enemy up to 20km anyway and it can just fine. The ground launch aim120c7 got like 8km effective range lol, its not that good. I only launch at planes when they are like 10km away.
From what I found, the “back” radar isnt limited to only scan for IFF and does actually help effectively scan for targets. Currently in game, the CLAWS radar spins at the rate of 15 rpm (real life is 30 rpm) and the back scanning works correctly to double its virtual scans per minute. This means that the radar is scanning 50% slower in-game because the radar spins half as slow. The real CLAWS radar have 60 virtual scans per minute. which isnt a little ammount at all and i want it fix ASAP
wait dude ur actually right, i was so confused and was doing research for the past hour hour on it lol. the “back” radar that we see indeed seems to be the IFF and not the radar responsible for scanning behind it. How the CLAWS radar (AN/MPQ-64) scan behind itself is using something called Phased-Array-Radar or something and what it does is sending a beam (only ±3.5 degrees, which is rather small but still useful) directly behind itself using the main radar dish. It’s crazy cool to me that it can do that without needing another radar “pannel”.
I think Ray Tracing still has a ways to go to truly feel right but I was having the artifacting and it finally seems to be resolved. It’s a step in the right direction, so I’ll take it.