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?

To add to my info - Dungeon, prophecy was ok, 90% of the time, only right by final boss it had typical 100-110fps drops, looked like some npc animation cpu issue. - lawles frontier basecamp was ok, -Cosmodrome also ok -EDZ with new live event was ~100-120fps and jittery, so it's something with new event too. - tower is mixed bag, has more fps drops then not. Im forcing driver vsync, driver fps limiter doesnt work anymore *fullscreen optimizations off in windows, *new beta steam app ingame vsync and fps limiter have issues and cause extra negative fps drops Traversal framepacing stutters seem to be gone.

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).

Turning off steam overlay does nothing. Ive had it off forver. Removing proper exclusive fullscreen destroyed the frame pacing and the latest update nail in the coffin to it. Used to be locked 240. EoF and removal of exclusive fullscreen saw poor frame pacing and the last tuesday update has destroyed fps and 1% lows.

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.

didn't fix it today, yall still gonna fix this or nah?

Team I'm sure you're aware at this point the frame pacing issue is only on steam. Someone else mentioned it but the very least you guys could do is allow DLC to be played on any cross progression platform so or at the very least Xbox / Epic so steam users can can switch and continue to enjoy the game. Thank you.

Dear Team, I've seen there's no mention of this issue in today's patch notes, this is still happening and making the game unplayable at times. If no ETA on when or if this will be fixed, can the option to transfer our DLCs to other platforms (at no cost..e.g Free of charge) be opened up as a solution - so we can move to either Epic or Windows (Xbox) platforms to play the game without huge framerate drops. Cheers.

https://youtu.be/JrvI-TRovBw https://pastebin.com/UgHPKbki This issue seems to only affecting Steam. No issues on Epic games. I notice these issues more when Im in any PVP mode.

I’ve tried both the Epic store version and XBOX PC App versions and the framepacing issue is not affected with those launchers, only Steam.

The game is still running very poorly for me. The game has run perfectly on my PC for years, up until the first hotfix after MoT. It would be a shame to break the performance of the game with one of the last ever updates and then not fix it. I would hate for my final memories of this game to be spoiled by this.

Game is unplayable in this state. No statement in the patch notes Marathon has 3k players Gg