With the launch of the PC version of Destiny 2 quickly approaching, Bungie has shared a list of issues PC players may face.
These Destiny 2 known issues most of the time don’t yet have solutions, though for some, restarting the game should help. The list is a bit long, but most of them are very PC-specific problems.
This follows two other equally important info dumps. The first detailed the game’s global launch times, system requirements, and app incompatibilities. The other one was shared earlier today detailing Destiny 2’s content calendar post-launch with regards to activities like the Leviathan raid, Trials of the Nine and Guided Games.
In our Destiny 2 guide, we cover more common problems across PC and consoles, such as the error codes, but you’ll find the PC-specific issues below:
–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 5760×1080, 4080×768, and 3072×768 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.
- 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.
- 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 the Network Troubleshooting Guide.