The Diablo IV beta test has begun – sort of, because you can probably forget about a comfortable game for a while. Players complain about long queues and numerous bugs. Below you will find a list of the most commonly reported issues.
Many players have reported that the “Play” button in Battle.net is still greyed out. To resolve this issue, it is recommended that you restart the application. Then you have to wait in line at the server. This is to be expected, although there are times when players do not even log into the game after the appointed time. Blizzard recommends that you be patient and not close the app until you are able to play – otherwise the queue will definitely reset.
Also, many are faced with the following message: “Game servers are unavailable. Please try again later (code 34202)”.
Since Diablo IV requires a permanent internet connection, you will not be able to play if you see this message. Worse, you are unlikely to be able to fix the situation, since the fault most likely lies with Blizzard. While you can make sure your connection is stable or check that your drivers are up to date, don’t count on much.
Blizzard precedes the start of beta testing by publishing a list of issues that the developer is aware of and which he has not yet had time to fix.
If the intro scene is played during an in-game day, the shadows of the player character and accompanying NPC will begin to flicker. This state will remain until the end of the prologue. The error will not occur if the cinematic interlude is skipped. In-game voice chat does not work correctly. Optimization leaves much to be desired – especially on weak PCs, as well as on PS4 and XOne consoles. The “Play” button visible on the character screen does not work. The dub is only available in English. There are supposed to be more languages in the full game, but for now, you’ll have to settle for subtitles. If another player wants to join the co-op mode, and he already has a created character, he may run into problems.
Leave a Reply