Destiny 2 on the PC launched a few hours ago and all kinds of issues have surfaced. One issue in particular that seems to be causing frustration for some is the AMD Phenom II crashing problem as it falls below minimum specs and the SSSE3 requirement. Bungie is aware of the problem and confirmed Destiny 3 won’t run without SSSE3.
We have seen some players ask for refunds which appears to be possible if support is contacted. Keep that in mind you are still experiencing crashes and problems after this launch teething period. Also, bans are still happening (Update: Bungie issues a statement on bans) to players using third-party apps.
The list of known issues has been growing over the past few hours and so far the following has been identified:
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.
SSSE3 Required: Destiny 2 will not run on processors without Supplemental Streaming SIMD Extensions 3 (SSSE3).
PLEASE NOTE: We’ve seen a number of reports of crashes on CPUs that fall below our stated minimum specs (E.G. AMD Phenom II series). We are investigating the issue and will attempt to fix the crash, but these CPUs are below minimum spec and are not officially supported.
TRUMPET Errors: Players who are encountering TRUMPET errors on PC may attempt to work around this issue by changing Blizzard Region. We are investigating.
Clan Roster: We are aware of player reports describing the Clan Roster not appearing in Destiny 2 on PC. We are investigating this issue.
Continuous Sign On: We are actively investigating reports of players blocked from signing in to Destiny 2.
Windows Updates: Before playing Destiny 2 on PC, players should ensure that their version of Windows is up-to-date. The player experience may vary on versions of Windows that are not up-to-date.
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.
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.
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.
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.
Founder and Editor of PC Invasion. Veteran PC gamer of over 22 years.