Blizzard’s Diablo 4 beta update fixes latency and bugs

- Advertisement -

The Diablo 4 beta is still far from perfect. While many players were able to dive into the early access beta of the dark fantasy RPG and experience its first act, the initial release was accompanied by long queues and player bans, as well as performance issues on some hardware. Blizzard is listing some of the known Diablo 4 bugs and issues that it is actively working on as the beta continues.

Diablo Community Manager Adam “PezRadar” Fletcher thanks players for their “overwhelming response to the Early Access Beta weekend” and lists some of the most common issues the team is currently working on. He notes that the team has been working through the night and says that more updates will be provided “the latest [Saturday] Tomorrow (PDT)” on the Blizzard forums.

- Advertisement -

The early access beta is available to players who pre-order the game and allows them to choose from three Diablo 4 classes available in the full game. Players can reach level 25 and receive an adorable sleeping puppy in a backpack for reaching level 20 with at least one character. An open beta weekend will take place from March 24-26, during which progress will be carried over and the remaining classes will also be available.

Diablo 4 Beta Known Issues

These are the Diablo 4 beta bugs recognized by Blizzard:

  • Sometimes players are unable to party with other players during gameplay.
  • Players who are kicked out of the game receive an error message stating that their party does not exist.
  • The rubber band appears on players when moving between areas.
  • High RAM and GPU usage on select hardware.
  • If the player triggers Lorat’s opening cutscene while the world is in daylight, the player’s and Lorat’s shadows will flicker in-game until the prologue is complete. This issue will not occur if the player skips the scene.
  • In-game voice chat may not work well for all players.
  • Performance optimization is still ongoing. Players may experience performance issues, especially on older hardware on all platforms.
  • The “Play” tab at the top of the character select is active, but does not currently lead to another menu in the beta.
  • Users may experience a queue when logging into Diablo IV during the Early Access Beta weekend. Please note that the countdown may end and exceed the duration indicated on the countdown. DO NOT leave the queue as this will reset the queue.
  • During the beta, players will be able to choose from a variety of unfinished “text languages” in addition to English. English will be the only option available for the spoken language during the beta, but other languages ​​will be available at launch.

Fletcher says that Blizzard also continues to manage in-game player flow with queues. He notes, “Many players have successfully logged into the game, but we understand that for some the wait time has been longer than expected.” Many also find themselves banned from the game due to Diablo 4 code 316719.

While my initial startup queue was around 90 minutes, I was able to connect after waiting just 1-2 minutes later on Friday night. However, this can fluctuate during peak times, so keep that in mind if you want to gamble.

Once inside, check out our in-depth Diablo 4 Barbarian, Diablo 4 Rogue, and Diablo 4 Sorceress guides and you’ll be set to succeed no matter which class you choose.

Source : PC Gamesn

- Advertisement -

Subscribe

Related articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here