Per Bungie, if you encounter this error again, exit Destiny then relaunch. If this error pops up, relaunch the beta and retry that activity again and resume what you were doing before the error occurred. Bungie has disabled clan invites for the rest of the beta to squash this bug. Bungie does not yet have a solution, but redditors discovered a workaround related to clan invites. This error occurs after a player is returned to orbit during an activity or when inspecting gear. The latest update from Bungie suggests restarting the activity. This error crops up while playing various activities. If your Destiny 2 beta client crashes while playing or when logging in, uh - sorry? Open it again. ![]() Here's what to do if you encounter each one: ![]() Now that the Destiny 2 open beta has kicked off, we've seen a crop of error codes and crashes. If you encounter any network related issues during the Destiny 2 beta, please follow our network troubleshooting guide to ensure proper network settings for Destiny gameplayĪs of July 20, Bungie has also acknowledged the infinite super and infinite ammo exploits discovered by beta testers - so don't expect them to last.īungie suggested that players report any issues not listed above in the help forum if and when they run into any.Not all content has been localised in all languages.Sandbox balancing is still taking place: some weapons or abilities may have higher or lower damage than intended.Players may sometimes be placed at the beginning of the Inverted Spire strike when joining in progress.Players sometimes are kicked to orbit after witnessing a black screen when entering a Countdown match.Location names sometimes do not appear during Crucible gameplay.Bungie will be testing server stability throughout the beta, which may cause error codes to appear periodically.Players may experience a variety of networking error codes when attempting to play the beta.Here's the full list as of the time of writing: Other issues include location names not appearing in Crucible matches, bugs related to joining an in-progress game of the Inverted Spire strike, missing localisation for some content, and more. The biggest and most obvious problem Bungie has highlighted in advance is networking issues, something you're bound to run into in a stress test like this. You can consult that below, or scroll down further for current error codes and solutions. Prior to the Destiny 2 beta start, Bungie provided a list of known issues it expected players to run into. That doesn't mean you just have to live with it, though. ![]() In either case, it's not unexpected and you should anticipate some interruptions to gameplay. If you're having a problem with the Destiny 2 beta, it could be an error, or it could just be the fact that you're helping to test an unfinished product. Here's the latest on error codes and known issues. The Destiny 2 beta is not without its problems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |