The Mirage 4000 is still missing its chaff dispensers. To this day it only has the correct x112 large calibre countermeasures available, despite the modeled chaff dispensers on the same countermeasure pods.
This bug report is genuinely so frustrating to read. Over a year ago they gave a fair response, in my opinion, stating that the chaff dispensers will be implemented once separated countermeasures are implemented. However, in the Seek & Destroy update in June this year, split countermeasures were fully implemented. After this, other bug reports made on the issue are simply shut down and claimed to be duplicates of the bug report I have linked above. It has now been 6 months with no word or changes, with no recourse for the players to point out the issue to Gaijin. Gaijin simply plugs their ears whenever anyone makes a bug report about this. Just fix this issue
Sure there is, at 13.0 it’s still competitive enough IMO, and it’s the only vehicle that can take more than 4 Magic 2s. I’m still able to find success with it even now at 14.0 uptiers.
Well, these guys obviously don’t have time to fix mistakes; they’ve prepared eight premium packs for the next patch (only one of which won’t be a clone).
I’d love to hear from anyone about why this is handled so bizarrely. @Smin1080p_WT
It’s been YEARS NOW, such a simple thing, and it’s repeatedly silenced and never mentioned.
If a forwarded report already exists for something, making a new one sadly doesnt change anything. Unless there is new information or evidence to add, it will be closed as a duplciate of the existing one. Anything that adds additional countermeasures is considered as a suggestion, not as a bug.
Hello Smin, the original report was given a specific response that is pretty unique to it. Most responses don’t have a statement like this but this report did. The developers specifically stated that the extra countermeasures would be implemented once the mechanism came into the game. The mechanism is now in the game and it still is not yet fixed.
There has to be some level of accountability here. If the developers promise to implement it when the feature arrives, then they should hold their word to it.
This is exactly the problem. I understand that this isn’t a bug, and a new report won’t really change much, but it’s frustrating that there’s no recourse here. Especially when the devs already accepted the suggestion and gave specific info to their plans to fix this problem. BUT ITS BEEN TWO YEARS NOW. And somehow there’s not a word about it, and no way to notify the devs of this suggestion and their own words regarding plans to fix said issue.
