With the Destiny 2 beta days away, Bungie has outlined a lot of points gamers might run into.
The developer stated that this has to do with it being a beta construct, which is to be anticipated. Some of the issues might interrupt gameplay, whether or not on account of server instability or different bugs.
The largest and most evident one is networking points, one thing you’re certain to run into in a stress check 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 checklist as of the time of writing:
- Players might 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 look periodically
- Location names typically don’t seem throughout Crucible gameplay
- Players typically are kicked to orbit after witnessing a black display when coming into a Countdown match
- Players might typically be positioned firstly of the Inverted Spire strike when becoming a member of in progress
- Sandbox balancing remains to be going down: some weapons or skills might have larger or decrease injury than supposed
- Not all content material has been localised in all languages
- If you encounter any community associated points throughout the Destiny 2 beta, please observe our community troubleshooting information to make sure correct community settings for Destiny gameplay
Bungie instructed that gamers report any points not listed above in the help forum if and once they run into any.
The Destiny 2 beta begins first on July 18 for pre-order clients on PS4, then a day in a while 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
