Key takeaways
- Regular image pauses while the frame rate appears stable: usually a shader-cache, background-process, storage, or driver problem.
- Stutter when entering new areas or seeing new effects: often shader compilation, asset streaming, or a storage bottleneck.
- Consistently low frame rates: graphics settings, resolution, thermal throttling, or insufficient CPU/GPU performance.
- Players teleporting, delayed damage, or “Contacting Destiny 2 servers” messages: a connection problem rather than rendering stutter.
How to Fix Stuttering in Destiny 2
To fix stuttering in Destiny 2, clear the shader cache, update or clean-install your graphics driver, reduce the settings that cause frame-time spikes, close overlays and background tasks, then cap the frame rate below your system’s normal maximum.
First, identify which kind of stutter you have
Not every hitch is caused by low graphics performance. Play the same short activity for several minutes—such as a patrol area, a Lost Sector, or a strike opening—and watch what happens:
- Regular image pauses while the frame rate appears stable: usually a shader-cache, background-process, storage, or driver problem.
- Stutter when entering new areas or seeing new effects: often shader compilation, asset streaming, or a storage bottleneck.
- Consistently low frame rates: graphics settings, resolution, thermal throttling, or insufficient CPU/GPU performance.
- Players teleporting, delayed damage, or “Contacting Destiny 2 servers” messages: a connection problem rather than rendering stutter.
Use the same location and camera movement for each change. Record the approximate average FPS and, more importantly, whether the game produces sudden pauses. A stable 90 FPS usually feels better than a fluctuating 130 FPS that repeatedly falls to 45 FPS.
1. Clear and rebuild the shader cache
Shader caches store compiled effects so the game does not have to prepare them repeatedly. A damaged or outdated cache can cause hitching after a Destiny 2 update, graphics-driver update, or major Windows update. The first play session after clearing it may stutter more while shaders are rebuilt, so do not judge the fix after only one minute.
NVIDIA graphics cards
- Close Destiny 2 and the Steam or Epic Games launcher.
- Open Windows Settings and search for Disk Cleanup.
- Select the system drive and check DirectX Shader Cache, then remove it.
- Restart Windows and launch Destiny 2.
- Play through the same activity for 10–20 minutes to allow the cache to rebuild.
If the problem began immediately after a driver update, you can also use the NVIDIA App or NVIDIA Control Panel to confirm that shader-cache storage is enabled. Avoid repeatedly deleting the cache every day; rebuilding it can temporarily increase stutter.
AMD Radeon graphics cards
- Open AMD Software: Adrenalin Edition.
- Open the graphics settings and choose the option to reset the shader cache.
- Restart the computer before launching Destiny 2 again.
- Allow one complete test session for shaders to compile.
On either platform, keep Destiny 2 on an SSD where possible. An SSD does not guarantee a fixed frame rate, but it generally reduces asset-loading pauses compared with an older mechanical hard drive.
2. Apply a stable graphics baseline
Before changing individual options, use a controlled baseline. Set the display to its native resolution and choose Fullscreen or the borderless mode that behaves most consistently on your system. Then apply the following starting values:
| Setting | Starting value | Why it helps |
|---|---|---|
| Texture quality | High; Medium with 4 GB VRAM or less | Reduces VRAM pressure without removing much image detail |
| Shadow quality | Medium | Shadows can create large GPU and CPU frame-time spikes |
| Depth of field | Off | Removes an unnecessary post-processing pass |
| Motion blur | Off | Improves clarity and avoids extra processing during camera movement |
| Wind impulse | Off if frame times remain uneven | Can reduce effects-related load in busy scenes |
| Render resolution | 100% | Keeps testing comparable; lower it only if the GPU is the limit |
| V-Sync | Off initially | Prevents it from hiding the source of a performance problem |
If the GPU is near 99% usage and frame time rises during explosions or crowded areas, lower shadows first, then render resolution or resolution scale. If GPU usage is low while the frame rate drops, reducing image quality may do little; investigate the CPU, background software, temperatures, and frame cap instead.
3. Choose a frame cap your system can actually hold
An uncapped frame rate makes the GPU run at maximum effort and leaves no performance headroom for effects, menu transitions, or asset streaming. Use Destiny 2’s in-game frame-rate limit where available, or a driver-level limiter if necessary.
| Display refresh rate | Suggested first cap | Use this when |
|---|---|---|
| 60 Hz | 58–60 FPS | You want consistent pacing and your system can sustain 60 |
| 120 Hz | 90 or 117 FPS | Your PC fluctuates below 120 or you use variable refresh rate |
| 144 Hz | 100–141 FPS | Your system cannot hold a reliable 144 FPS |
| 165 Hz | 120 or 162 FPS | You want headroom during combat rather than the highest menu FPS |
| 240 Hz | 160–200 FPS | Your CPU and GPU can maintain that range without repeated drops |
For a simple calculation, a 144 Hz display refreshes every 6.94 milliseconds, while 60 FPS produces one frame every 16.67 milliseconds. If your PC normally reaches 130 FPS but falls to 55 FPS during effects, a 100 FPS cap may feel smoother because it leaves roughly 23% of the uncapped average performance as headroom. The ideal cap is the highest value your system can sustain in the heaviest scene, not the number shown in an empty room.
Enable FreeSync or G-SYNC-compatible variable refresh if your monitor and GPU support it. A common starting point is a cap 2–3 FPS below the display’s maximum refresh rate, with V-Sync configured consistently rather than mixing several conflicting limiters.
4. Update or clean-install the graphics driver
Driver updates can fix game-specific issues, but installing a new driver over a damaged configuration can preserve the problem. Download the current driver for your GPU from NVIDIA or AMD, choose the clean-install or factory-reset option when offered, and restart Windows afterward.
If stuttering began immediately after a driver update, test the previous stable driver instead of assuming the newest version is best. Do not change the driver, shader cache, and every graphics setting at the same time; make one change, repeat the same activity, and compare frame pacing.
5. Remove background interference
Overlays and monitoring tools can interrupt a game during capture, notification, or hardware polling events. Temporarily disable:
- Steam Overlay and the Xbox Game Bar.
- Discord overlay and browser hardware-acceleration windows running in the background.
- NVIDIA or AMD recording overlays.
- RGB-control, motherboard-monitoring, peripheral, and aggressive antivirus overlays.
- Cloud-sync clients, large downloads, launchers, and video streams.
Open Task Manager while Destiny 2 is running. Look for CPU usage that repeatedly spikes above 90%, memory use approaching the installed total, or a disk sitting at 100%. Close unnecessary programs and pause downloads. If RAM is nearly full, Windows may page data to storage, producing hitches even when the GPU appears underused.
6. Check temperatures, power, and Windows settings
Monitor CPU and GPU temperatures, clock speeds, and utilization during a stutter. A sudden clock-speed drop can indicate thermal or power throttling. Clean blocked vents, make sure the laptop is plugged in, and select a balanced or high-performance Windows power mode appropriate for your hardware. On laptops, test with the manufacturer’s performance mode enabled and the dedicated GPU selected for Destiny 2.
Keep Windows and chipset drivers current, but avoid optional hardware utilities that constantly poll sensors if disabling them removes the hitch. Also check that the page file is enabled on an SSD with adequate free space. Destiny 2 itself may not use a large amount of memory continuously, but Windows and other applications still need virtual-memory headroom.
7. Use this situation-to-fix matrix
| What you observe | Most likely first action | Next test |
|---|---|---|
| Stutter began after a game or driver update | Clear the shader cache | Replay the same activity for 10–20 minutes |
| GPU usage stays near 99% | Lower shadows and render resolution | Check whether frame time improves during combat |
| GPU usage is low during drops | Close overlays and check CPU, RAM, and disk usage | Test with a lower frame cap |
| Only the first run after launching stutters | Allow shader and asset caches to rebuild | Compare a second run without clearing anything |
| Enemies teleport or damage arrives late | Test the network connection, not graphics settings | Use wired Ethernet or troubleshoot Wi-Fi and packet loss |
Final verification checklist
After making changes, restart Destiny 2 and repeat the same route. Compare the frame-rate cap, GPU utilization, temperatures, and the frequency of visible hitches. The fix is successful when frame times remain consistent during combat and area transitions, not merely when the peak FPS number increases.
- Shader cache cleared once, then given time to rebuild.
- Graphics driver clean-installed or rolled back if the issue followed an update.
- Shadows and expensive effects reduced before sacrificing resolution.
- Overlays, downloads, and monitoring utilities tested in an isolated state.
- Frame rate capped below the system’s unstable maximum.
- Temperature, clock speed, CPU usage, RAM, and disk activity checked during a hitch.
