DICE's silence
DICE's silence worries me, it just makes the game harder and harder to come back.
Forum Discussion
@VBALL_MVP Why don't they do it in this forum, what is official? so people stop being "toxic" a little ...
Here is the site...
https://answers.ea.com/t5/Updates/bd-p/battlefield-2042-updates-en
They need time to work on all the excuses in order to appease what is left of the player base. Or maybe they watch the player numbers drop and hope it is all over and forgotten soon. To me DICE is not looking determined to bring the game in this franchise into a halfway decent direction.
@NarrowSpeedo Game is out barely 2 months and obviously you expect it to be fixed yesterday, huh?
- @Chief2GFD i don't think this is what he means, its more on the line of the fact the game was released in this state can be seen as DICE lacking direction again, just liek they did with BFV
- @borroma31 Seems an up to date place to go🙄
I think people should stop blaming the developers. There is a difference between development and management. From what has been put mainstream, management is effectively entirely to blame.
@LeMairyHuffI partly agree on this. The big decisions like specialists etc are made by management.
But the quality (not design) of the game are the developers problem. There are a lot of issues that shouldn't be in the game.
Things like when you put in a match just to see the EOR-screen, stuttering when getting shot by vehicles/choppers, sudenly jump is not working, cannot revive people close to walls, hit-reg not working etc etc.
This is perhaps due to not having time enough, but it's still on the developers that creates the code (I work in IT, programs a lot and knows very well how hard it is).@cso7777I would agree to an extent.
There were a lot of decisions made which hindered the progress of the game which were out of the Developers hands (and also the artists and QA). Lockdown happened and everyone had to share a reduced amount of testing devices remotely between each other. Then, the Game switched focus from BR to FPS which is one of the worst decisions you could make for a game part-though its development cycle. You never change the original design and vision to such an extent. Especially on this scale of project. On top of that, many of the Frostbite Engine developers had left before 2042 switched to a new version of the engine, leaving no experienced engine developers left to aid the switch over, which drained the project for a while. Then, nearer the end of development, a number of UI developers left for a different company and apparently the UI was under-scoped and understaffed.
Developers aren't just coders. Typically, as you move into massive companies, developers become specialised. So for example instead of programmer we'd have "vehicle technical specialist" or "UI scripter" or "Anti-Cheat engineer" yada yada yada. I guess everyone was affected and the process became incredibly inefficient.
Its very complex but I suspect the Game Design shift and the Engine version shift were the biggest killers. It's never a good idea to do either before starting development. They still need time to formulate what happened before Christmas. I suspect they've still got a lot of vacancies and a lot of people are still new there. Must be quite scary in a situation like this.
The back tracking in star wars battlefront 2 was huge, and it eventually became a much loved game. So it can be done. Whether EA is willing to let DICE properly fix 2042 is another matter.
@ABC-Warrior-real wrote:The back tracking in star wars battlefront 2 was huge, and it eventually became a much loved game. So it can be done. Whether EA is willing to let DICE properly fix 2042 is another matter.
It's hard to compare Battlefront 2 to this though as the problems with 2042 are a completely different beast.
With Battlefront 2 people were irritated by the monitisation, the gameplay was still there though.
With 2042 the core is rotten and it doesn't feel like a Battlefield game.
Featured Places
