{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
1/13/2021 10:42:24 PM
3
I am having massive issues in every part of the game. Last time I played (early Decemeber) the game ran smooth as butter and looked amazing. Now I am getting massive FPS drops in the menus (drops to like 1). I can't even load into the Cosmodrome, it just closes my game and throws me to desktop. I managed to load into Tangled Shore but my fps drops to 1 - 5 and freezes up every second. The game is literally unplayable for me now. I tried.
My specs are
i7-6700
16gig ram
GeForce 1080 FTW
All my drivers are up to date. I just re-installed and it's still not working. The game ran so beautifully not even 2 months ago. Now I can't even load into the Cosomodrome. I can't do anything. I have nearly 500 hours on Steam alone. I've purchased every expansion since launch on PC and PS4. I've put a lot of money into this game and now I can't even play it. Can someone from Bungie please help me out here? I'm at my wits end.
I want to finish up this season but the game is literally unplayable for me.
English
-
Monger, the tip I have is to go into the NVIDIA Control Panel, and within "Manage 3D Settings", select "Program Settings", then under "Select a program to customize", open the dropdown list there and select destiny2.exe. Once you have that selected, in the list below, scroll until you see an option named "Shader Cache" and to the right of that, turn Shader Cache off. I was having issues earlier, especially with the Dreaming City, and found that turning that option off helped quite a bit, and for me I'm running a 2060, so this should help you as well. Hopefully Bungie fixes the issue with the Shader Cache so we can have it enabled for more optimized performance instead of worse performance.
-
Holy crap, it worked! I loaded into the cosmodrome. Thank you soooooo much!!!
-
You're welcome. I found this solution in a different help thread, so I tried it, and it worked for me. Apparently it seems it's just an issue with the Shader Cache optimization.
