Battlefield 2042 Dev Blog Addresses Fixes Coming This Week And Beyond, Leaves Other Issues For Later Discussions

It's no secret that Battlefield 2042 hasn't been off to a stellar start. Performance issues (particularly on consoles), bugs, and a mostly negative reception aren't doing the game any favors. In spite of all of this, the team is boasting over twice as many players compared to the last version of the game at this time in the release cycle.

The good news for those of you playing may be that the team at DICE has published a dev blog detailing quite a few changes and fixes coming this week (on Thursday) and in larger updates in December.

The bad news? Some bigger issues that fans want to hear about have been put off until there is more to talk about.

On the server side of things, the team is now mostly happy with server performance after some initial fixes were put into place already and they feel that further changes will really balance the server issues out. This includes the "spawning without your loadout" bug. Expect that to be addressed this Thursday, the 25th. The XBox crashing bug linked above has also been addressed through a mandatory update that went out last week.

What is put off for later here is the framerate issues PC players are getting if they don't have high-end CPUs and GPUs. The team is investigating, but you'll have to wait for an update on any real fixes for that particular issue. Other feedback that will be addressed in the future are the return of scoreboards, voice chat, and a server browser...the team just isn't ready to talk about these larger items and future plans for them just yet.

Over the course of this week's update and the larger "Update 2" and "Update 3", you'll be seeing a TON of adjustments for balancing. These run the gamut from weapon spread improvements to vehicle changes (yes, the hovercraft is getting a nerf), fixes to aim assist on consoles and aim issues on PC, and the continued monitoring of XP farms now that progression has been reenabled.

It's a LONG post, but if you're hoping to see something in particular addressed, you'll want to give the post a full read.