JavaScript is required to use Bungie.net

Service Alert
Destiny 2 will be temporarily offline tomorrow for scheduled maintenance. Please stay tuned to @BungieHelp for updates.

Forums

1/20/2021 6:38:55 PM
5
Bungie another thing. Turning on force_enable_multi_threaded_render_submit fixes the issue but causes bad shadow flicker. Why did you guys think it had something to do with lighting on tangled shore causing the issue? Its a CPU issue. I really hope this message gets to someone. When force_enable_multi_threaded_render_submit is off I get 20-60fps and my CPU does not boost and only 2 cores are used. When force_enable_multi_threaded_render_submit is turned on I get 90-120fps but then I also have horrible shadow flicker but my CPU is boosting correctly and all cores are being used. Proof of Low CPU usage. On - force_enable_multi_threaded_render_submit https://imgur.com/6khJjZh Off - force_enable_multi_threaded_render_submit https://imgur.com/eJ4YGaq Bungie please show this to one of the bug fixing guys!!
English

Posting in language:

 

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

  • Its only partly a CPU issue. "force_enable_multi_threaded_render_submit" is and has been a beta feature for years, because it is essentially left over code from porting the code from the 8th generation consoles. both the Xbox one and ps4 consoles, have it enabled, unsurprisingly because the bulldozer era jaguar cores wouldn't have a shit show of running the game any other way. but the reason there are no issues on those versions of the game is because of console specific hardware optimizations, and fixed cpu cycle speed as well as predictable behavior. As such running code on different threads the timing is all synchronized, which means the game runs without any noticeable graphical issues. The difference on PC being a wide array of different configurations and architectural design, they cannot predict certain behaviors such as clock boosting across different threads on different CPUs. the core issue is that the code has been written to execute in parallel on a set configuration, where everything runs the same and is synchronous in execution. eg. shadow draw calls are being executed by a separate thread to other core game functions. when the executions aren't synchronized u get the flickering. TLDR: Because Bungie couldn't be bothered back in 2017 we got an flawed port that was deemed acceptable because it runs on a few threads at competent performance. After all Destiny Runs on a modified Halo Reach engine, which in itself a modified Halo 3 Engine. Which Runs on a 3-Core 6-Thread CPU, albeit a PowerPC based architecture, of the Xbox 360. The Current issue GPU Draw call related. We see much larger issues on AMD Gpus because Bungie Consider owners to be second class citizens and they don't test on platforms running that hardware. But there are now issues for Nvidia users also because the current build was pushed out rushed. (just look at all the seasonal quest bugs) but less so because that's what they develop on, Intel Cpus, and Nvidia Gpus.

    Posting in language:

     

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

  • Either way Bungie dropped the ball on this one. Cyberpunk 2077 runs better than Destiny 2 atm, that says a lot. I'm just tired of waiting and I'm tired of trying trying fixes.

    Posting in language:

     

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

  • Agreed at least CDPR is getting sued. Bungie hides behind their POS Lazy Ass SLA, that likely isn't legally enforceable anyway. Certainly not in Australia, those guys take no shit. probably not in the EU either.

    Posting in language:

     

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

  • Edited by Sailor Venus: 1/27/2021 9:57:43 PM
    Ryzen 5 3600 with RX5600XT Multithread Render Enabled (Lastest driver 21.11.1): Framerate drops to 46-50 in EDZ, GPU load 65% and not above Multithread Render Disabled (Old driver 20.4.2): Framerate drops to 65-70 in EDZ, GPU load 80% and up. This problem CPU+GPU and possible solution should be for both and not only CPU. However, if fix GPU, it will give more FPS than solution for CPU. P.S. Or replace game API on DirectX 12 that is best solution.

    Posting in language:

     

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

  • Have you tried disabling SMT (HyperThreading)? That works in my case, but I have an Intel CPU.

    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