With the Destiny 2 console beta almost upon us, Bungie has been kind enough to provide a list of bugs that may be encountered during the event via the developer"s weekly blog post. Considering the game is still nearly two months away from release, ironing these issues out with a beta is probably the best route to take for a smooth launch.
The issues range from networking errors and missing location names, to getting kicked into orbit when entering a Countdown match. The full list of known issues in the Destiny 2 beta is found below:
- Players may experience a variety of networking error codes when attempting to play the Beta
- Bungie will be testing server stability throughout the Beta, which may cause error codes to appear periodically
- Location names sometimes do not appear during Crucible gameplay
- Players sometimes are Kicked to Orbit after witnessing a black screen when entering a Countdown match
- Players may sometimes be placed at the beginning of the Inverted Spire Strike Activity when joining in progress
- Sandbox balancing is still taking place: Some weapons or abilities may have higher or lower damage than intended
- Not all content has been localized in all languages
As the console beta is slated to begin next week, pre-loads for the Xbox One and PlayStation 4 are now available. The pre-load"s download size for the Xbox One comes at 13GB, with the PlayStation 4 pre-load weighing in at 15GB.
Lastly, be sure to head on over to the Bungie feedback forums and the issue tracker to help the developers out during the beta phase.
The Destiny 2 beta begins early for players that pre-order the game, starting July 18 for PlayStation 4, and July 19 for Xbox One. The console beta then opens up for everyone on July 21, with the whole event set to end on July 23. A PC beta is set to begin in late August, and will most likely include the same content that is included in the console beta, as Bungie announced earlier this month.