They didn’t reject it. The accepted the document. The current flight model was close enough to not need adjustment for that anomaly.
Flight models in WT are not 1:1 with reality because WT itself is not 1:1 with reality. You can’t just change a single value and have it perform correctly, it affects everything with the flight envelope.
It’s the same reason why when people were hyperfocusing on the Oswald efficiency of the Su-27 they were in the wrong.
MLD supremacy!
dont he dare touch my G.91,s
Nowhere have I stated that. To wit, you asked for them rejecting a bug report. Them listing a report as not a bug is the developers doing just that. I accept your concession.
You have implied that developers will just take his numbers at his words, and even stated there was no materials in the reports he’s done.
If it makes you feel better, then I concede on this part because it really doesn’t matter either way even though developers have stated they will still tune the aircraft in the future as their response.
You made a lot of assumptions earlier on thinking that his testing or his motivation matters, that’s the crux of the issue, I’m just here to say that it’s not.
Also, RideR2 is a pretty nice guy, he’s willing to share with people the materials he’s using. If you don’t trust his tests, feel free to do your own.
I made no such assumptions. In fact, I have been very complimentary towards the dev team for doing their own tests and pushing back on the conclusions RideR2 made from his unsound tests. Instead I commented on the veracity of his claims along with the hope that the dev team do push back on these reports. Not sure where you are getting the idea that I am making such insinuations but it is deeply ironic that you are criticizing me (unfairly) for making assumptions while making considerable assumptions yourself.
You didn’t claim that his reports didn’t have sources or materials in them?
I would just like to point out, all of the FM reports in question have direct historical sources attached to support the claims made.
On the community bug report site, historical sources attached to reports are hidden from other users. Only the creator of the report and moderators / staff can see them:
I would also add that our developers naturally review all of this historical material and any tests submitted within a report and come to their own conclusions about the content and issue at hand.
I never made the claim that the developers would accept his reports at face value, that is your assumption (ironic). Instead my issue has been with the bug report system not allowing people to see the full info in the report.
His mathematical skills aren’t even very good, I saw a bug report that thankfully got shot down a few days ago by him where he wanted to nerf the F16A based on values that seemed to be made up. I think it’s best to take anything this user has with a grain of salt.
Thanks. Is there a reason why those sources are not freely available to those looking at the bug report who are not in the comment chain for that bug report? It would be helpful.
At the end of the day. We are talking about a soviet aircraft, which includes i guess one of the better selling premiums. The likelyhood that Gaijin would accept a mediocre bug report in this regard that would see it nerfed is extremely unlikely.
BOL nerfs that mostly affect mostly Sweden and UK. yeah that got passed very quickly despite most of it being wrong it seems and was instantly bugged report as being wrong by a tech mod. But Mig-23. No chance of that same thing happening.
Only way it got passed is if Gaijin saw un-disputable evidence of something being wrong
agreed
Way too much classified information gets leaked about war thunder. Had best not allow public access to them. Should just DM the bug reporter. Usually people like to share what they found
Some of his reports were accepted by developers.
These same reports are the ones that you claimed had no sources in them.
By claiming that reports which were accepted by developers had no sources in them, that is claiming the developers just took his word for it.
i only care about MLD lol
poor mig-27,s NOT like they ever turned that good before
His reports all contain actual historical values. His testing does not matter overall, only the actual documentation.
I dont think you’ll feel much of a change. Except at the upper limits of a fight
Considering those reports are locked to those who are not party to the bug report and that those sources are not part of the initial bug report and were added on later, one must simply go off the information provided to them. Again, my issue has not been with the developers. It has been with the clearly fallacious tests RideR2 has done and their use in his bug reports. You are tilting at windmills.
Yes, there are a number of factors.
First and foremost, security. As you will no doubt be aware, in recent years people have tried both unintentionally and intentionally to use classified or restricted material in reports. We cannot, will not and do not accept these in any way as per our rules. We will not touch or handle them. This method allows us to protect other users from accessing restricted material and also stops the malicious posting of said material with intent to cause harm. We can safely remove and delete the material without it spreading.
Secondly, many people spend their own free time and their own money to either purchase books, documentation or visit archives to collect information. Some of this may never have been seen before and there are many people on the internet keen for it whilst not so keen to properly obtain it for themselves. This method we have allows people to submit a bug report with materials that they have obtained without fear that random people cannot simply access it and screenshot it / download it for themselves. Respecting the OPs submission to help improve the game without forcing them to have to loose whatever materials they have obtained at their own time / cost expense.