{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
2/22/2018 3:27:56 AM
3
Destiny 2 starts with sound but no visuals
BattleTag acgh#1170
Configuration Info
CPU:Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 2592 Mhz, 4 Core(s), 8 Logical Processor(s)
GPU: Nvidia GeForce 960m
RAM: 16gb
GPU Driver Version:
Operating System: Windows 10 1709 (OS Build 17074,1002)
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:https://pastebin.com/KFU19mbC
Issue Information
Destination/Activity: Startup of Destiny 2
Description: When I start the game, it shows as a windowed screen that is all black. Sound plays in the background, and hitting enter works as it should. Making the noise before it loads the character screen. I am unable to see anything, or interact with the character select. I have uninstalled and reinstalled all my display drivers, and windows. Once the removal and installation of my intel and nvidia drivers helped solve this problem. Now the problem is back and the same solution isn't cutting it.
-
8 RepliesHi, Thank you for your report. This display issue may be resolved by deleting CVARS.xml. To clear CVARS, players must: [quote] 1) Close Destiny 2 2) See file directory: \Users\USER_NAME\Appdata\Roaming\Bungie\DestinyPC\prefs\ 3) Select and delete the CVARS.xml file in this directory 4) Relaunch Destiny 2 [/quote] PLEASE NOTE: When relaunched, Destiny 2 will generate a fresh CVARS.xml file. This will revert all custom player settings in Destiny 2 to their defaults. Players may readjust these settings to their preference by relaunching Destiny 2 and visiting Settings after selecting a character. If you still encounter this issue after following these troubleshooting steps, please reply back to this post.
