'

Bungie releases a list of Destiny 2's Day-1 issues on PC

Bungie are being upfront about some of the game's issues

Bungie releases a list of Destiny 2's Day-1 issues on PC

Bungie releases a list of Destiny 2's Day-1 issues on PC

Destiny 2 is set to launch on PC later today, delivering the series to PC for the first time outside of August's Open Beta. Whenever a game launches, especially on PC, issues often come to light, aggravating some day-1 purchasers while also acting as an effective "stay away" sign for the game when it is discussed on forums and social media. 
 
Bungie is being proactive with their release of Destiny 2 by delivering a list of known day-1 game issues, as well as some fixes for these issues if/when they occur, which will help players to have a better in-game experience. 
 
This list includes issues with SLI, HDR, login/disconnect issues and even issues with multi-screen display configurations. Thankfully Bungie has included fixes for most of these issues. 
 
 

Destiny's official PC system requirements and release times have been released


With the release of Destiny 2 on PC the PC version of the game will be receiving an update called Hotfix 1.05, which fixes several issues that are present in the PC version's early builds.  Both AMD and Nvidia have released GPU drivers that offer performance optimisations for this title, so we recommend installing these before playing the game yourself. 

 

Day 1 PC Known Issues List

Listed below are issues that Bungie is aware of that exist in Destiny 2 on PC.

- SLI, HDR, and VSYNC: Players may experience some rare issues when enabling SLI, HDR, or disabling VSYNC in some non-native resolutions. For the best experience, players are encouraged to use these features while running at their display’s maximum available resolution.
- Saxophone Errors when Launching: Players may erroneously encounter Saxophone errors when launching the Destiny 2 application directly from the .exe file. Players who encounter this issue must close the application and relaunch through Blizzard’s Battle.net app.
- Idling to Title Screen: In some activities, players who are returned to the title screen due to idling may be unable to log back in. Players who encounter this issue must close and relaunch the Destiny 2 application.
- Login after Disconnects: A generic error code may appear to players who lose internet connection, which may block an affected player from logging back in even after reconnecting. Players who believe they are encountering this issue should close the Destiny 2 application and relaunch.
- Buffalo Errors on multiple PCs: Players may encounter Buffalo errors when logging in to Destiny 2 on multiple PCs at the same time. To prevent this issue, players must ensure that they are logged out of Destiny 2 on any PC that they do not currently intend to play on.
- Cursor in Tri-Monitor Configurations: Changing resolution between 5760x1080, 4080x768, and 3072x768 may trap the mouse cursor in the right-most monitor. Players who encounter this issue should ALT+TAB out of the Destiny 2 application, then back. Players may also toggle Windowed Mode by pressing ALT+ENTER.
- Tri-Monitor Depth of Field: DOF effects may be overly aggressive on some tri-monitor configurations. Players who encounter issues with DOF can disable this feature in the Graphics Settings.
- Windows 10 Game Bar: The Windows 10 game bar may not work in Fullscreen Mode. Affected players who wish to use this feature should use Windowed or Windowed Fullscreen Mode.
- NumPad Binding: Players are not able to bind controls to most NumPad keys.
Screen Bounds on AZERTY Keyboards: Players may receive an incorrect key prompt when adjusting screen bounds on an AZERTY keyboard.
- IME in Fullscreen: Players who are running Input Method Editors may encounter a black screen or delay when inputting characters in Fullscreen Mode. For the best experience, these players are encouraged to play in Windowed or Windowed Fullscreen Modes.
- Closing Application: When closing Destiny 2 on PC, players must close the application via mouse input. Controllers cannot select the in-game button to close the Destiny 2 application.
- Corporate and University Networks: Some players may be unable to play Destiny 2 on corporate or university networks. Players who encounter this issue must contact their IT department, to meet the connectivity standards outlined in our Network Troubleshooting Guide.

 

You can join the discussion on Destiny 2's day-1 PC issues on the OC3D Forums

«Prev 1 Next»

Most Recent Comments

x

Register for the OC3D Newsletter

Subscribing to the OC3D newsletter will keep you up-to-date on the latest technology reviews, competitions and goings-on at Overclock3D. We won't share your email address with ANYONE, and we will only email you with updates on site news, reviews, and competitions and you can unsubscribe easily at any time.

Simply enter your name and email address into the box below and be sure to click on the links in the confirmation emails that will arrive in your e-mail shortly after to complete the registration.

If you run into any problems, just drop us a message on the forums.