The Ultimate PC Gaming Optimization Guide

Cyberpunk 2077: Path Tracing & DLSS 3.5 Optimization

1. Engine & Rendering Overview

Cyberpunk 2077 runs on REDengine 4, CD Projekt Red's proprietary engine that's been significantly overhauled since launch to support cutting-edge rendering features. The game's Path Tracing mode—introduced with the 2.0 update and ray reconstruction via DLSS 3.5—represents one of the most demanding real-time rendering workloads available in gaming today.

At its core, Path Tracing replaces virtually all traditional lighting systems (screen-space reflections, shadow maps, ambient occlusion) with a unified path-traced solution that simulates realistic light transport. This creates physically accurate global illumination, reflections, and shadows but comes at an immense performance cost, utilizing RT cores at near-maximum capacity.

The rendering pipeline is heavily GPU-bound in most scenarios, though crowded city districts with high NPC density can trigger CPU bottlenecks on systems with fewer than 8 performance cores. The game uses DX12 with aggressive async compute for RT workloads and benefits significantly from VRAM headroom—expect 10-12GB usage at 1440p Ultra with RT, scaling to 16GB+ at 4K.

2. System-Level Tweaks

Windows Optimization

• Hardware-Accelerated GPU Scheduling (HAGS): Enable this. Cyberpunk benefits from reduced CPU-to-GPU latency, netting 2-5% FPS gains and improving frame pacing in crowded areas.
• Power Plan: Use "Ultimate Performance" or "High Performance" mode. Cyberpunk's shader compilation and streaming systems benefit from sustained CPU boost clocks.
• Game Mode: Keep enabled. Windows will prioritize GPU resources for the game, reducing background interference.
• Page File: Ensure a system-managed page file exists on your fastest SSD. Cyberpunk's streaming system can lean on virtual memory during intensive sequences.

Driver Control Panel Settings (NVIDIA)

• Power Management: "Prefer Maximum Performance"
• Low Latency Mode: Set to "On" (not Ultra). Ultra can cause stutter with DLSS Frame Generation.
• Shader Cache: Enable and set to max size (10GB+). Cyberpunk benefits enormously from cached shaders.
• Resizable BAR: Critical. Enable in BIOS and verify in GPU-Z. Provides 5-10% performance uplift in RT scenarios.

AMD-Specific Settings

• Smart Access Memory: Must be enabled (AMD's version of Resizable BAR).
• Radeon Boost: Disable. Causes visual artifacts with FSR upscaling.
• Anti-Lag+: Enable only if not using Frame Generation. Can conflict with upscaling tech.

RAM & VRAM Considerations

Cyberpunk is surprisingly RAM-hungry. 32GB of system RAM is ideal, with dual-channel configuration mandatory for smooth frame times. The game actively uses 12-16GB during gameplay, leaving insufficient headroom on 16GB systems once Windows and background tasks are factored in.

For VRAM, the story is more nuanced:

• 1080p: 8GB adequate for RT Off/Medium; 10GB+ recommended for RT Ultra/Path Tracing with DLSS Quality.
• 1440p: 12GB minimum for comfortable headroom with Path Tracing; 16GB ideal.
• 4K: 16GB strongly recommended. Native 4K Path Tracing can spike above 20GB on cards that support it.

DLSS 3.5 & Ray Reconstruction

DLSS 3.5 introduces Ray Reconstruction, an AI-powered denoiser that replaces traditional hand-tuned denoisers for ray-traced effects. In Cyberpunk, this is transformative:

• Image Quality: Eliminates the "ghosting" and temporal artifacts present with DLSS 2.x when used with Path Tracing. Reflections in wet surfaces and glass become significantly cleaner.
• Performance Impact: Minimal. Ray Reconstruction adds <1% performance overhead while dramatically improving visual stability.
• Recommended Setting: Always enable when using Path Tracing. With standard RT, the benefits are less pronounced but still worthwhile.

DLSS Preset Selection:

Frame Generation Best Practices: DLSS 3 Frame Generation (FG) can dramatically boost perceived smoothness but requires a baseline of 50+ native fps to avoid input latency issues and artifacts. In Path Tracing mode with an RTX 4070, the optimal configuration is DLSS Quality + Frame Gen, delivering 80-100fps at 1440p—unplayable at 40-50fps native becomes silky smooth.

3. Optimal Graphics Settings Breakdown

Ray Tracing Configuration

Cyberpunk offers a spectrum of RT implementations, from selective RT effects to full Path Tracing. Here's the performance and visual breakdown:

Path Tracing Analysis: This mode is the visual showcase of the game. Night City's neon-lit streets become dramatically more immersive with physically accurate light bounce, reflections that capture the entire scene (not just what's on-screen), and shadows that respect real-world light behavior. However, it's a -65% to -75% performance hit compared to RT Off.

The decision matrix is simple:

• RTX 4090: Path Tracing at 1440p/4K with DLSS Quality + FG → 90-120fps. Go for it.
• RTX 4080 / 4070 Ti: Path Tracing at 1440p with DLSS Balanced + FG → 70-90fps. Viable.
• RTX 4070 / 4060 Ti: RT Ultra instead of Path Tracing. You'll get 85% of the visual impact with 40% better performance.
• RTX 3000 Series: RT Medium/High. Path Tracing requires DLSS 3 FG to be playable.

Core Graphics Settings

Texture Quality:

• Impact: Minimal FPS difference (2-3%) but significant VRAM usage.
• Low: 6GB VRAM | Medium: 8GB | High: 10GB | Ultra: 12GB+
• Recommendation: Match to your VRAM capacity. Ultra is worth it if you have headroom; the difference in wall textures, clothing, and signage detail is substantial.

Level of Detail (LOD):

• Impact: High → Medium = +8% FPS. Primarily CPU-bound setting.
• Visual Difference: Controls object pop-in distance and geometric complexity. Medium reduces distant detail but maintains good visual fidelity in the immediate vicinity.
• Recommendation: High for open-world exploration; Medium if CPU-limited or pushing for 120fps+.

Volumetric Fog/Cloud Quality:

• Impact: Ultra → High = +10-12% FPS in fog-heavy areas (industrial districts, badlands storms).
• Visual Difference: Ultra adds extra resolution to volumetric effects. The difference is subtle unless you're specifically looking for it.
• Recommendation: High. One of the best performance-for-visuals trades in the game.

Shadow Quality & Ray-Traced Shadows:

• Rasterized Shadows (RT Off mode): Ultra → High = +6-8% FPS. Slightly softer penumbras.
• RT Shadows: Built into RT modes; cannot be independently tuned. Path Tracing shadows are absolute perfection—physically accurate with proper contact hardening and soft shadows.
• Recommendation: High for rasterized; RT/Path Tracing when hardware allows.

Screen Space Reflections (SSR):

• Impact: Only relevant when RT Reflections are disabled. Ultra → High = +7-9% FPS.
• Visual Difference: SSR quality affects reflections on wet surfaces and glass. High is 85% of Ultra quality.
• Recommendation: Disable entirely if using RT Reflections; High if running RT Off.

Crowd Density:

• Impact: High → Medium = +10-15% FPS in dense city centers. CPU-bound.
• Visual Difference: Reduces NPC population. Night City feels noticeably less alive on Low.
• Recommendation: High for immersion; Medium if CPU-bottlenecked (Ryzen 5 5600, i5-12400 tier).

Motion Blur & Film Grain:

• Impact: ~2% FPS when disabled.
• Recommendation: Personal preference. Disable for competitive driving/combat; enable for cinematic experience.

4. Performance Tier Recommendations

Mid-Tier RTX 3060 12GB / RX 6700 XT @ 1080p

Upper-Mid RTX 4070 / RX 7800 XT @ 1440p

High-End RTX 4090 / RX 7900 XTX @ 4K

5. Advanced Tweaks & Config File Edits

Configuration File Location

%USERPROFILE%\Saved Games\CD Projekt Red\Cyberpunk 2077

User Settings Tweaks

Edit UserSettings.json for advanced options not exposed in-game:

Mods for Optimization

• Cyber Engine Tweaks: Unlocks hidden console commands and advanced memory management. Essential for power users.
• ArchiveXL: Improves asset streaming, reducing stutters in dense areas.
• Better RT Lighting: Adjusts PT lighting balance for more balanced indoor/outdoor exposure (visual preference mod).

NVIDIA Profile Inspector Settings

For those comfortable with advanced driver tweaks:

• Maximum Pre-Rendered Frames: Set to "1". Reduces input latency by 8-12ms.
• Triple Buffering: Disable when using VSync or GSync/FreeSync.
• Anisotropic Filtering: Force 16x if game setting is lower. Minimal performance cost (~1%).

6. Final Optimized Preset Summary

Balanced Preset (High Visuals + Solid Performance)

Path Tracing Showcase (Maximum Visuals)

Competitive Performance (120fps+ Target)

Alan Wake 2: Northlight Engine RT Overhead & FSR 3 Optimization

1. Engine & Rendering Overview

Alan Wake 2 is built on Remedy's Northlight Engine, a highly customized in-house engine that debuted with Quantum Break and has evolved into one of the most visually impressive proprietary engines in the industry. Northlight's rendering architecture is uniquely focused on cinematic presentation, with an emphasis on advanced lighting, volumetric effects, and photorealistic materials.

What makes Alan Wake 2 particularly demanding is its aggressive ray tracing implementation. Unlike some games where RT is supplementary, Northlight's RT pipeline handles reflections, global illumination, and shadows simultaneously—creating a cohesive, physically-based lighting model. However, this comes with substantial computational overhead that even high-end hardware struggles with natively.

The engine is predominantly GPU-bound, with RT operations consuming the majority of frame time. CPU usage is moderate—typically 30-50% across 8 cores—meaning even mid-tier CPUs (Ryzen 5 5600, i5-12400) aren't bottlenecks. The rendering uses DX12 exclusively, with no DX11 fallback, and relies heavily on mesh shaders for geometric detail in the environment.

FSR 3 vs DLSS Integration

Remedy shipped Alan Wake 2 with AMD FSR 3.0 as the primary upscaling solution, including FSR Frame Generation. While DLSS support was added post-launch, the engine is optimized around FSR, making it an interesting case study:

• FSR 3.0 Quality: Excellent upscaling quality at 1440p/4K, competitive with DLSS 2.x. At 1080p, slight softness visible.
• FSR Frame Generation: Works well but requires 60fps+ native to avoid artifacts. More prone to ghosting than DLSS 3 FG during rapid camera movement.
• DLSS 2.x: Slightly sharper image quality, especially in motion. Better temporal stability.
• DLSS 3 Frame Gen: Superior to FSR FG in artifact reduction, but only available on RTX 40-series.

2. System-Level Tweaks

Windows & Driver Optimization

• HAGS: Enable. Alan Wake 2 benefits from reduced command buffer latency, especially during intense combat sequences.
• Shader Cache: Max size (10GB). The game compiles many shaders during first-time area loads.
• Resizable BAR: Enable. Provides 6-8% performance uplift due to the engine's aggressive texture streaming.
• Virtual Memory: Critical. Ensure 32GB+ page file on NVMe SSD. The engine uses virtual memory during transitions between areas.

AMD-Specific Considerations

Since Alan Wake 2 was co-developed with AMD, Radeon GPUs receive specific optimizations:

• Smart Access Memory: Mandatory. 7-9% performance increase on RDNA 2/3 GPUs.
• Anti-Lag+: Can be used with FSR upscaling but disable if using Frame Generation (causes frame pacing issues).
• Radeon Super Resolution (RSR): Do not stack with FSR. Use FSR natively in-game.

VRAM & Streaming Buffer Management

Alan Wake 2's streaming system is both impressive and demanding:

• 1080p (High Settings): 8GB minimum; 10GB recommended for consistent frametimes.
• 1440p (High/Ultra): 12GB comfortable; can spike to 14GB in heavily forested areas (Cauldron Lake).
• 4K (Ultra): 16GB minimum. The game will exceed this on cards with 24GB if available.

CPU Thread Utilization

Northlight uses a well-threaded architecture:

• 6-core CPUs: Will see 70-90% utilization across all cores. Adequate but no headroom.
• 8-core CPUs: Sweet spot. 50-60% utilization provides smooth frame pacing.
• 12+ core CPUs: Minimal benefit beyond 8 performance cores. Northlight doesn't scale significantly past this point.

3. Optimal Graphics Settings Breakdown

Ray Tracing Configuration

Alan Wake 2's RT implementation is all-or-nothing. You can adjust quality, but disabling individual RT features isn't possible:

RT Recommendation by Hardware:

• RTX 3060 / RX 6700 XT: RT Off or Low only at 1080p with FSR Quality. The performance cost is too high for playable framerates otherwise.
• RTX 3070 Ti / RX 6800 XT: RT Low at 1440p with upscaling. Medium possible with FSR Balanced + FG.
• RTX 4070 / RX 7800 XT: RT Medium sweet spot at 1440p with FSR/DLSS Quality.
• RTX 4080+ / RX 7900 XTX: RT High at 1440p or RT Medium at 4K with upscaling.

Core Graphics Settings

Texture Quality:

• Impact: Minimal FPS (~2%) but massive VRAM difference.
• Low: 6GB | Medium: 8GB | High: 11GB | Ultra: 14GB+
• Visual: Ultra vs High is barely perceptible except on close-up surfaces (bark, rock faces, fabric).
• Recommendation: High for most users. Ultra only if 16GB+ VRAM and not concerned about VRAM headroom.

Mesh Quality:

• Impact: High → Medium = +8-10% FPS. GPU and VRAM bound.
• Visual: Controls geometric complexity of environments. Medium reduces polygon count on distant objects and foliage.
• Recommendation: High for open environments; Medium acceptable for performance-focused builds.

Volumetric Lighting:

• Impact: High → Medium = +12-15% FPS in fog-heavy areas (most of the game).
• Visual: Alan Wake 2's signature atmospheric fog is heavily dependent on this. Medium still looks good but loses some density.
• Recommendation: High if GPU allows. This setting defines the game's visual identity. Dropping to Medium is acceptable for <60fps scenarios.

Shadow Quality:

• Impact: Ultra → High = +6-7% FPS. RT enabled makes this less relevant.
• Visual: With RT On, shadow quality primarily affects shadow map resolution for non-RT shadows (rare). With RT Off, High vs Ultra difference is subtle.
• Recommendation: High is the sweet spot. Ultra marginal visual benefit.

Global Illumination Quality:

• Impact: Only applies when RT is enabled. High → Medium = +8-10% FPS.
• Visual: Controls RT GI sample count. Medium introduces slight graininess in indirect lighting; High is clean.
• Recommendation: Match to RT setting. If RT is Low, use Medium GI Quality. If RT is Medium/High, use High GI Quality.

Screen Space Reflections (RT Off Only):

• Impact: High → Medium = +5-6% FPS.
• Visual: Affects puddle reflections, wet surfaces. Medium has more visible cutoff artifacts at screen edges.
• Recommendation: High. The game is designed around reflections being high quality.

Post-Processing & Effects

Motion Blur:

• Impact: ~3% FPS when disabled.
• Recommendation: Artistic preference. Remedy uses excellent per-object motion blur that enhances cinematic feel. Leave on for immersion; disable for competitive clarity.

Depth of Field:

• Impact: Minimal (~1-2% FPS).
• Recommendation: Keep enabled. Used sparingly and enhances cinematic sequences.

Lens Distortion / Chromatic Aberration:

• Impact: 0% FPS.
• Recommendation: Disable if you find edge distortion distracting. Purely visual preference.

4. Upscaling & Frame Generation Deep Dive

FSR 3 Optimization

FSR 3.0 in Alan Wake 2 is AMD's showcase implementation. Here's what you need to know:

FSR Frame Generation:

• Minimum Native FPS: 50fps. Below this, motion artifacts become distracting.
• Latency Impact: Adds ~10-15ms of latency. Use Anti-Lag+ to partially compensate (AMD GPUs).
• Visual Artifacts: Ghosting on fast camera pans and transparent effects (fog). Less pronounced than FSR 2.x but still present.
• Recommendation: Use when native is 50-70fps to reach smooth 100-140fps. Don't rely on it to "save" <40fps scenarios.

DLSS vs FSR Quality Comparison

Having tested both extensively in Alan Wake 2:

• DLSS Quality: Sharper image in motion, especially on foliage and fine details (chain-link fences, text). Better temporal stability—less flickering on thin objects.
• FSR Quality: Very close to DLSS at 1440p/4K. At 1080p, more softness visible. Foliage can shimmer slightly during movement.
• DLSS Frame Gen vs FSR Frame Gen: DLSS 3 FG has fewer artifacts and better motion vector prediction. If you have an RTX 40-series card, prioritize DLSS 3 over FSR 3.

5. Performance Tier Recommendations

Mid-Tier RTX 3060 Ti / RX 6700 XT @ 1080p

Upper-Mid RTX 4070 / RX 7800 XT @ 1440p

High-End RTX 4080+ / RX 7900 XTX @ 4K

6. Advanced Tweaks & Known Issues

Config File Location

%LOCALAPPDATA%\Remedy\AlanWake2\renderer.ini

Shader Compilation Stutter Fix

Alan Wake 2 suffers from shader compilation stutter during first-time area loads. To minimize:

Frame Pacing Fixes

• Disable In-Game VSync: Use GSync/FreeSync or RTSS frame limiting instead. In-game VSync causes frame pacing issues with FSR Frame Gen.
• RTSS Frame Limit: Set to 3fps below your monitor's max refresh rate (e.g., 117fps for a 120Hz display). Eliminates judder.
• Windows Fullscreen Optimization: Disable in game .exe properties. Reduces input latency by 6-10ms.

Known Texture Streaming Bug

Some users experience blurry textures that don't resolve, even with high settings and sufficient VRAM. Workaround:

7. Final Optimized Presets

Balanced High-Quality (RT Medium, 1440p)

Maximum Visual Fidelity (4K RT High)

Performance-Focused (RT Off, 1080p/1440p)

Black Myth: Wukong: Unreal Engine 5 Nanite/Lumen Tuning

1. Engine & Rendering Overview

Black Myth: Wukong is one of the first AAA titles to fully leverage Unreal Engine 5's cutting-edge rendering features at scale. Built on UE 5.2, the game utilizes Nanite for virtualized geometry, Lumen for dynamic global illumination, and hardware ray tracing as an optional enhancement layer—making it a showcase for Epic's next-generation engine tech.

Nanite: Virtualized Geometry System

Nanite allows the game to render billions of polygons without traditional LOD (level of detail) management. In practice, this means:

• Environmental detail is extraordinarily dense—rock faces, foliage, and architecture display movie-quality geometric complexity.
• Performance doesn't scale linearly with polygon count; instead, screen pixel count matters more.
• At lower resolutions (1080p), Nanite's overhead is minimal. At 4K native, the cost increases substantially.

Lumen: Dynamic Global Illumination

Lumen provides real-time GI without baked lightmaps, allowing lighting to respond dynamically to time-of-day changes and destructible environments. Two modes exist:

• Software Lumen: Uses software ray tracing (screen-space + distance fields). Works on all GPUs but is performance-intensive.
• Hardware Lumen (RT): Leverages RT cores for higher quality reflections and more accurate light bounces. Significantly more demanding.

Performance Characteristics

Black Myth: Wukong is heavily GPU-bound, with frame times dominated by Lumen GI calculations and Nanite rasterization. CPU usage is moderate—typically 40-60% on 8-core CPUs—though certain boss arenas with complex particle effects can trigger brief CPU spikes.

The game uses DX12 exclusively with aggressive asynchronous compute for overlapping Lumen and shadow work. VRAM usage is high: expect 10-12GB at 1440p High, scaling to 16GB+ at 4K Ultra with all settings maxed.

2. System-Level Tweaks

Windows & Driver Configuration

• HAGS: Enable. UE5 benefits from reduced command buffer overhead, netting 3-6% FPS improvement.
• Shader Cache: Max size (10GB+). UE5 generates substantial PSO (Pipeline State Object) caches.
• Resizable BAR: Mandatory. Provides 8-12% uplift in Nanite-heavy scenes due to improved VRAM access patterns.
• Virtual Memory: 32GB+ page file recommended on NVMe SSD for Nanite's virtual texture streaming.

NVIDIA Control Panel Optimizations

• Power Management: "Prefer Maximum Performance"
• Low Latency Mode: "On" (not Ultra, which can cause frame pacing issues with DLSS)
• Texture Filtering - Quality: "High Performance" (minimal visual difference, 2-3% FPS gain)
• Threaded Optimization: On (helps with UE5's draw call overhead)

AMD-Specific Settings

• Smart Access Memory: Enable (6-9% performance increase)
• Radeon Anti-Lag: Can be used but disable if experiencing frame pacing issues
• Texture Filtering Quality: Performance mode for slight FPS gain

VRAM Management Critical

UE5's virtual texturing system is aggressive with VRAM allocation:

• 1080p: 8GB minimum; 10GB comfortable for High settings
• 1440p: 12GB minimum; 16GB recommended for Ultra with RT
• 4K: 16GB minimum; will use 20GB+ on 24GB cards

CPU Thread Optimization

UE5 is well-threaded but has specific characteristics:

• 6-core CPUs: Minimum viable. Expect 80-95% utilization and occasional frame drops during complex scenes.
• 8-core CPUs: Ideal sweet spot. 60-70% utilization with headroom for background tasks.
• 12+ core CPUs: Diminishing returns beyond 8P cores. UE5 scales to about 10 threads effectively; beyond that, limited benefit.

3. Optimal Graphics Settings Breakdown

Lumen Global Illumination Configuration

Lumen is the visual centerpiece and largest performance factor:

Lumen Recommendations by Hardware:

• GTX 1080 Ti / RX 5700 XT: Lumen Off or Low only. The performance cost is too severe without RT cores.
• RTX 3060 / RX 6700 XT: Lumen Medium at 1080p with FSR/DLSS Quality. Acceptable compromise.
• RTX 4070 / RX 7800 XT: Lumen High (Software) at 1440p with upscaling. Sweet spot for visuals-to-performance.
• RTX 4080+ / RX 7900 XTX: Hardware Lumen (RT) at 1440p/4K with DLSS/FSR Quality. Transformative visual upgrade.

Core Graphics Settings

Texture Quality:

• Impact: ~3% FPS difference but massive VRAM allocation.
• Low: 7GB | Medium: 9GB | High: 12GB | Epic: 16GB+
• Visual: Epic vs High is barely noticeable except in close-up examination of surfaces (stone carvings, cloth).
• Recommendation: Match to VRAM capacity. High is the sweet spot for most 12GB+ cards.

Effects Quality:

• Impact: Epic → High = +9-11% FPS. Affects particle density and quality.
• Visual: Controls spell effects, environmental particles (falling leaves, dust), and weather density. Epic adds extra layers of particles that are beautiful but taxing during combat.
• Recommendation: High. The visual difference is marginal during gameplay; Epic's extra particles only shine in photo mode.

Foliage Quality:

• Impact: Epic → High = +7-10% FPS in dense forest areas (70% of the game).
• Visual: Controls grass/vegetation density and LOD distance. Epic has incredibly dense undergrowth; High still looks lush.
• Recommendation: High. One of the best performance trades. Medium acceptable if severely GPU-limited.

Shadow Quality:

• Impact: Epic → High = +5-7% FPS.
• Visual: Epic increases shadow map resolution and extends draw distance. High shadows are already excellent; Epic is diminishing returns.
• Recommendation: High. Save the performance for Lumen instead.

Visual Effects (Cinematic Motion Blur, DOF):

• Impact: Combined ~4% FPS when all disabled.
• Recommendation: Personal preference. Motion blur is well-implemented and cinematic. DOF only active during cutscenes—leave on unless disliking the effect.

Nanite & Virtual Shadow Maps (VSM)

These UE5 features are not directly adjustable in the graphics menu but are tied to overall quality presets:

• Nanite: Always enabled. Cannot be disabled without config edits (not recommended—breaks rendering).
• Virtual Shadow Maps: Provides high-quality shadows with minimal overhead compared to traditional cascaded shadow maps. Enabled automatically at Medium settings and above.

4. Upscaling & Frame Generation

DLSS vs FSR vs XeSS Comparison

Black Myth: Wukong supports all three major upscaling technologies. Here's the quality hierarchy:

Upscaling Recommendations:

• NVIDIA RTX: Always use DLSS. It's the sharpest and most stable, especially on vegetation (critical in this game).
• AMD RDNA: FSR 3 is excellent. Quality mode is nearly indistinguishable from native at 1440p/4K.
• Intel Arc / Non-RT GPUs: XeSS works but is noticeably softer. Use only if FSR isn't available.

Frame Generation Implementation

DLSS 3 Frame Generation:

• Requirements: 45fps+ native for smooth experience. Below 40fps, artifacts become distracting during fast combat.
• Latency: Adds ~12ms. Use NVIDIA Reflex (built-in) to compensate—net latency is similar to native.
• Best Use Case: Achieving 100fps+ at 1440p/4K with Lumen High or RT enabled. Transforms playability.

FSR 3 Frame Generation:

• Requirements: 50fps+ native recommended. More prone to artifacts than DLSS 3 during rapid camera movement.
• Latency: ~15ms added. Use Anti-Lag+ if available (AMD GPUs).
• Visual Artifacts: Ghosting on spell effects and boss attacks. Less pronounced with higher base framerates.

5. Performance Tier Recommendations

Mid-Tier RTX 3060 Ti / RX 6700 XT @ 1080p

Upper-Mid RTX 4070 / RX 7800 XT @ 1440p

High-End RTX 4090 / RX 7900 XTX @ 4K

6. Advanced Tweaks & Stutter Mitigation

Config File Location

%LOCALAPPDATA%\b1\Saved\Config\Windows\Engine.ini

Shader Compilation Stutter Fix

UE5's PSO (Pipeline State Object) compilation causes traversal stutter. To minimize:

Frame Pacing Optimization

• Disable In-Game VSync: Use GSync/FreeSync or RTSS frame limiter instead.
• RTSS Frame Limit: Cap to 3fps below max refresh (e.g., 117fps for 120Hz). Eliminates frame time variance.
• Windows Fullscreen Optimization: Disable for the game executable (reduces latency by ~8ms).

VRAM Overhead Reduction

If you're close to VRAM limits, add to Engine.ini:

CPU Thread Priority (Advanced)

For systems with background tasks interfering:

7. Final Optimized Presets

Balanced High-Quality (Lumen High, 1440p)

Maximum Visual Fidelity (Hardware Lumen, 4K)

Performance-Focused (Lumen Off, 1080p/1440p)

Microsoft Flight Simulator: CPU-Limited Scenarios & DX12/DLSS Balancing

1. Engine & Rendering Overview

Microsoft Flight Simulator 2024 (and the 2020 edition) runs on Asobo Studio's proprietary engine, heavily customized for large-scale terrain streaming and photogrammetry rendering. Unlike typical games, MSFS is fundamentally a simulation platform, prioritizing accuracy and scale over traditional game optimization patterns.

Engine Architecture

The engine's unique characteristics:

• Terrain Streaming: Data is streamed from local cache, Azure cloud servers, or Bing Maps in real-time as you fly. This creates massive I/O overhead and dependency on internet bandwidth/latency.
• Photogrammetry & Satellite Imagery: Major cities use real-world 3D scans (photogrammetry) with gigabytes of texture data loaded on-demand.
• Weather Simulation: Real-time global weather data integration adds computational overhead for volumetric clouds and atmospheric effects.
• DX11 vs DX12: DX12 support was added post-launch and offers better multi-threading but requires specific optimizations. DX11 is more stable but CPU single-thread limited.

Performance Characteristics: The CPU Problem

Flight Simulator is notoriously CPU-bound, particularly in two scenarios:

• Low-altitude flying over dense cities (New York, London, Tokyo): Object culling, LOD management, and terrain streaming hammer 1-2 CPU cores.
• Complex aircraft (airliners with detailed system simulations): Flight model calculations, avionics simulation, and system logic run predominantly on single threads.

This means that even an RTX 4090 can be bottlenecked by CPU in typical gameplay, delivering 40-60fps regardless of GPU power. GPU usage often hovers at 60-80% while CPU cores show 1-2 threads at 100% utilization.

2. System-Level Tweaks

CPU Optimization Priority #1

Before touching graphics settings, optimize CPU:

• Ryzen 7000/9000 X3D CPUs: Best-in-class for MSFS due to 3D V-Cache. The extra cache drastically reduces terrain streaming latency.
• Intel 13th/14th Gen: Competitive, but ensure P-cores are prioritized. Disable E-cores in BIOS for MSFS if using 13600K or higher—E-cores add latency without benefit.
• Memory Speed Critical: 32GB DDR5-6000+ (AMD) or DDR5-6400+ (Intel) provides measurable FPS gains. MSFS benefits from memory bandwidth more than most games.
• Windows Power Plan: Ultimate Performance mode mandatory. Prevents CPU from downclocking during "light" loads (which MSFS incorrectly appears as).

Storage & Streaming Optimization

• Installation Location: NVMe Gen 4 SSD minimum. Gen 3 SSDs will bottleneck terrain streaming, causing stutter.
• Rolling Cache: Enable in-sim and set to 32GB+ on your fastest SSD. This caches previously visited areas, reducing re-downloads.
• Manual Cache (Optional): Pre-download regional data for areas you fly frequently. Eliminates streaming overhead entirely for those areas.
• Internet Connection: 50Mbps+ recommended. Lower bandwidth increases terrain loading latency, causing pop-in and stutter.

DX12 vs DX11 Decision

This is nuanced:

DX12 Requirements:

• Latest GPU drivers (critical—DX12 path is actively being optimized)
• HAGS enabled in Windows
• Resizable BAR enabled in BIOS (8-12% FPS improvement in DX12)

NVIDIA/AMD Control Panel Settings

• Low Latency Mode: "Ultra" for DX11; "On" for DX12 (Ultra causes issues in DX12)
• Shader Cache: Max size. MSFS generates extensive shader permutations.
• Threaded Optimization: On (helps in DX12)
• Texture Filtering: Quality mode. MSFS benefits from high-quality filtering due to terrain LOD transitions.

3. Optimal Graphics Settings Breakdown

Render Scaling & DLSS/FSR

MSFS's Render Scaling works differently than most games:

• 100% Render Scale: Native resolution. Only achievable on flagship GPUs.
• 80-90% TAA: Standard anti-aliasing. Acceptable quality loss, +20-30% FPS.
• DLSS Quality (67%): +40-50% FPS. Image quality superior to TAA 80%. Strongly recommended.
• DLSS Balanced (58%): +60-70% FPS. Slight softness on distant terrain but usable.
• FSR 2.2 Quality: Comparable to DLSS Balanced. Use on AMD GPUs.

Critical Recommendation: Always use DLSS/FSR in MSFS. The performance gain is massive, and the image quality trade-off is minimal due to the game's heavy reliance on distant terrain rendering (where upscaling excels).

Core Graphics Settings Analysis

Terrain Level of Detail (LOD):

• Impact: 200 → 100 = +25-30% FPS. Heavily CPU-bound.
• Visual: Controls terrain mesh detail distance. 200 = maximum detail out to horizon. 100 = noticeable LOD pop-in beyond 5-10km.
• Recommendation: 150 is the sweet spot. 200 is overkill unless cruising at FL400 (40,000ft).
• CPU Impact: This is the #1 CPU killer. Lower this first if CPU-bottlenecked.

Objects Level of Detail:

• Impact: 200 → 100 = +20-25% FPS. CPU-bound.
• Visual: Controls building, tree, and object draw distance. Ultra High (200) shows incredible detail but tanks FPS in cities.
• Recommendation: 100-150 for dense city flying; 200 for rural/cruising flight.

Buildings (Photogrammetry):

• Impact: High → Medium = +15% FPS over major cities. Minimal impact over rural areas.
• Visual: High uses full photogrammetry data. Medium uses simplified versions. Low disables photogrammetry entirely.
• Recommendation: Medium unless specifically showcasing city scenery. Low for VR.

Trees (Vegetation):

• Impact: High → Medium = +8-10% FPS. GPU-bound.
• Visual: High = dense forests. Medium = noticeably sparser but acceptable.
• Recommendation: Medium. The FPS cost of High isn't worth it for most flying.

Grass and Bushes:

• Impact: Ultra → High = +5-7% FPS at low altitude.
• Visual: Only visible below 1000ft AGL. Ultra is extremely dense.
• Recommendation: High. You're rarely low enough for Ultra to matter.

Clouds (Volumetric):

• Impact: Ultra → High = +10-12% FPS when flying through weather.
• Visual: MSFS's volumetric clouds are stunning. Ultra adds extra density layers. High still looks excellent.
• Recommendation: High. One of the signature visuals—worth keeping elevated.

Texture Resolution & Anisotropic Filtering:

• Impact: Ultra → High = +3-5% FPS. VRAM-bound.
• Visual: Minimal difference in flight. Noticeable only in cockpit closeups.
• Recommendation: High unless 16GB+ VRAM and GPU headroom. Ultra for screenshots.
• Anisotropic Filtering: 16x always. Minimal cost, huge visual benefit for runway/terrain textures.

Reflections:

• Impact: Ultra → High = +4-6% FPS.
• Visual: Affects cockpit glass reflections and water surfaces. Ultra adds minimal visual benefit.
• Recommendation: High. Save performance for more impactful settings.

Shadows:

• Impact: Ultra → High = +8-10% FPS.
• Visual: Shadow resolution and draw distance. High is already excellent; Ultra is diminishing returns.
• Recommendation: High. Medium acceptable for VR or performance-focused builds.

VR-Specific Optimization

MSFS in VR is exponentially more demanding:

• OpenXR Toolkit: Mandatory. Enables FSR upscaling in VR, providing 40-60% FPS boost.
• Render Scaling: 70-80% in-sim, then OpenXR FSR on top. Double upscaling is necessary.
• LOD Settings: Terrain LOD 100-120; Objects LOD 80-100. VR requires aggressive compromises.
• Target Framerate: 45fps native with motion reprojection to 90fps. Don't target 90fps native—impossible on current hardware.

4. Performance Tier Recommendations

Mid-Tier RTX 3060 Ti / RX 6700 XT @ 1080p

Upper-Mid RTX 4070 / RX 7800 XT @ 1440p

High-End RTX 4090 / RX 7900 XTX @ 4K

5. Advanced Tweaks & Config Edits

Config File Location

%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_[alphanumeric]\LocalCache\UserCfg.opt

Hidden Performance Settings

Edit UserCfg.opt with game closed:

Rolling Cache Optimization

In-sim settings:

• Rolling Cache Size: 32-64GB on your fastest SSD (separate from game install if possible).
• Manual Cache: Download your home region and frequent destinations. Saves 40-60% bandwidth during flight.

NVIDIA Profile Inspector (Advanced)

For experienced users:

• Frame Rate Limiter Mode: "Disabled" (use in-sim limiter or RTSS instead)
• Maximum Pre-Rendered Frames: "1" (reduces latency)
• Texture Filtering - Negative LOD Bias: "Clamp" (prevents shimmering on distant terrain)

6. Final Optimized Presets

Balanced High-Quality (1440p DX12)

Maximum Visual Showcase (4K)

VR Optimized (Quest 3 / Reverb G2)

Assassin's Creed Shadows: Anvil Engine Crowd Density & Shadow Caching

1. Engine & Rendering Overview

Assassin's Creed Shadows runs on the latest iteration of Ubisoft's Anvil Engine (formerly AnvilNext), significantly overhauled for this generation with improved lighting, vegetation systems, and—critically—massive crowd rendering capabilities. Set in feudal Japan, the game pushes NPC density to new extremes, particularly in bustling city districts.

Anvil Engine Characteristics

The engine's defining traits:

• Crowd Simulation: Hundreds of NPCs on-screen simultaneously, each with individual AI routines. This is heavily CPU-bound, particularly on the main thread.
• Volumetric Fog System: Dense atmospheric fog is a signature visual element, especially in temple districts and forests. GPU-intensive but beautifully implemented.
• Shadow Map Caching: Anvil uses aggressive shadow caching to reduce per-frame rendering cost. When working well, performance is excellent; when cache invalidation triggers excessively, frame times spike.
• Vegetation System: Grass, bamboo forests, and foliage use a custom rendering pipeline separate from standard geometry. Scales well with GPU power but has CPU overhead for wind simulation.

Performance Bottlenecks

AC Shadows exhibits distinct bottleneck patterns:

• Dense Cities (Kyoto Markets, Castle Towns): CPU-limited. Crowd simulation, AI pathfinding, and LOD management overwhelm 1-2 CPU cores, with GPU usage dropping to 60-70%.
• Open World Traversal: GPU-balanced. Vegetation, shadows, and volumetric effects utilize GPU efficiently while CPU load is moderate.
• Interiors (Temples, Mansions): GPU-bound. Ray-traced indirect lighting (if enabled) and high-resolution textures dominate frame time.

2. System-Level Tweaks

CPU Optimization for Crowd Density

Crowd simulation dominates CPU usage:

• 6-Core CPUs: Minimum viable. Will bottleneck severely in cities, seeing 100% usage on 2-3 cores.
• 8-Core CPUs: Recommended. Maintains 60-75% utilization with headroom for background tasks.
• 12+ Core CPUs: Diminishing returns. Anvil doesn't scale well beyond 8 threads for game logic.
• Cache Matters: CPUs with large L3 cache (Ryzen 7800X3D, i7-13700K) perform 10-15% better in crowd-heavy scenarios due to improved AI/physics data access.

Windows Configuration

• HAGS: Enable. Provides 3-5% uplift in GPU-bound scenarios.
• Power Plan: High Performance minimum; Ultimate Performance if available.
• Game Bar: Disable. Anvil engine can conflict with Game Bar overlays, causing frame pacing issues.
• Memory: 16GB minimum; 32GB strongly recommended. Anvil is memory-hungry, using 12-16GB during gameplay plus Windows overhead.

Driver Settings (NVIDIA)

• Shader Cache: Max size (10GB). Anvil generates extensive shader variations.
• Low Latency Mode: "On" (not Ultra—causes microstutter with Anvil's frame pacing)
• Threaded Optimization: On (helps with draw call overhead)
• Texture Filtering: Quality mode (Anvil's LOD transitions benefit from high-quality filtering)
• Resizable BAR: Enable. 5-8% performance improvement, especially in open-world streaming scenarios.

AMD-Specific Optimizations

• Smart Access Memory: Mandatory. Significant uplift in texture streaming scenarios.
• Anti-Lag+: Enable if not using FSR Frame Generation (conflicts otherwise).
• Radeon Boost: Disable—causes visual artifacts during camera movement.

VRAM Requirements

Texture streaming is aggressive:

• 1080p (High): 8GB minimum; 10GB comfortable.
• 1440p (High/Ultra): 12GB minimum; 16GB recommended for Ultra Textures.
• 4K (Ultra): 16GB minimum; will utilize 20GB+ on 24GB cards.

3. Optimal Graphics Settings Breakdown

Crowd Density Configuration (Critical Setting)

This is the single most impactful setting:

Recommendations by CPU:

• 6-core CPUs (Ryzen 5 5600, i5-12400): Medium maximum. High causes severe stuttering in cities.
• 8-core CPUs (Ryzen 7 5800X, i7-12700): High for immersion; Medium for performance-focused 90fps+ targets.
• High-end CPUs (Ryzen 7800X3D, i9-13900K): Very High viable at 1440p. Expect 50-60fps in densest areas regardless of GPU.

Core Graphics Settings

Shadow Quality & Shadow Caching:

• Impact: Ultra → High = +8-10% FPS. Affects shadow map resolution and caching aggressiveness.
• Visual: Ultra produces razor-sharp shadows with proper contact hardening. High is 90% as good; Medium introduces noticeable softness.
• Caching Behavior: Ultra caches fewer shadow maps per frame (higher resolution each), causing occasional 1-frame hitches when cache invalidates. High caches more efficiently.
• Recommendation: High. Best balance of quality and cache efficiency. Ultra for screenshots only.

Environment Quality (Foliage, Grass, Vegetation):

• Impact: Very High → High = +12-15% FPS in forests/bamboo groves. Minimal in cities.
• Visual: Very High adds extremely dense undergrowth and individual blade rendering. High still looks lush.
• CPU Cost: Moderate CPU overhead for wind simulation on Very High (4-6% CPU usage).
• Recommendation: High. Very High is overkill unless specifically showcasing environmental detail.

Volumetric Quality (Fog, Mist, God Rays):

• Impact: Very High → High = +10-12% FPS. Heavily GPU-bound.
• Visual: Very High adds extra sampling steps to volumetric effects. High maintains atmospheric quality with less overhead.
• Recommendation: High. This is a signature visual for the setting—worth maintaining elevated. Medium acceptable on mid-tier GPUs.

Texture Quality:

• Impact: Minimal FPS (<3%) but massive VRAM difference.
• Low: 6GB | Medium: 8GB | High: 12GB | Very High: 16GB | Ultra: 20GB+
• Visual: High vs Very High/Ultra is barely noticeable in gameplay. Close-up material detail differs in photo mode.
• Recommendation: Match VRAM capacity. High for 12GB cards; Very High only if 16GB+ with headroom.

Clutter Density (Props, Objects):

• Impact: Very High → High = +7-9% FPS. CPU-bound in cities.
• Visual: Controls density of environmental props (crates, barrels, lanterns, debris). Very High adds clutter that's rarely noticed.
• Recommendation: High. Performance gain is worthwhile; visual loss is negligible.

Anti-Aliasing:

• TAA (Native): Baseline quality, can be somewhat soft.
• DLAA (NVIDIA): Better image quality than native TAA, minimal performance cost (~3%). Requires RTX GPU.
• Recommendation: Use DLAA if GPU has headroom at target resolution. Otherwise, TAA is adequate.

Ray Tracing Implementation

AC Shadows supports selective RT features:

Recommended RT Configurations:

• RTX 3060 Ti / RX 6700 XT: RT Off. Performance cost too severe.
• RTX 4070 / RX 7800 XT: RT Shadows only. Good quality-to-performance ratio.
• RTX 4080 / RX 7900 XTX: RT Shadows + Reflections at 1440p with DLSS Quality.
• RTX 4090: Full RT (Shadows + Reflections + GI) at 4K with DLSS Balanced.

4. Upscaling & Frame Generation

DLSS vs FSR 3 in Anvil Engine

Both upscalers are well-implemented:

Frame Generation Considerations:

• DLSS 3 FG: Requires 50fps+ native. Works well in open-world; can cause artifacts during fast grappling hook movement.
• FSR 3 FG: Similar requirements. Slightly more ghosting during rapid camera pans in crowded areas.
• Latency: DLSS 3 + Reflex maintains sub-35ms latency even with FG. FSR 3 + Anti-Lag+ is 5-8ms higher.

5. Performance Tier Recommendations

Mid-Tier RTX 3060 Ti / RX 6700 XT @ 1080p

Upper-Mid RTX 4070 / RX 7800 XT @ 1440p

High-End RTX 4090 / RX 7900 XTX @ 4K

6. Advanced Tweaks & Known Issues

Shadow Caching Optimization

Anvil's shadow cache can sometimes invalidate too aggressively, causing frame time spikes:

Crowd Simulation LOD Adjustment

Force more aggressive NPC LOD to improve CPU performance:

Frame Pacing Fixes

• Disable In-Game VSync: Use GSync/FreeSync or RTSS frame limiter (set to -3fps below max refresh).
• Fullscreen Optimization: Right-click game .exe → Properties → Compatibility → Disable fullscreen optimizations. Reduces input latency by ~6ms.
• Process Priority: Set game process to "High" priority in Task Manager during play. Can reduce background interference.

Texture Streaming Stutter Mitigation

If experiencing brief freezes during traversal:

7. Final Optimized Presets

Balanced High-Quality (1440p)

Maximum Visual Showcase (4K RT)

Performance-Focused (High FPS, 1080p/1440p)