JavaScript is required to use Bungie.net

Help - Destiny 2

Help us help you.
Edited by drakonnan: 8/10/2023 2:08:40 PM
1

(Bug) Destiny 2 only uses 2 CPU threads

PLATFORM: Steam SYSTEM INFO: CPU: i5 11400 @ 2.6GHz (12 cores) GPU: RTX 3060 RAM: 16GB GPU Driver Version: 536.99 Studio OS Version: Windows 10 Pro 22H2 19045.3324 ISP Provider/Speed (upload/download) / Connection Type (LAN or wireless): 50mbps down DxDiag: I'd rather not publicly post this ISSUE: I'm experiencing 1-2FPS on the orbit screen, when in the past, the game runs smoothly for me. CPU usage is at 16-17%. GPU usage is negligible REPRO STEPS: 1. Boot Destiny 2, and navigate to the orbit screen. Close all other apps. 2. Observe abysmally low fps 3. Open task manager (whilst keeping D2 running) 4. Observe the CPU usage by destiny2.exe 5. Set the affinity to cores CPU0 and CPU1 only for destiny2.exe. 6. Observe the CPU usage by destiny2.exe again 7. Set affinity to CPU0 only. 8. Observe CPU usage again 9. Set affinity to cores 0, 1 and 2 10. Observe CPU usage again ACTUAL RESULT: - 1-2 FPS on the orbit screen. Background music works fine - 16-17% CPU usage (i.e. 2 cores out of 12). Negligible GPU usage - when affinity locked to cores 0 and 1: No improvement in FPS. CPU util for those two cores is near 100% - when affinity is locked to core 0 only: game freezes more, and the audio starts to stutter. CPU util is 100% for core 0 - when affinity is locked to 3 cores: performance is the same as the start. CPU util is higher for cores 0-2 than the others, but not that high EXPECTED RESULT: - 165 FPS usually on the orbit screen - more than 17% CPU usage Notes: I tried these things, and none of them worked to fix the issue: - restarting the computer - installing the latest windows updates - installing the game-ready version of graphics driver 536.99 - installing the studio version of graphics driver 536.67 - enabling/disabling HDR - enabling/disabling Gsync - enabling/disabling v-sync in-game - enabling/disabling Xbox game bar - enabling/disabling Windows "Game Mode" (Windows settings -> Gaming -> Game Mode) - enabling/disabling "Hardware Accelerated GPU scheduling" and "Variable Refresh Rate" (Windows Settings -> Gaming -> Additional Graphics Settings) To isolate the issue, I also tried other games, in particular, Halo 3 (both base and ODST), Halo Reach, and Halo 4 (all from Halo MCC on Steam), as I understand these are predecessors of D2's engine, and all of which support multithreading: - in H3 and Reach: the very first encounters of Sierra-117 and SwordBase cause the game to lag. This lead me to believe that it's a CPU issue. I have never dropped frames on these games before. - in H4: looking at the horizon (as opposed to looking at the ground) is enough to cause lag. I have never dropped frames on H4 games before. - Halo CE runs fine on original graphics. On anniversary graphics I'm seeing 20fps during encounters - For all of these MCC games, I'm seeing only 25% CPU usage when the fps drops - in Halo Infinite: No issues. This game ran as well as before - for non-Bungie/343 games: No issues
English
#Help #pcsupport

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