JavaScript is required to use


Hilf uns, dir zu helfen.
Bearbeitet von BNGHelp4: 11/14/2017 9:10:24 PM

[BUNGIE] Destiny 2 PC Vital Information and Known Issues List

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 the 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 encounter issues other than what is listed below should report them to the [url=]#PCSupport[/url] forum. [b][u]KNOWN ISSUES[/u][/b] For a full list of confirmed Destiny 2 PC issues, please see: [spoiler] [b]-EMERGENT ISSUES-[/b] [quote] • [u][b]UPDATED: Performance Issues over time:[/b][/u] Issues causing a general performance degradation over time have been resolved in PC Hotfix Players who continue to encounter these performance issues that also have Oculus Rift positional tracking cameras should disconnect them from their PC and try again. Players who continue to encounter this behavior should report it to the PC Support forum. • [u][b]UPDATED: Hitching Post Hotfix[/b][/u] Issues causing general "hitching" or "stuttering" in framerate have been resolved in PC Hotfix Players who continue to encounter this issue should create a new forum post reporting the status of this issue. • [u][b]UPDATED: Clan Roster:[/u][/b] Issues causing Clan rosters to not appear in-game have been resolved in PC Hotfix • [u][b]UPDATED: SSSE3 Required:[/b][/u] As of 10 AM Oct. 30, Destiny 2 PC Hotfix was deployed, which removed this SSSE3 requirement. • [b][u]UPDATED: 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=] [/url] • [b][u]Beta Emblems:[/b][/u] We are aware that players who participated in the Destiny 2 PC Beta have not received the appropriate emblem within the Collection. We will provide additional information once available. • [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 accounts from their friends list. More info [url=]here[/url]. • [b][u]AMD Vega Crashes:[/b][/u] We are aware of player reported crashes at Mission Six for players using AMD Vega GPUs, and are working with our partners to investigate this issue. • [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 are actively investigating reports of players blocked from signing in to Destiny 2. [/quote] [b]-ORIGINAL LIST-[/b] [quote]• [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]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 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]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]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]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]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=]Network Troubleshooting Guide[/url].[/quote] [/spoiler] Additionally, players should visit our [url=]Destiny 2 PC Guide[/url] for more information on Destiny 2 on PC. [b][u]ERROR CODES[/b][/u] The following are errors codes that players may encounter at elevated frequency during the PC launch window. They are currently under investigation, and players may learn more about them at their respective help articles. [spoiler] • [url=]BEETLE[/url] • [url=]BUFFALO[/url] - See Known Issues listed above. • [url=]CABBAGE[/url] • [url=]NEWT[/url] • [url=]PINEAPPLE[/url] • [url=]RUTABAGA[/url] • [url=]TRUMPET[/url] - See Emerent Issues listed above. [/spoiler] [b][u]REPORTING ISSUES[/b][/u] When reporting hardware issues to the [url=]#PCSupport[/url] forums for Destiny 2, 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”. • Upload to preferred file sharing service and provide hyperlink to DxDiag file. [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.
#Help #pcsupport

Sprache des Beitrags:


Abbrechen Bearbeiten Einsatztrupp erstellen Posten Benimm dich. Nimm dir eine Minute, um dir unsere Verhaltensregeln durchzulesen, bevor du den Beitrag abschickst.

Es ist dir nicht gestattet, diesen Inhalt zu sehen.
preload icon
preload icon
preload icon