Anyone has a delay sometimes when you ADS?
Anyone has a delay sometimes when you ADS?I'm having a weird slowdown when crouched unless they added that.
DXR Firestorm Crash – Players who are running DX12 & DXR and who attempt to play Firestorm after playing normal Multiplayer will crash. The workaround here is to either switch off DX12 or go straight into Firestorm after booting the game.
“Cairo” Reference in Menus – There is a setting which allows you to change your Squad colors in Firestorm. This setting has the word "Cairo" as part of the name. This is an old code-name and has no impact on the game.
Axis Male Soldier Face Paint - We're aware of an issue where Axis male soldier face paints aren't visible/selectable. We're working on this and will update with an ETA as soon as possible.
Firestorm Matchmaking Disabled - We're seeing too many failed Matchmaking attempts for this mode and so we're disabling all Matchmaking Options. We believe that we've developed a successful hotfix for this and are looking to deploy that tomorrow so that we can renable the mode.
Incorrect Dogtag Art - Dogtags for some of the new weapons which will be given as Chapter rewards have the wrong 3D and 2D assets. We're working with the teams to address and correct this.
End of Round Company Coins – Rank 50 players are presently no longer receive Company Coins for the End of Round. This is completely unintended. We believe that we have a backend fix and intend to deploy it tomorrow, if not sooner.
I can´t simply put my head around of how they work at Dice.I work as a developer myself, and I dont get how new and even old bugs return all the time.These reaccuring bugs just makes me feel like the devs dont test things, and they work fixes on different builds and old builds of the game where old code is lingering.Do they even get the time they need to test things before release with this live service model?
How is it on xbox ?
I can't believe Dice has finally cured me of my BF obsession. I literally have zero desire to play it now.
SirZeusor11 wrote: »
I can´t simply put my head around of how they work at Dice.
I work as a developer myself, and I dont get how new and even old bugs return all the time.
These reaccuring bugs just makes me feel like the devs dont test things, and they work fixes on different builds and old builds of the game where old code is lingering.
Do they even get the time they need to test things before release with this live service model?
In my field, this is a classic symptom of lazy workers.
Lazy Engineers (my field) copy and paste everything from the previous revision to the new revision.
While this is usually successful, they don't bother to correct the test procedure, or work instructions for the actual production of the product.
Quality control is supposed to catch the errors from the test procedure to validate that it does indeed work as the procedure and test result states.
This (at least in my field) is where the process breaks.
Most of the time, Quality Control "Assumes this as a mistake" and skips this step in the procedure, and the test passes.
It's to much of a bother to bring that fault, or error up to the engineer who revised the "project/product", or schedule a meeting over what they consider " an easy fix".
That gets someone in trouble with Management, people loose their jobs over things like this due to the cost of yet another revision.
It then goes overlooked, it's implemented, and created, released, and you have a recall.
I have worked on a LOT (not coding, or computers, but mechanical machinery) of engineering projects over the last 25 years, and this is classic lazy.
It looks like you're new here. If you want to get involved, click one of these buttons!