New mechanics and features generally come first for Russians wherever applicable and then rolled out for the others later unfortunately. Aster-30 still doesn’t have PIF-PAF mechanism while the new Pantsir gets correctly configured the new proxy fuze system which still has not yet to be rolled out to any other vehicles likely because developers are relying on reports to come in to expand this system.
It still remains that it is routine for new mechanics or features comes to Russian equipment or vehicles initially before being expanded to others through bug reports. Russian vehicles may still get bug reports, that is true, but more often they do not need bug reports for certain features or mechanics as developers have already done the research on the Russian vehicles.
This disparity is a double-standard for developers treatments of vehicles unfortunately. Some vehicles need to be bug reported and wait for reports to be resolved after several years while Russian vehicles do not need to be bug reported for certain mechanisms and features at all as developers have configured them to have those features in the first place.
So during the development of the Dragoon, you’re telling me that every single person working on it missed the videos of it firing PABM? Or how about the fact that it is well documented that it is based on the flat bottom hull ICV (M1126), which is also well documented to have spall liners? The report for spall liners wouldn’t have been needed to begin with, if you guys had fixed the M1128 missing spall liners, which was reported 2 YEARS ago. I feel like I hardly ever see a vehicle receive missing content until it’s like, several years after its addition.
A) Everything on the dev server is work in progress, NO vehicle is considered final
B) During this stage, whilst the devs work on the finalisation of vehicles, anything that can be seen on the the dev server to be “missing” should be reported anyway so it receives a response from the devs or is correctly picked up on and resolved
Not reporting things always has a chance that things can, inevitably unfortunately get missed. That is why, rather than keep posting about it / asking about it, we encourage a report be made so that there is a fully traceable and trackable public place for people to see its progress and/or dev response.
Unfortunately there isn’t enough transparency in regards to where progress is on reports. For instance if we ask you what the status is on a report, it is usually one of two answers:
“Report remains open and is still being investigated”
Or
“Report is resolved and waiting on deployment”
There’s no in between. There isn’t explanation exactly on what else is missing in terms of research or investigation that could assist the report in being resolved.
In some cases, it could be the case that the only thing holding up a report from being implemented was an additional source being needed to resolve the report, but it isn’t communicated to the author of the report who could help provide the additional sources to expedite the report.
There is a tag for missing information or if more information is needed in a report. Don’t know what it’s called exactly but it’s blue ^^
What’s more problematic is the lack of transparency regarding suggestions and why some reports sit on “accepted” for years (not even just suggestions but bug reports too).
its funny how there expectations are wait 3 years for 1 small buff to be implemented because “there doing extra research” (photos of challenger 2 spall liners isnt enough or they just dont want to buff it)