[b][u]TROUBLESHOOTING[/u][/b] Players experiencing an issue that is not listed below as a known issue should follow the troubleshooting steps found here: [spoiler] For the best experience, it is recommended that players update their drivers to their most recent versions, and accept any Windows updates that have yet to be applied before accessing Destiny 2 on PC. Additionally, as an initial troubleshooting step when encountering an issue, players should close and relaunch the Destiny 2 client and Blizzard application. For players who continue to encounter issues, it is recommended that players delete their existing CVARS.xml file. This file can be found in: [b] \Users\USER_NAME\Appdata\Roaming\Bungie\DestinyPC\prefs\ [/b] Note that when relaunched, the Destiny 2 application will generate a fresh CVARS.xml file. Players who continue to encounter issues unrelated to the known issues list below should report them to the [url=https://www.bungie.net/en/Forums/Topics?pNumber=0&tg=Help%20PCSupport]#PCSupport[/url] forum. When reporting hardware issues, players should provide [i]as much of the below information as possible[/i]: [quote][b]BattleTag[/b] [i](with numerical suffix)[/i] [b]Configuration Info[/b] CPU: GPU: RAM: GPU Driver Version: Operating System: • To find this information, press (Windows Key + R) to bring up the Run dialog box, enter this command “winver”, no quotation marks. DxDiag: • To find this information, press (Windows Key + R) to bring up the Run dialog box, enter this command “dxdiag”, no quotation marks. • Click on “save all information”. • Copy text from saved file to preferred third-party text dump website (i.e. PasteBin, DumpTxt) and share link here: [b]Issue Information[/b] Destination/Activity: Description: [/quote] Please note that players may not be provided actionable steps in response to their report, however all reported information is escalated to our internal teams for investigation. [/spoiler] [b][u]KNOWN ISSUES[/u][/b] For a full list of confirmed Destiny 2 PC issues, please see below: [Quote] • [u][b]Scan and Repair:[/b][/u] 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 [url=https://www.bungie.net/en/Help/Article/46501]here[/url]. • [u][b]BUFFALO Errors on multiple PCs:[/b][/u] 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. • [u][b]TRUMPET Errors:[/b][/u] 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 [url=https://www.bungie.net/en/Help/Article/46138]here[/url]. • [u][b]Fullscreen on Laptops:[/b][/u] Fullscreen mode is unable to be selected on some laptops. Affected players may use Windowed Fullscreen mode to work around this issue. • [u][b]Continuous Sign On:[/b][/u] 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. • [u][b]Flashing shadows in Pyramidion:[/b][/u] 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. • [u][b]Crash at Third Spire:[/b][/u] 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 [url=https://www.bungie.net/en/Help/Article/46407]here[/url]. • [u][b]Oculus Rift Users:[/b][/u] Players may experience lowered performance while Oculus Rift tracking cameras are plugged in. Unplugging the cameras from the computer may restore system performance. • [u][b]Windows Updates:[/b][/u] 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. • [u][b]SLI, HDR, and VSYNC:[/b][/u] 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. • [u][b]SLI Flickering:[/b][/u] 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. • [u][b]Crash after Task Switching:[/b][/u] 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. • [u][b]SAXOPHONE Errors when Launching:[/b][/u] 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. • [u][b]Idling to Title Screen:[/b][/u] 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. • [u][b]Login after Disconnects:[/b][/u] 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. • [u][b]Cursor in Tri-Monitor Configurations:[/b][/u] 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. • [u][b]Tri-Monitor Depth of Field:[/b][/u] 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. • [u][b]Windows 10 Game Bar:[/b][/u] 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. • [u][b]NumPad Binding:[/b][/u] Players are not able to bind controls to most NumPad keys. • [u][b]Screen Bounds on AZERTY Keyboards:[/b][/u] Players may receive an incorrect key prompt when adjusting screen bounds on an AZERTY keyboard. • [u][b]Cursor Stutter in Menus:[/b][/u] 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. • [u][b]IME in Fullscreen:[/b][/u] 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. • [u][b]Closing Application:[/b][/u] 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.\ • [u][b]Mouse does not reach bottom-right area of screen:[/b][/u] Some players may encounter issues with the mouse cursor hitting an invisible "wall" on the right and bottom portion of the screen. Players experiencing this should adjust the game resolution to match the PC resolution. • [u][b]Corporate and University Networks:[/b][/u] 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 [url=https://www.bungie.net/en/Help/Troubleshoot?oid=13602#University]Network Troubleshooting Guide[/url]. [/Quote] For a localized list of Known Issues on PC, see the [url=https://www.bungie.net/en/Help/Article/46684]Destiny 2 PC Known Issues Help Article[/url]. For additional gameplay known issues, please visit our [url=https://www.bungie.net/en/Forums/Post/239718019?sort=0&page=0]Curse of Osiris[/url] known issues round-up. Additionally, players should visit our [url=https://www.bungie.net/en/Help/Troubleshoot?oid=45899]Destiny 2 PC Guide[/url] for more information on Destiny 2 on PC.
RESOLVED ISSUES: [Quote] • [u][b]Hitching Post Hotfix 126.96.36.199:[/b][/u] Issues causing general "hitching" or "stuttering" in framerate have been resolved in [url=https://www.bungie.net/en/Explore/Detail/Update/46459]PC Hotfix 188.8.131.52[/url]. Players who continue to encounter this issue should create a new forum post reporting the status of this issue. • [b][u]Beta Emblems:[/b][/u] Players who participated in the Destiny 2 PC Beta had not received the appropriate emblem within the Collection. The fix is live and the emblem can be found in the emblem collection. • [u][b]Clan Roster:[/u][/b] Issues causing Clan rosters to not appear in-game have been resolved in [url=https://www.bungie.net/en/Explore/Detail/Update/46437]PC Hotfix 184.108.40.206[/url]. • [u][b]SSSE3 Required:[/b][/u] Destiny 2 [url=https://www.bungie.net/en/Explore/Detail/Update/46436]PC Hotfix 220.127.116.11[/url] was deployed, which removed this SSSE3 requirement. • [u][b]Performance Issues over time:[/b][/u] Issues causing a general performance degradation over time have been resolved in [url=https://www.bungie.net/en/Explore/Detail/Update/46437]PC Hotfix 18.104.22.168[/url]. Players who continue to encounter this behavior should report it to the PC Support forum. • [b][u]Vega GPU Crash on Mission “Six”:[/b][/u] Players who are encountering Vega GPU crashes when attempting to proceed through Mission “Six” may resolve this issue by downloading the most recent AMD Driver update here: [url=http://support.amd.com/en-us/download]http://support.amd.com/en-us/download [/url] [/Quote]