The Destiny 2 beta shouldn’t be with out its issues. Here’s the most recent on error codes and recognized points.
If you’re having an issue with the Destiny 2 beta, it may very well be an error, or it may simply be the truth that you’re serving to to check an unfinished product. In both case, it’s not sudden and you need to anticipate some interruptions to gameplay.
That doesn’t imply you simply need to stay with it, although. Prior to the Destiny 2 beta start, Bungie supplied an inventory of recognized points it anticipated gamers to run into. You can seek the advice of that under, or scroll down additional for present error codes and options.
Destiny 2 beta recognized points
The greatest and most evident drawback Bungie has highlighted prematurely is networking points, one thing you’re certain to run into in a stress take a look at like this. Other points embody location names not showing in Crucible matches, bugs associated to becoming a member of an in-progress recreation of the Inverted Spire strike, lacking localisation for some content material, and extra.
Here’s the complete record as of the time of writing:
- Players could expertise quite a lot of networking error codes when trying to play the beta
- Bungie shall be testing server stability all through the beta, which can trigger error codes to seem periodically
- Location names typically don’t seem throughout Crucible gameplay
- Players typically are kicked to orbit after witnessing a black display when getting into a Countdown match
- Players could typically be positioned in the beginning of the Inverted Spire strike when becoming a member of in progress
- Sandbox balancing continues to be happening: some weapons or skills could have greater or decrease harm than meant
- Not all content material has been localised in all languages
- If you encounter any community associated points in the course of the Destiny 2 beta, please observe our community troubleshooting information to make sure correct community settings for Destiny gameplay
Bungie urged that gamers report any points not listed above in the help forum if and after they run into any.
Destiny 2 beta error codes
Now that the Destiny 2 beta has opened for PS4 early access, we’ve seen a crop of error codes and crashes. Here’s what to do in case you encounter every one:
-
Client crashes
If your Destiny 2 beta shopper crashes whereas enjoying or when logging in, uh – sorry? Open it once more. Bungie is investigating this subject.
- Olive error code
If you encounter this error, attempt restarting the beta shopper. Bungie has no additional informaiton at the moment.
-
Moose error code
This error crops up whereas enjoying numerous actions. The newest replace from Bungie suggests restarting the exercise.
-
Weasel error code
This error happens after a participant is returned to orbit throughout an exercise or when inspecting gear. Bungie doesn’t but have an answer, however redditors have found a workaround associated to clan invitations.
-
Olive error code
If this error pops up, relaunch the beta and retry that exercise once more and resume what you had been doing earlier than the error occurred. If you encounter this error once more, exit Destiny then relaunch. If you proceed to see this error, it’s doubtless as a result of testing on Bungie’s finish.
-
Termite error code [resolved]
The Termite error prevented gamers from hook up with the Destiny 2 beta, however seems to have been resolved on PS4, however affected Xbox One gamers till the preliminary demand of beta launch died down. Restart the shopper in case you’re nonetheless caught.
The Destiny 2 beta began first on July 18 for pre-order prospects on PS4, then a day afterward Xbox One. It goes open to everyone on July 21.
The beta contains entry to a single-player mission, a strike, and two PvP maps and modes.
Source
