Destiny 2 Monument of Triumph (9.7.0) Best Settings 2026

Destiny 2's Monument of Triumph update (9.7.0) shipped with subtle but impactful changes to LOD pop-in distance, texture streaming budget allocation, and shadow cascade behavior. Players with GPUs under 12GB VRAM reported immediate stuttering in the new Tower area, and even high-end cards saw 15–25 FPS drops in the Pale Heart destination compared to Episode: Echoes builds. Bungie's patch notes buried the rendering changes under "improved visual fidelity," but the real story is performance regression if you don't adjust your config.

The good news: three specific settings account for 80% of the performance delta, and rolling them back costs almost nothing in visible quality during actual combat. This guide walks through the exact adjustments that restore pre-9.7.0 frame rates without sacrificing competitive visibility or breaking the new shader effects Bungie added to Monument of Triumph exotic armor. You can also run a free hardware-specific playbook that auto-tunes every setting for your GPU and monitor refresh rate.

What Changed in Update 9.7.0

Bungie pushed three rendering-layer changes in 9.7.0 that affect frame pacing and VRAM allocation. First, the LOD transition distance for environmental geometry increased by roughly 30% — rocks, columns, and decorative assets in Pale Heart zones now hold high-poly models farther from the camera before swapping to lower-detail meshes. This looks slightly sharper at distance but forces the engine to manage more triangles per frame. Second, texture streaming now pre-loads one additional mip level for character armor and weapon models to support the new Monument of Triumph shader system, which uses higher-resolution normal maps. On GPUs with 8GB VRAM or less, this causes visible texture pop-in as the streaming system thrashes between mip levels.

Third, shadow cascade distribution shifted to bias the highest-resolution cascade closer to the player — this tightens shadow detail on your Guardian's armor (important for the new exotic glows) but pushes mid-distance shadows into a lower cascade tier, creating a subtle performance hit in busy Crucible maps where 12 players congregate. The Tower social space compounds all three changes, because it now spawns 10–15% more decorative geometry (banners, monument pedestals) and bumps player density cap from 24 to 28. Players on cards like the GTX 1060 6GB or RX 580 8GB — which measured 66 FPS avg at 1440p high in Destiny 2 pre-patch — are now seeing dips into the low 50s in the Tower specifically.

The Three Settings That Matter

Destiny 2's graphics menu has 17 adjustable sliders, but only three of them account for the performance delta introduced in 9.7.0. Start here before touching anything else. **Environment Detail Distance** controls the LOD transition point Bungie extended in this patch. The default is now "High" (previously "Medium" in most configs). Dropping it back to Medium restores the old pop-in distance and frees 12–18 FPS on mid-range GPUs without affecting combat readability — you're not sniping environmental rocks. **Texture Quality** governs the mip-loading behavior that now pre-fetches higher-res armor normals. On 8GB cards, set this to "Medium" instead of "Highest." On 12GB+ cards, leave it at Highest — you have the headroom.

**Shadow Quality** is the third lever. Bungie's new cascade distribution means "Highest" now renders shadows for a larger screen-space area than before, even though the shadow map resolution itself didn't change. Medium shadow quality uses the old cascade split and recovers 8–14 FPS depending on scene density. The visual trade-off is minimal — you lose some definition on distant enemy shadows, but player silhouettes and nearby cover shadows (the ones that matter for PvP awareness) are identical between Medium and Highest. Players targeting 144+ FPS for Crucible should lock these three settings to Medium and treat everything else as optional tuning.

Secondary Settings for Marginal Gains

Once the big three are dialed in, five additional settings offer 2–6 FPS each if you need to squeeze closer to your monitor's refresh rate. **Ambient Occlusion** can drop from HDAO to SSAO — Destiny 2's HDAO implementation is screen-space anyway (not true geometric AO), so the quality delta is a slight reduction in shadow contact depth around armor crevices. SSAO is 4–5 FPS cheaper and visually identical in motion. **Depth of Field** (the menu calls it "DoF Intensity") adds a subtle blur to distant geometry when aiming down sights. Bungie re-tuned the blur radius in 9.7.0 to be slightly more aggressive, which costs an extra 3 FPS. Setting DoF to Low or Off recovers that cost with zero competitive downside — serious players disable DoF entirely to keep backgrounds sharp during sniper duels.

**Anti-Aliasing** is worth revisiting if you're chasing high refresh. SMAA and FXAA are both post-process (no meaningful performance difference), but Bungie's SMAA has an edge-detect bug in the new Tower that over-sharpens monument geometry and costs 2–3 FPS. FXAA is slightly softer but faster — or skip AA entirely if you're playing at 1440p or higher, where pixel density naturally reduces jaggies. **Motion Blur** remains pure preference, but 9.7.0 increased the per-object blur sample count from 8 to 12 for exotic armor glows, adding 2 FPS overhead. If you already run with motion blur off, you're unaffected; if you leave it on for aesthetic reasons, you're paying a small tax now.

**Foliage Detail Distance** is Destiny 2's sneakiest setting — it only affects grass and fern rendering in outdoor Pale Heart zones, but those zones are where the new story missions take place, and the default bumped up one tier in 9.7.0. Dropping it to Low costs nothing in Crucible or Strikes (which have minimal foliage) and saves 5–7 FPS in patrol zones. If you spend most of your time in PvP or endgame PvE, set Foliage to Low and forget it exists. The full Destiny 2 best settings guide breaks down every slider with side-by-side comparisons.

1. Launch Destiny 2 and open Settings → Video (not Graphics — that's the old pre-Lightfall menu, if it still appears).
2. Set Render Resolution to 100% (native) unless using DLSS/FSR, in which case enable your upscaler first, THEN adjust these sliders.
3. Environment Detail Distance: Medium. Texture Quality: Medium (≤8GB VRAM) or Highest (≥12GB). Shadow Quality: Medium.
4. Ambient Occlusion: SSAO. Depth of Field: Low or Off. Anti-Aliasing: FXAA or Off (if 1440p+).
5. Foliage Detail Distance: Low (unless you spend majority time in patrol zones and prefer the denser grass).
6. Motion Blur: Off (competitive standard) or leave at personal preference — it's 2 FPS either way now.
7. Apply settings and run a Crucible match or a Pale Heart patrol to confirm frame stability. Use the in-game FPS counter (Settings → Gameplay → Show FPS) or external overlay (MSI Afterburner, Steam) to track.

Hardware-Specific Baselines

Destiny 2 scales well across GPU tiers, but 9.7.0 tightened the performance bands. Cards that previously cruised at 1440p high now need setting adjustments to maintain smooth frame pacing. The GTX 1060 6GB, a legacy workhorse, measured 66 FPS avg at 1440p high pre-patch and now dips to 54 FPS with 9.7.0 defaults — applying the Medium Environment Detail + Medium Shadows combo brings it back to 62 FPS, close enough to the old baseline. The GTX 1070, which hit 82 FPS avg at 1440p high, drops to 68 FPS on new defaults but recovers to 79 FPS with the three-setting tweak. If you're targeting 1440p 144Hz, you need at least an RTX 4070 or RX 7800 XT with these optimized settings — older cards cap out in the 90–110 FPS range even with everything on Low.

For 1080p high-refresh players, the GTX 1070 Ti previously measured 103 FPS avg and now sits at 87 FPS with 9.7.0 defaults. The optimized config pushes it back to 98 FPS, just under the old number but smooth enough for 100Hz panels. RTX 3060 12GB and RX 6700 XT users should see 115–130 FPS at 1080p with the adjusted settings, assuming no CPU bottleneck (Destiny 2 loves fast single-thread performance — a Ryzen 7 9800X3D or Intel Core Ultra 9 285K will pull ahead of higher-core-count chips here). At 4K, even the RTX 5080 struggles to hold 120 FPS with 9.7.0's new rendering load unless you enable DLSS Performance mode, which upscales from ~1440p internal and looks acceptable on large displays.

CVars and Advanced Tweaks

Destiny 2 exposes a handful of console variables (CVars) through the `cvars.xml` file in the game's install directory, but Bungie actively discourages editing it — most variables are either ignored by the engine or cause crashes if set outside expected ranges. The two that *do* work and survive patches are `render_scale` (duplicates the in-game Render Resolution slider, so redundant) and `fov_offset` (adjusts field of view by ±5 degrees beyond the menu limit, useful for ultrawide users but not a performance lever). The widely-circulated "disable dynamic resolution" CVar (`dynamic_resolution 0`) was patched out in Lightfall and now does nothing.

For advanced users chasing every last frame, the only reliable path beyond in-game settings is GPU driver-level frame caps and low-latency modes. NVIDIA Reflex is built into Destiny 2's menu (Settings → Video → NVIDIA Reflex Low Latency) and should be set to Enabled or Enabled + Boost if you're on an RTX card — it shaves 8–15ms of input lag with no FPS cost. AMD users get a similar benefit from Radeon Anti-Lag 2, but it requires enabling in Adrenalin software (Gaming → Destiny 2 → Anti-Lag 2 toggle) — Bungie doesn't expose an in-game toggle for it. Intel Arc users have XeSS Frame Generation available in some Destiny 2 zones (Crucible, Strikes) as of driver 5848, but the current implementation causes occasional hitching when super abilities trigger, so PvP sweats should leave it off.

Windows-level tweaks (Game Mode, Hardware-Accelerated GPU Scheduling, registry edits) have minimal impact on Destiny 2 specifically — the game's engine is well-threaded and doesn't respond to the scheduler changes that help some Unreal Engine titles. The one exception: disabling Fullscreen Optimizations (right-click `destiny2.exe` → Properties → Compatibility → check "Disable fullscreen optimizations") can recover 2–4 FPS if you run true Fullscreen mode instead of Borderless, but you lose the ability to alt-tab smoothly. Most competitive players stick with Borderless for the flexibility. The Performance Pro tier includes a deep-layer config that handles GPU driver settings and Windows scheduler tweaks automatically, updated whenever Bungie or driver vendors change behavior.

Upscaling and Frame Generation Matrix

Destiny 2 supports all three major upscaling standards — DLSS (RTX GPUs), FSR (broad compatibility), and XeSS (Arc + some NVIDIA/AMD cards) — but the quality-to-performance ratio shifted in 9.7.0 because of the increased native rendering load. DLSS Quality mode used to be the sweet spot for 1440p players targeting 120 FPS, but the new geometry density pushes the upscaler into artifact territory (shimmering on shader glows, aliasing on distant enemy outlines). DLSS Balanced or Performance mode now produces a cleaner image because the lower internal resolution gives the algorithm more headroom to resolve detail without temporal instability.

FSR 3.1 (AMD's latest) handles Destiny 2's new shader normals better than FSR 2, especially on exotic armor with metallic finishes — set it to Balanced mode at 1440p (upscales from ~1100p internal) for the best balance of clarity and frame rate. Quality mode looks softer than native in 9.7.0, which is unusual for FSR but tracks with the increased geometric complexity. XeSS 2 on Intel Arc cards performs similarly to FSR 3.1 in Balanced mode, though it tends to over-sharpen bright particle effects (Stasis crystals, solar ignitions) and can look unnatural if you crank up in-game sharpness slider above 50%.

Frame generation is a separate consideration. DLSS 3 Frame Generation (RTX 40-series) works in Destiny 2 as of patch 8.2.0 and carries forward into 9.7.0 without issues — it effectively doubles frame rate but adds ~20ms of latency, so PvP players should disable it for Crucible and enable it only for PvE content where input lag matters less. DLSS 4 (RTX 50-series) uses multi-frame generation and can triple frame rate in Destiny 2's patrol zones, but Bungie hasn't optimized for it yet, so you'll see occasional frame-time spikes when loading new players into view. FSR 3.1 Frame Generation is available to all GPUs and works decently in Strikes/Gambit but causes visible ghosting when tracking fast-moving targets in PvP — avoid it for competitive modes.

Destiny 2's Monument of Triumph update brought meaningful visual upgrades, but the performance cost is real if you stick with default settings. The three-setting adjustment (Environment Detail, Texture Quality, Shadow Quality all to Medium) restores 90% of your pre-patch frame rate with almost no perceptible quality loss during actual gameplay — you're not staring at rocks, you're shooting enemies. Pair that with DLSS/FSR in Balanced mode if you need extra headroom, and you're back to smooth high-refresh gaming. If you want a zero-guesswork config, generate a free playbook for your exact GPU and let the optimizer handle the full matrix of settings, resolution, and upscaler combos. The engine will keep evolving, but the fundamentals stay consistent: free VRAM pressure, bias toward medium-tier settings for the expensive rendering passes, and use upscaling smartly when native res doesn't hit your target.

Frequently asked questions