DXDIAG: https://pastebin.com/8scjfDC3 Video: https://imgur.com/a/VNG6pw9 Atm the video is quite blurry due to compression and may be unusable. https://drive.google.com/drive/folders/1lh3EpA0Lf7g_37jSduw0qNIUDpYQmnZM?usp=sharing I know you guys specifically said to not use Google Drive, but this data is worth it in this case imo. Platform: PC · Location tested: Moon (Sorrow's Harbor public event) · Reproduced across multiple destinations Summary Since the most recent Tuesday patch, frame rate drops significantly whenever dynamic entities (enemies, spawned objects) are in view. Looking at a wall or corner with no entities restores frame rate to near-normal. The issue is not GPU-related — profiling confirms it is a CPU-side regression, most likely in how entity state, draw calls, or memory is handled per frame. Steps to reproduce: Load into any destination with ambient enemy spawns (Moon Sorrow's Harbor confirmed; reproduced on other destinations) Face toward a group of enemies or wait for a public event to begin spawning mobs Observe frame rate drop and stutter — frame time spikes visible even with FPS cap disabled Turn camera to face a wall or static geometry with no entities in frame Observe frame rate recover significantly Measured impact — PresentMon (31,662 frames, ~5 min session) 122 - avg FPS 30 - 1% low FPS 97.8% - stutter frames: CPU bottleneck 6.6ms - avg GPU time on stutter frames 29.4ms - avg CPU busy on stutter frames 70% - avg GPU utilization (not saturated) On frames where frame time exceeded 16.67ms, CPU busy time averaged 29.4ms while GPU time remained at 6.6ms — the same as smooth frames. The GPU was not the bottleneck. The 1% low FPS of 30 against an average of 122 indicates severe periodic stalls rather than a sustained throughput issue. HWiNFO sensor data: GPU temperature peaked at 58°C with no thermal throttling detected. GPU power limits were not reached. GPU shader clock was actively scaling up during the drops — the GPU was trying to find more work and wasn't being given it. Max single-thread CPU utilization hit 89% during heavy-entity periods, averaging 72% sustained. Windows Performance Recorder (WPR) — CPU Usage (Precise): A 30-second WPR trace (CPU Usage Precise) was captured during active stutter. destiny2.exe process (PID 45048) showed the following on its primary hot thread (TID 58,772): Thread 58,772 CPU cycles used: 100,741 Ready time (µs): 792,672,700 ← thread wants to run but can't get scheduled Waits (µs): 4,460,807,600 Call stack root: └─ ntdll.dll <Symbols disabled> CPU cycles: 98,376 / 100,741 (97.7% of thread cost) Ready time: 780,288,500 µs ├─ destiny2.exe <Symbols disabled> — 1,193 cycles ├─ ?!? (unresolved module) — 1,152 cycles ├─ GameOverlayRenderer64.dll — 5 cycles └─ ntoskrnl.exe — 13 cycles The thread's Ready time (792ms out of the trace window) is far larger than its actual CPU execution time, indicating the thread is being queued by the Windows scheduler faster than CPU cores can service it. This is consistent with either a high-frequency polling/wake-up loop or a lock contention point introduced in the patch. Because Destiny 2's symbols are private, the exact game-side function calling into ntdll.dll cannot be resolved from this trace — but ntdll at this volume typically indicates heap allocation pressure. (RtlAllocateHeap/RtlFreeHeap) or critical section contention (RtlEnterCriticalSection). Hypothesis: The patch likely changed something in how entity state is batched, allocated, or synchronized per frame. The directional nature of the bug (camera angle matters, not player position) points to draw call submission or visibility culling as the trigger ; the game is doing significantly more CPU work per frame when non-static entities are in the view frustum. This was not the case before Tuesday's patch. Possible causes: increased per-frame heap allocations for spawned entity data; a new or unintentionally un-parallelized lock on the render or simulation thread; a change to entity tick rate or LOD evaluation frequency. System specs CPU: 8-core (16 threads), boosting to 5215 MHz · GPU: AMD Radeon (RX 7000 series inferred from HWiNFO MCD sensor layout) · RAM: ~36GB in use during session · GPU VRAM: ~4GB allocated to Destiny 2 · OS: Windows (confirmed via ntdll/ntoskrnl in trace).

I've installed Epic version and recorded a comparison. STEAM: [url]https://www.youtube.com/watch?v=SskNb3IYsgc[/url] EPIC: [url]https://www.youtube.com/watch?v=LiXG2dcLQ-A[/url] DXDIAG: https://pastebin.com/77cyEu7F CVAR: https://pastebin.com/ZQAQpweJ Steam version is stuttering even when stationary and not moving the mouse. What is performance floor for Epic version, is performance ceiling for Steam version. The Performance Overlay is from AMD Adrenaline. It has "Micro Stutter" tracker, described by AMD as: [quote]Micro Stutter Rate measures how many frames exhibit an instantaneous variance compared to the average frame rate over a 1-second sampling period.[/quote] [b]STEAM:[/b] FPS: ~80 1%: ~40 Micro Stutter: Constant 3-5%, up to 10% GPU: Hovers around 60%, constantly drops down to 30-40%, never goes above 90% [b]EPIC:[/b] FPS: ~120 1%: ~90 Micro Stutter: 0% GPU: Properly stays at 90%+ [b]My PC Spec:[/b] [i]SYS: Windows 10 CPU: AMD Ryzen 5 5600 GPU: AMD RX 6700 XT 12 GB RAM: 16 GB SSD 2TB 1440p V-Sync OFF, FreeSync ON[/i] Fullscreen Video Setting in Game Video Options. Fullscreen optimizations in properties of destiny2.exe - left default, meaning ON. (It stutters with OFF too.) Steam shaders: OFF Steam hardware optimization for web stuff: OFF Steam Input: OFF Steam Overlay: OFF (No solution helps) Settings between Epic and Steam versions are the same, same cvars file from Destiny2 AppData folder, that is shared between the two. Wish you the best guys, thanks for the game.

My specs: 12th Gen Intel(R) Core(TM) i7-12700H - RAM: 16 GB NVIDIA GeForce RTX 3050 - VRAM: 4 GB I turned off the steam overlay and it did not help at all. I have not turned it back on. I cant break 60 FPS anywhere except in orbit, where my frames reach 120. PVP is unplayable even after i limited FPS to 36 i still get micro stutters and and frame drops, that are as low as 26. I am a returning player. the only activities i finished were the renegade and light fall campaigns they ran okay, but the new renegade weapons every time i reload one of them my fps would drop low to 26 especially when there are enemies present. I tried playing the final shape campaign but it runs too poorly to even slog through, Most encounters in the final shape have fps reader stuck at 26 frames zooming in with a sniper causes the game to stutter even worse then it already is. normal campaign sections and the dungeons that I have played mainly grasp of avarice and Equilibrium ran okay. I am upset, because I was so excited to return to the game, and I even bought all of the DLCs, but i cant even play some of them like the final shape, because the game runs too poorly. Please update us it has been nearly 3 weeks.

I can confirm that this is STEAM issue ONLY. Tried every possible updating, deleting drivers etc, updating bios and every damn steam disable controller, overlay, delete shaders etc, nothing helped. Then I enabled cross save within bungie account and downloaded Destiny 2 trough Epic games and man the game works SMOOTH again in PVE and PVP both. If you do the switch you dont loose your character and the progress if you enable the cross save, all gear, god roll weapons etc are with you. The minus thing is that you need to buy licenses again if you wanna play Trials etc. Renegades is onyl 20 euros anyways so not a big money for good game. 69 euros if you want all, not expensive either. I made the switch and can now enjoy again. Wouldnt keep my hopes high that steam gets fixed anytime soon so. I am on older PC with Ryzen 5 CPU and RX 580 GPU, but still Destiny has worked smoothly with low/med settings. Within the update 9.7.0.2 these major stutters and fps losses started. This all with steam, not with epic games.

Started a new topic: -- GDPR: removed by user request --(1 Reply)

So is this ever getting fixed or are Steam users just outta luck forever?