Now that I am getting into vessels and crafts with explicit radar systems, I am starting to notice some errors. My first hint of an issue was with the PGM-59 Kim Qui: the Kim Qui uses the SG radar system, which is an S-band radar system.
However, the Wiki claims it is an A-band radar:
which is anachronistic in any labeling system I can find. There is no such thing as “A-band” in the IEEE system, and in the modern NATO labeling system, that refers back to the 0-250 MHz band. The pre-1978 NATO system also does not use “A” for any band. The band that the SG unit DOES use is 3 GHz, which is either S-band in IEEE, E-band in pre-1978 NATO, or the E/F-bands in modern NATO.
The AN/SPS-6 radar on the DL-2 Mitscher:
is an L-band radar according to pre-1978 labels, and according to Modern NATO nomenclature it is a D-band radar. The AN/SPS-4:
is C or G band, respectively, the AN/SPS-8A:
sits solidly in S or F band, respectively, and and the DL-2 Mitscher shouldn’t have the AN/SPG-51 system at all in its 1954 configuration as the game and wiki claims it is, that should be the Mk.37 GFCS, which moves that into an in-game modeling error independent of the errors listed above.
I’ll keep looking, but this seems like a relatively important oversight in my eyes, at least as more work on radar units are being done post-Nuclear Thunder (which means hopefully it’ll also get fixed soon?)
Sure, and I will, but I’m also curious just how far-reaching the mislabeling is as well. It’s not very helpful if I get one or two crafts fixed if there’s a bunch more than that mislabeled; I’d rather try and collate as much as I can and get it all fixed at once. Kinda wishing the wiki supported talk pages like wikipedia…
If/when you make a bug report, please let us know and leave a direct link to your report so that we can click on the “have the same issue” button!
I always greatly appreciate everyone who takes the time to find the errors, find the correct info, and submit a report. Thank you for your time and effort 🍻
You will still 100% need to make a bug report for each vehicle, UNLESS they all share the EXACT same radar.
Then, if you wanted to, you could create a “directory” of links to all of these very similar reports to add to each of the bug reports. That way the Devs might be able to address all of them together, hopefully. I would add a list like that as an “Edit” section, maybe to the top, but be VERY clear that these are NOT duplicate reports, that they are only related issues. If you make it seem like anything is a duplicate the bug reporting managers are likely to lock all of them except one and tag the rest with “duplicate/closed” etc.
I would highly recommend saving a “template” of your report(s) in a .txt file or something so that you are not redoing all of the work each time. Same for any screenshots, links, replays etc that you generate. Make yourself a folder on your computer with separate sub-folders for each report/vehicle/radar you create. Keep everything organized.
If you ever need to submit a video that is large/high resolution it is often best to upload it to YouTube first, and then paste the link to your YouTube video so that you do not have any file space limitations. You can then share up to 4k resolution videos without worry. (Also, if you are concerned about sharing your Google/YouTube profile, you could create a new account specifically for sharing War Thunder videos etc.)
The bug report system is not perfect, it can often take a LOT of time to get things corrected. However, it is still worth the time and effort. Make your bug reports as clear concise and detailed as possible. If you submit a report without supporting evidence the odds are it will just be closed and you will have to start over again. Take your time, let us know if you need any help filling out your report(s).
