Awful performance issues with brand new RX 6800 GPU
With all the other issues going on at the moment I doubt this will get much attention, but this needs to be talked about more. Destiny 2 is by far the worst game to play for anyone who has an all-AMD build.
And it has been this way ever since the launch of Beyond Light.
So, about 2 weeks ago I finally bought a new GPU - a brand new Sapphire RX 6800 Pulse. (For context - My previuos GPU was a GTX 1060 6GB)
With such an upgrade you'd expect a crazy leap in performance, right?
Well, in literally any other game, yes! (duh)
In Destiny 2, however, it's the oppsite.
So, how does the performance compare to the old GPU? 30% increase in performance? 50%??
Well, depends on the activity.
As long as you're in orbit everything is fine. Huge increase in FPS compared to the old GPU.
But the moment you load into literally ANY activity/social space all your hopes and dreams die (just like your framerate), for you are now faced with the harsh reality that you've wasted $450.
Here's some of the issues I have encountered so far -
- [b]Lag Spikes[/b]. "awful" would be a nice way of putting it. The lag spikes I have been getting almost non-stop ever since installing the GPU are so awful I just outright stopped playing the game. (have not uninstalled. yet.) After some testing I figured out the lag spikes appear only when the game is trying to render new entities (that includes bullets, grenades, supers, rockets, explosions, dying, etc.). For that reason, activities such as Crucible (especially Mayhem) are literally unplayable. The game rarely stays above 30 FPS during any sort of combat.
- [b]Graphical/visual glitches[/b]. Altough I have only seen 3 cases with my eyes, I wouldn't be surpried if there are more I am missing.
-- first two were graphical glitches where there would be a black line across the entire screen, that was there for about a couple frames. I have not seen any for a while now, so I guess at least those are gone
-- the final (and big one) is to do with the foliage shadows. If you disable wind impulse the shadows of every single plant/tree/grass start flickering (A LOT). Disabling shadows fixes the issue, but I really don't think players should have to lower their graphics settings simply because the plantlife is having a stroke.
- [b]The "force_enable_multi_threaded_render_submit" setting in the CVARS file[/b]. I have heard NVidia users also can't turn this on, but I am guessing they just don't need it the same way AMD users do. I could be wrong about this but I am pretty sure this one setting could fix a lot of the issues I am facing. [i]ahem [/i]lag spikes [i]ahem[/i]
[b] Here's everything I have done to [i]try[/i] to improve my performance: [/b]
- Driver update
- Driver downgrade
- Both of the above but with slimmed versions of the drivers
- Deleting the driver with DDU multiple times and reinstalling them
- Reinstalling Windows
- Reinstalling Destiny 2
- Changing my graphics settings
- Switching to a more optimized and stripped down version of Windows 10
- Checking which BIOS my GPU is using (It is in performance mode)
- Disabling every overlay possible
- Deleting CVARS
- Disabling shadows (almost) completely through CVARS
- crying
- Disabling Resizable BAR / SAM
- Enabling Resizable BAR / SAM
[b]Here's all my hardware:[/b]
- GPU: Sapphire RX 6800 Pulse
- CPU: AMD Ryzen 5 2600 @3.85GHz
- RAM: Kingston HyperX Fury 16GB 3200MHz
- PSU: EVGA 850 GQ 80+ Gold 850W Power Supply
- Motherboard: ASUS TUF GAMING B550-PLUS
Lag spikes: from what you wrote, that sounds like your Shader Cache keeps compiling, which shouldn't happen after the very first time you launch the game after a driver update/change.
Graphical glitches: black lines across the screen (like also black points or patches) may indicate VRAM overclock or overheating; is the video card clocked default?
The Wind Impulse off glitch has been around since WQ, I suggest you leave the option on instead of turning off shadows, the performance impact is negligible after all.
The force_enable_multi_threaded_render_submit setting has never worked fine for anyone, as far as I know. I don't even know why it was left in the CVARS.xml file to begin with. Destiny 2 is indeed very CPU-bound (not uncommon with DX11 titles).
Steam, Xbox for PC or Epic?
When the game is running, what's the percentage of GPU usage? Temps?
Disabled ULPS in the registry?