The first report is a 3D model issue, which usually take the longest to get fixed. The second was submitted as suggestion.
I know these have been “submitted as suggestion”; but I just wonder if the developers have actually taken a look, acknowledged and seen that these things need to be changed, or if they are like “nah”, which is how it feels.
2 Likes
This is only a suggestion that you might be able to bring up with the development teams and studiers in progress.
If they wouldn’t mind including some short notes regarding these suggestions and their reviews to at least show where the relevant teams are with their progress? It would be greatly appreciated.
Thanks again
2 Likes
It seems that bug reports are mostly based on whether or not it can be used to make money or change the balance in another nations favor. Bug reports are getting put on the back burner for years (Bagels two-feed cannon for example, Puma’s AHEAD) and then suddenly fixed sometime half a decade later.
The MIG-23 was overperforming hard, even without a bug report one could see that the older third gen, often simply regarded as a piece of shit by it’s own pilots, was outdogfighting Mig-29s and that that might be a bit from the real life performance of the aircraft.
However, there was an aircraft for 70$ that was based on a MIG-23 and was one of the best selling premium planes. Fix delayed.
Same for stingers and mistrals. Imagine the hate from all the people that bought the A10 and SU-25 getting clapped by lifelike manpads. No more dodging with a simply aileron roll. You’d have to work for that.
1 Like
Actually there are lots of trustworhthy public available information sources,but developers tend to deny them.The real question is developers are not military experts,even those experts are not familiar with every military vehicles,not to mention developers.I would say why not to just let technical moderators decide whether to accept a issue report or not,rather than leave them for developers.
2 Likes
Give them time, it has only been between a month to a week since they were accepted as suggestions (I don’t personally understand how they qualify as suggestions, instead of fixes or how they decide which queue they end up in, though).
https://community.gaijin.net/issues/p/warthunder/i/yUohrEMuQLna
https://community.gaijin.net/issues/p/warthunder/i/LbD7XSmoaAJc
https://community.gaijin.net/issues/p/warthunder/i/CrgLh51VkpQZ
Since they are after all correcting performance, and extending existing mechanics.
Reports that rely source materials are generally treated as suggestions, bugs are normally saved for things that aren’t working as intended, example being say you changed missiles on a plane but they won’t fire (that’s a bug). Where as “missile should perform differently and here is why” that’s a suggestion.
2 Likes
So, for example; if the devs had modelled Tiger I’s front armor as being 50mm thick instead of the real 102mm thickness, a bug report would be considered to be a “suggestion”, instead of an actual modelling mistake that needs fixing?
I am asking with an example regarding a retular steel plate’s thickness because many bug reports regarding these when it comes to modern MBTs are being treated as “suggestions”, even though the reported issues are, for example, the Abrams turret ring being modelled as being 50mm thick even though it’s visually closer to 300 on every photograph, etc.
If you needed source materials to make the case yes that would be a suggestion. If it was previously correct and changed without a report or any reason then it would likely be a bug.
1 Like
That’s a shame… I don’t know if it’s just a matter of wording, but it feels like the developers don’t take “suggestions” as seriously as “bugs”.
As if “bugs” as such were technical matters that objectively required addressing, while anything labelled as a “suggestion” were subjective matters with outcomes decided by the devs’ personal standpoints instead of real evidence (because they could consider it unreliable, insufficient or whatever.)
Largely there is always going to be a bit of subjective element to it. But it matches the difference in Incident and Service Request we see in the IT world.
I’ve had suggestions fixed the same day I’ve submitted them and bugs that lasted months, so I don’t think there is too much in the type of report dictating the urgency.
2 Likes
Thank you for your replies!
I always try to remain optimistic when it comes to issue addressing, but it’s sometimes frustrating and discouraging to see some of them remain unaddressed and unsolved for months, years or even indefinitely.
The maneuverability was higher when they were originally implemented in 1.91
This was changed with Update 1.97 when things were erroneously corrected.
So in this case should it be a bug or not?; since the issue is effectively, that it was erroneously impacted by “G-Averaging” As per the MANPADS article, and probably slightly low in the first place.
And if you trust what was said in
Apparently there can be issues due to there being siloed teams for bugs and features (?Sugestions?), but I wouldn’t read into it too much. though that may cause issues for the implementation of the Photo-contrast mode for the POST seeker, since its basically the same underlying issue.
1 Like
It was configured this way intentionally though, if the change was unintentional it would be a bug, but since its in change notes its intentional. So changing it is a suggestion.
Honestly its much easier to think of it as “incident” and “service request”, in IT an incident is something happening we never intended to happen (server crash, applications failing to run, loss of network connectivity, etc etc etc), where “Service Requests” are stuff like “I need this new application made available” or “there is a new config for application that needs to be distributed”.
For modifying the behaviour of Stinger (and others) we’ve got what is essentially an intentional configuration, ie the devs specifically made them the way they are, and you’re asking for that to be changed. That’s a service request (suggestion), the missile works, its working as the devs intended but you want it to work differently.
This was an interesting one, it could have been submitted as a suggestion on the CBR, I would’ve forwarded that. I don’t understand why the tuber in question was sent around the houses or how they ended up messaging War-Tinder and not a Tech Mod, but I see all kinds of people being encouraged to contact me for stuff I cannot help with so who knows haha.
2 Likes
Speaking of PURE bugs, bugs; could you take a look at this one?
It’s tremendously annoying and it’s 100% unintended and a bug: but even though it’s been 20 days, no one has even seen it yet, hence why I am resorting to you, hahah.
https://community.gaijin.net/issues/p/warthunder/i/duYXheyHvuJr
Cheers, forwarded.
1 Like
Great, thank you, cheers!
Thanks! I don’t know why some players shout their report about X vehicle could have Y armament be sumbited as a suggestion or be noticed not a bug, cause J-8F couldn’t use PL-8B won’t crash the game…
So, if X vehicle’s in-game armament don’t have it’s real-world performance or it’s model/animation have mistakes, it’s a bug, while if it don’t have a armament could use but not shown in game, it should be a suggestion?
Performance of a weapon would still be a suggestion. And weapon loadouts are always a suggestion. As they’re also used as a balancing criteria.
3 Likes