Pls could you pass the where say it
The AIM-54C and AIM-54C+ appear to have Doppler filtering modeled in the public files, despite the stat-card/spreadsheet showing “Continuous Wave.” The issue is not absence of Doppler. The issue is absence of visible distance / distGate range-gate behavior which I will try to correct. The sheet even states ’ In game value '.
You can find datamines on GitHub - gszabi99/War-Thunder-Datamine: Frequently updated War Thunder Datamine repository · GitHub.
Specific link : https://raw.githubusercontent.com/gszabi99/War-Thunder-Datamine/refs/heads/master/aces.vromfs.bin_u/gamedata/weapons/rocketguns/us_aim_54c_plus.blkx.
Don’t worry, there’s plenty of evidence for this.
That poll was extremely biased and also had a lot of shadow voters, so it’s pretty irrelevant at this point.
nuh uh
Oh to have that implemented
Yes, CW and PD are just named categories, not performances.
I appreciate yours and everyone else’s efforts to dig into these details 👍 Thank you guys, keep up the good work 🍻
Im gonna be honest, who the HELL has the time or patience to bot war thunder polls out of anything, they could use their bots on anything else but nope warthunder forum polls. There are definitely bots voting but probably not to the extent you are alleging, I could always be wrong tho
The poll is set to public votes too. He has 0 proof, just 100% cope.
I personally did not vote on the poll, because I am ambivalent to a TT version of the F-14D. I will support the majority opinion, and the majority obviously wants a TT version.
I already posted a few times that I preordered the F-14D, but I will not argue or vote against those who want a TT version.
If it had distance as well, it would be PD and not CW. CW is a correct reflection of its current state.
I love this literally, those who support TT F-14 say there are people using bots, and those who don’t support it say they’re using bots, but I think that at the end of the day, the problem is that these 1,000 people think they represent the ‘Community’ or the majority, without even knowing the opinion of 95% of the community.
Bro… a lot of people have already told you about your “objective” survey, well, really, it’s not good to produce clones in the tech tree, just because for movie lovers top gan f14d is something special
Don’t worry, I’m just noticing.
Bots are just a part of the problem.
Let me quote myself.
I had a genuine laugh when I found this.
Usernames are wt_jk, wt_fk and wt_lm.
All voted at the same time, all created on the same day…
Some people are certainly invested in this thread, which is why it got more than 1k votes with only 50ish unique users posting. So many voters are either literal bots or accounts that just happen to hop on the forum for the first time in months (with ridiculously low read times), cast their vote there and then disappear into thin air again, probably until a similar poll arises in the future. Definitely not compelled voters being used.
Not to mention the biased nature of said poll and inherent problems with polls on this forum in general.
That is exactly the issue. The current implementation may be CW-like because it lacks visible distance / distGate, but that does not mean CW-only behavior is historically correct. The AIM-54C documentation specifically states range discrimination and improved beam-aspect capability. Doppler discrimination and range discrimination are not the same thing, so adding a range-gate mechanic would be correcting the missing documented behavior. I believe stating PD as a ‘distance’ modifier might be seen as a fallacy considering the state of bug reports.
I did not buy it, but I think the AIM-54C+(?) should at least receive those seeker and other buffs that were mentioned by other players previously. Just stating that they have different cooling and are a functionally identic copy paste is not cool.
As well as the 54C+ receiving a much newer Transmitter adapted from the Aim-120, It should be able to take full advantage of newer LFM techniques to Range Discriminate, which is what this distance / distGate is trying to mimic but obviously having a much weaker distance / distGate function than modern ARHs
It is on the work as a report.
Exactly but we won’t use that as a primary argument as it is ambiguous. We have direct proof of range discrimination instead.
Edit: Because devs might just close the report instantly saying it doesn’t prove anything :(
