{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
6/1/2023 10:19:10 PM
4
Destiny 2 still has major stuttering issues on AMD graphics cards.
Every time I download a new AMD graphics driver, it is like my computer has to relearn Destiny 2 again. Every ability that I have not seen in game since updating my drivers stutters the game. Every destination I have not visited, stutters the game. It stops stuttering after hours and hours of playing, when the game finally gets "used to" Destiny again. It is incredibly frustrating, and it makes the game feel almost unplayable until it stops. I don't have this issue with ANY other game.
I have tried everything, setting low latency to 0 in the cvars file, editing AMD Radeon settings, tuning my GPU, reinstalling Destiny 2, playing with different graphics settings in Destiny 2, and even completely uninstalling and reinstalling all of my graphics drivers.
I understand Bungie has mentioned AMD GPU issues in the past, I hope work is still being done to improve PC performance.
I had a RTX 3070 before upgrading to an AMD RX 6900 XT and the Nvidia card had no problems. I get higher frame rates in every game, but the stuttering in Destiny 2 is horrible, which is unfortunate because it is my most played and favorite game.
-
1 ReplyEdited by Dessart: 6/2/2023 8:43:20 PMI was just going to report this same issue, but then I saw this thread. I recently (just before Lightfall) upgraded from a 1060 to a 6800XT and just like it was described, the game starts compiling shaders seemingly from scratch after *every* driver upgrade. It's not great. I'd assume shader data has to be compiled by the game every time a new set of drivers comes it, but I wonder if it would be possible to add a way to pre-compile at least a good amount of them on the character selection screen, like other games do. Not sure what works differently between AMD and NVIDIA, but I never had this issue when using the 1060. I reported this situation to AMD through their software just in case it's something on their end. That's also why I wrote here, just in case this is something that shouldn't be happening. Thank you!
