JavaScript is required to use Bungie.net

Forums

Edited by kpsingh: 6/15/2021 7:57:28 PM
2
EDIT: I followed every bit in https://www.gamepretty.com/destiny-2-amd-fps-guide-2021-steam-version/ and while I was not very hopeful it would work. It brought back my FPS but produces artifacts in the ship / launch screen and Tower and unfortunately also Gambit [this is super disappointing]. It seems like this is particularly affecting bright areas (like the gambit bank), when one goes to Zvala in the tower and only of the loading screens with the ship (no the one with purple clouds flying around). System Profile: CPU: Threadripper 3970x (64 Threads / 32 cores) GPU: AMD 6800XT (XFX MERC) RAM: 128GB (3200 MHz) Power Supply (850W) Based on what the suggestions of fixes that I see, bungie is trying to tell us that they want to keep our CPUs free (remove background processes overlays, reduce sound quality etc) so that their renderer can schedule as quickly as possible and, this is assumption on my side, dispatch the frame for rendering to the GPU. It seems to corroborate well with some users who reported better FPS with screen flickering when enabling [i]force_enable_multi_threaded_render_submit[/i] in their [i]cvars.xml[/i]. I also see when reducing the sampling rate of my GPU usage that the utilization spikes up to 99% and then falls down pretty much to 0. Such spiky load again points to a sub-par renderer. While reducing background processes might help their single rendering thread to schedule on a system with low parallelism it certainly does not help on my system. I have a Threadripper 3970x (64 threads). The only thing that, in this scenario, can marginally help is overclocking the CPU or using a CPU with higher clock speed. But I think Bungie really needs to focus on fixing their multi-threaded rendering. Bungie: I would be willing to help you figure this out :)
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon