Destiny 2 Known Issues List Updated – PC, Crucible, And Public Space Issues Targeted

Now that Destiny 2 is officially out on all platforms after the release of the timed launch of the PC version, Bungie can now focus on what’s ahead. With a new expansion on horizon and the team amping up for all the new goodies season 2 will bring, the developers are still hard at work with their weekly updates letting players know what they are working on and what issues they are aware of.

This week’s known issues understandably revolve around PC. Like any MMO, there are always launch issues to be addressed; especially on a large player-base game. This is everything in Bungie’s report for the week of 10/26:

Destiny 2 PC Launch: Known Issues

Since the release of Destiny 2 on PC, we have been recording verified issues within the Vital Information and Known Issues thread. The following is a list of confirmed issues that have come up since launch:

• 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.
• AMD Vega crashes: We are aware of player-reported crashes at Mission Six for players using AMD Vega GPUs, and are we working with our partners to investigate this issue.
• Clan Roster: We are aware of player reports describing the Clan Roster not appearing in Destiny 2 on PC. We are investigating this issue.
• Error codes: BUFFALO, TRUMPET, and CHIVE knowledge base articles have been updated with information relevant to issues players have encountered with Destiny 2 on PC.
• Beta emblems: We are aware that players who participated in the Destiny 2 PC Beta have not received the appropriate emblem within their Collection. We will provide additional information once it is available.

Reporting PC Issues to the #Help Forum

If you are encountering any issues not listed within the Vital Information thread, we advise posting a report to the PC Support forum on #Help. When reporting an issue, please include the following:

• BattleTag with numerical suffix
• Configuration info: CPU, GPU, RAM, GPU driver version, and operating system
• DxDiag: Steps on how to provide this may be found within this thread under “Reporting Issues”
• Issue information: Destination, activity, and description of the issue that occurred.

What’s Ahead

To prep for the weekly reset and hotfix issued, here’s what Guardians can expect to be fixed here shortly in-game short preview form (full list goes live when the update hits): 

General

• Fixed an issue with collision detection on the Bureaucratic Walk emote
• Fixed an issue causing players to encounter empty public spaces too often in free roam

Crucible

• Updated Mercy Rule settings to allow Mercy to activate slightly later in the match, allowing a wider range of scores to trigger it.

Clash

• Reduced score limit to 50 (was 75)

Control

• Reduced score limit to 90 (was 100)
• Reduced influence that enemy-controlled zones exert over the spawning system

Survival

• Reduced round time limit to 2 minutes (down from 3) 
• Reduced life count to 6 (down from 8)

Supremacy

• Increased score-to-win to 70 (up from 50)
• We now grant one point for defeating an enemy Guardian
• Adjusted the influence that enemy crests have on the spawning system