Destiny 2: PC Known Issues
This is a sub-page of Destiny 2 PC Support. If you are seeking Known Issues for Destiny 2 gameplay, please follow this link. For the most recent and updated list of emergent PC issues in Destiny 2, please click here.
Destiny 2: PC Known Issues
The following are confirmed known issues that players may experience while playing Destiny 2 on PC. Updates to this list will occur when possible. For the most up to date list, please see the Destiny 2 PC Known Issues thread within the #Help forum.
- 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.
- SLI Flickering: Some SLI users may experience severe flickering when launching Destiny 2. Players may need to change screen resolution or run Destiny 2 in Windowed Fullscreen to alleviate flicker.
- Fullscreen on Laptops: Fullscreen mode is unable to be selected on some laptops. Affected players may use Windowed Fullscreen mode to work around this issue.
- Flashing shadows in Pyramidion: Players may encounter flashing shadows when entering the final area of the Pyramidion. We are investigating this issue and will provide additional information once available.
- Oculus Rift Users: Players may experience lowered performance while Oculus Rift tracking cameras are plugged in. Unplugging the cameras from the computer may restore system performance.
- Screen Bounds on AZERTY Keyboards: Players may receive an incorrect key prompt when adjusting screen bounds on an AZERTY keyboard.
- 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.
- NumPad Binding: Players are not able to bind controls to most NumPad keys.
- 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.
- 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.
- 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.
- 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.
- Continuous Sign On: We have determined the cause to an error where players would be stuck at sign-on and are looking to ship a fix in a future update.
- TRUMPET Errors: Players who are encountering TRUMPET errors on PC may attempt to work around this issue by changing Blizzard Region, or unfriending deleted Battle.net accounts from their Battle.net friends list. More info here.
- 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.
- 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.
- Crash after Task Switching: The Destiny 2 client may crash after switching tasks (ALT+TAB) when AMD Crossfire is enabled. To avoid this issue, players should avoid switching tasks for extended periods of time when the AMD Crossfire feature is enabled.
- Cursor Stutter in Menus: Players may notice Mouse/Cursor stutter while browsing game menus with some system configurations. Players may want to lower mouse polling rate to improve performance.
- 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.
- Crash at Third Spire: Players encountering crashes at The Third Spire should try setting their frame rate cap to under 100 frames per second. Instructions for setting framerate cap can be found here.
- Scan and Repair: In some cases, players may repeatedly receive an error directing them to use the Scan and Repair tool, but the tool reports “no problems found.” For troubleshooting steps to take when this occurs, click here.