Battlefield 2042 Dev Blog addresses fixes coming this week and beyond, leaving other issues for discussion later

It’s no secret that Battlefield 2042 didn’t get off to a stellar start. Performance issues (especially on the dashboard), bug, and a mostly negative reception do not make the game any favors. Even so, the team still boasts twice as many players as the final version of the game at this point in the release cycle.

Good news for those of you who are playing maybe the team at DICE has publish a developer blog details some of the changes and fixes that will take place this week (on Thursday) and in larger updates in December.

The bad news? Some of the bigger issues fans want to hear have been put on hold until there’s more to talk about.

On the server side, the team is currently mostly satisfied with server performance after some initial fixes have been rolled out, and they feel that further changes will really balance out the server issues. happen. This includes the “spawn without your load” error. Hopefully that will be resolved this Thursday, the 25th. The XBox crash bug linked above has also been resolved through a required update that went live last week.

What is addressed later here are the frame rate issues that PC players are facing 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 responses to be addressed in the future are the return of scoreboards, voice chat, and server browsing… the team is not yet ready to talk about these larger entries and future plans for them. .

During this week’s update and the larger “Update 2” and “Update 3”, you’ll see TONS of tweaks to balance. They run the gamut from weapon spread improvements to vehicle changes (yes, seaplanes are being nerfed), fixes to console targeting aids, and aiming issues. on PC, and continuous monitoring of XP farms is now re-enabled.

It’s a LONG post, but if you’re hoping to see something specifically mentioned, you’ll want to read the entire post.