Best Ashes of Creation Settings for Performance

Muhib Nadeem / December 24, 2025 / 12 min read
Note: This article reflects technical best practices from the writer’s perspective and does not necessarily reflect the views of Hone.

You load into Verra at 90 FPS. A Harbinger event spawns. Your framerate crashes to 25 and the screen stutters. Combat becomes a slideshow while others fight smoothly around you.

This guide shows the best Ashes of Creation settings for performance on PC. You will learn how Unreal Engine 5.6 works, which settings destroy FPS, hardware-specific optimizations, and advanced tweaks that stabilize frame rates during sieges and open world events.

Understanding Unreal Engine 5.6 Performance in Verra

Ashes of Creation runs on cutting-edge technology that looks incredible but demands proper configuration. The good news: most performance issues have straightforward fixes once you understand what causes them.

What Makes Ashes of Creation Performance Demanding

Ashes of Creation

The game uses Unreal Engine 5.6 with two main technologies that define its visual quality and performance cost. Nanite handles geometry by streaming high detail 3D models dynamically instead of using traditional level of detail systems. Lumen provides real time global illumination, meaning light bounces realistically off surfaces and changes throughout the day night cycle. Both systems look stunning but stress your hardware in specific ways.

⚙️
Nanite Virtualized Geometry
Streams billions of polygons dynamically. Creates stutter on slow storage drives and increases CPU load during heavy object culling in player hubs.
CPU Impact
💡
Lumen Global Illumination
Real time lighting and reflections. Single biggest GPU performance factor, accounting for 30 to 40 percent of frame time at high settings.
GPU Impact
🌥️
Volumetric Clouds & Fog
Ray marched atmospheric effects. Extremely expensive and can be completely disabled via console commands for 10 to 20 percent FPS gains.
GPU Impact
🎭
Virtual Shadow Maps
Ultra sharp shadows at extreme distances. Consumes massive VRAM. Cards with 8GB or less need Medium or Low shadow quality to prevent stuttering.
VRAM Impact
📊 Alpha Performance Expectations
Ashes of Creation is still in Alpha Two. The client prioritizes feature implementation over code optimization. Memory leaks, shader compilation stutters, and unoptimized asset streaming are normal. Full optimization happens later in development, so current settings work around these issues rather than eliminate them.

Best Graphics Settings for Different Goals

Scenario Based Settings Profiles

Choose your priority to see recommended settings for that playstyle

⚔️
Competitive PvP
Max FPS / Low Latency
🌄
Immersive PvE
Visual Quality / 60 FPS
🏰
Mass Sieges
Stability / No Crashes
💻
Low End Hardware
Playable 30 FPS
Setting Name
Competitive
Immersive
Performance Impact
Global Illumination (Lumen)
Low/Medium
High
Critical
Reflections
Low
Medium
High
Shadows
Low
High
High
View Distance
Medium
High
High (CPU)
Foliage Quality
Low
High
Medium
Effects Quality
Low
Medium
Medium
Post Processing
Low
Medium
Low
Texture Quality
High
Epic
Low (VRAM Only)
Why Lumen Settings Matter Most
Global Illumination at Epic uses high precision software ray tracing over long distances. High maintains precision but reduces range. Medium simplifies the calculations significantly while keeping lighting dynamic. The difference between Epic and Medium can be 40 to 60 FPS in demanding areas like Harbinger events. Low disables Lumen entirely for massive gains but makes the world look flat and lifeless.

Advanced Console Commands for Extra Performance

Press the Tilde key (~ or backtick) to open the developer console. These commands provide performance gains beyond what the graphics menu allows. They reset after each login unless you add them to configuration files.

Performance Console Commands
~ r.VolumetricCloud 0
Disables volumetric cloud rendering completely. Clouds become a simple 2D skybox. This is the single most effective command for GPU bound systems.
+10 to 20% FPS
~ r.VolumetricFog 0
Removes atmospheric fog and haze effects. Improves visibility in swamps and forests while reducing GPU load. Makes distant areas clearer.
+5 to 10% FPS
~ r.Lumen.Reflections.Allow 0
Forces Lumen reflections off completely. Overrides in game menu settings. Critical for performance near water in the Sport Fishing update areas.
+8 to 15% FPS
~ r.Shadow.Virtual.Enable 0
Disables Virtual Shadow Maps entirely. Reverts to standard shadow maps with lower quality but much better performance on VRAM limited cards.
Stability on 8GB VRAM
~ stat fps
Displays real time FPS counter and frame time graphs. Use this to test which settings actually improve your performance.
💾 Making Console Commands Permanent
To avoid retyping commands every session, edit GameUserSettings.ini located at %localappdata%\AOC\Saved\Config\WindowsClient\. Add your preferred commands under the [SystemSettings] section. Always backup the file before editing. Example: sg.GlobalIlluminationQuality=0 forces Lumen completely off if even Low setting is too heavy.

Upscaling Technologies: DLSS vs FSR

Native resolution rendering is inefficient for Unreal Engine 5 games. Upscaling technologies render the game at a lower internal resolution and use AI to reconstruct a sharper image. This dramatically reduces GPU load while maintaining visual quality.

Nvidia DLSS 4

Hardware Required RTX 20/30/40/50
Best Mode Quality
Frame Generation RTX 40/50 Only
Input Latency Use Reflex On + Boost
PvP Recommendation DLSS On / Frame Gen Off

AMD FSR 4

Hardware Required Any GPU (Best RX 9000)
Best Mode Quality
Frame Generation Available
Image Quality Slight Shimmer on Grass
Universal Support Works on Nvidia/Intel

TSR (Fallback)

Hardware Required Any GPU
Quality Softer than DLSS/FSR
Performance Heavier than DLSS/FSR
Use Case DLSS/FSR Glitches
Recommendation Last Resort Only
🎮 Frame Generation Trade Off
Frame Generation doubles displayed FPS by inserting AI generated frames between real frames. This looks smoother but adds input latency because the system must wait to generate the interpolated frame. For competitive PvP, turn Frame Gen off and use Nvidia Reflex or AMD Anti Lag to reduce latency instead. For PvE exploration, Frame Gen makes 40 FPS feel like 80 FPS.

Hardware Specific Optimization Tips

GPU and CPU Specific Tweaks

Different hardware benefits from different optimizations

🟢
Nvidia RTX GPUs
  • 1
    Update to driver 591.59 WHQL for DLSS 4 support and Ashes of Creation game profile
  • 2
    Nvidia Control Panel: Set Shader Cache Size to Unlimited. Default cache fills up causing repeat shader compilation stutters
  • 3
    Power Management: Prefer Maximum Performance prevents GPU downclocking during CPU bound moments in cities
  • 4
    Cards with 8GB VRAM (RTX 3070, 4060 Ti): Lower Texture Quality to High and Shadows to Medium to prevent VRAM thrashing
🔴
AMD Radeon GPUs
  • 1
    Update to Adrenalin 25.12.1 WHQL for FSR 4 Redstone support on RX 9000 series
  • 2
    Enable Smart Access Memory (Resizable BAR) in BIOS. UE5 streams massive data, full VRAM access reduces stuttering
  • 3
    Radeon Anti Lag: Turn On to reduce input latency, especially if not using FSR Frame Generation
  • 4
    RX 5000/6000 series: Lumen ray tracing hits harder than Nvidia. Use Medium Global Illumination instead of High
🔵
AMD Ryzen CPUs
  • 1
    X3D chips (5800X3D, 7800X3D, 9800X3D): Massive advantage in MMO scenarios. Large L3 cache stores player data reducing RAM latency
  • 2
    Enable PBO (Precision Boost Overdrive) and EXPO/DOCP for RAM to maximize single thread performance
  • 3
    32GB RAM is the real requirement despite 16GB being listed. Client has memory leak issues consuming 20 plus GB over time
🔷
Intel CPUs
  • ⚠️
    13th/14th Gen K-series (13900K, 14900K): Update BIOS to latest microcode. Known voltage instability causes UE5 crashes
  • 2
    Enable XMP/EXPO for RAM in BIOS. Faster memory speeds help compensate for smaller CPU cache vs AMD X3D
  • 3
    Disable E-cores in BIOS if experiencing stuttering. UE5 main thread can get scheduled on efficiency cores causing hitches
🚨 VRAM Thrashing Warning
At 1440p High settings, the game uses 10 to 12GB of VRAM. Graphics cards with 8GB (RTX 3070, 4060 Ti, RX 6700 XT) will experience severe micro stuttering as the GPU constantly swaps texture data between VRAM and slower system RAM. This manifests as hitching during camera rotation. Solution: Lower Texture Quality to High or Medium and reduce Shadow Quality to Medium. This is non negotiable for 8GB cards regardless of GPU core power.

DirectX 12 vs DirectX 11 Performance

DirectX 12 is the default API and required for Nanite, Lumen, and Frame Generation. However, it suffers from shader compilation stuttering where the game freezes momentarily when loading new visual effects for the first time. DirectX 11 is the stability fallback that disables modern rendering features but eliminates most stuttering.

Use DirectX 12 for modern hardware (RTX 30 series and newer, RX 6000 series and newer). The first few hours will have compilation stutters, but these smooth out as shaders cache. If the game crashes constantly or stutters unplayably, force DirectX 11 via Steam launch options by adding -dx11 to the launch arguments. Visual quality degrades significantly but frame pacing stabilizes immediately.

Critical System and Driver Settings

Windows settings and driver configurations outside the game matter just as much as in game settings. The Alpha Two client has a known memory leak where the process consumes 20 to 30GB of RAM over extended sessions. With only 16GB total, the system will page to your SSD causing massive stuttering and eventual crashes.

Install 32GB of RAM if possible. If stuck with 16GB, use Process Lasso to automatically trim the working set when AOC.exe exceeds 80 percent of system memory. Set the game process to High CPU priority and High I/O priority to prevent Windows Update or background tasks from causing streaming stutters. Ensure your storage drive is an NVMe SSD for Nanite asset streaming. SATA SSDs work but introduce traversal hitching. HDDs are unplayable.

Steam Launch Options for Extra Control

Right click Ashes of Creation in Steam, select Properties, and add these to Launch Options under the General tab:

  • -dx12 Forces DirectX 12 explicitly (default but ensures it even if settings corrupt)
  • -dx11 Forces DirectX 11 legacy mode for stability on crashing systems
  • -USEALLAVAILABLECORES Better core distribution on high core count CPUs like Ryzen 9 5950X and 7950X
  • -NOTEXTURESTREAMING Only for 24GB plus VRAM (RTX 3090/4090). Eliminates pop in but crashes instantly if VRAM fills

Siege and Mass Combat Specific Settings

Node wars and siege events with hundreds of players create the worst case performance scenario. The CPU bottlenecks from processing player positions and animations. The GPU struggles with overlapping particle effects from dozens of abilities firing simultaneously.

For these situations, turn Character Nameplates to Minimal or Off. This significantly reduces UI thread load on the CPU. Lower Effects Quality to Low to reduce particle overdraw. Set Shadows to Low because spell effects cast dynamic shadows that multiply the rendering cost. If DirectX 12 crashes during sieges, switch to DirectX 11 via launch options. Visual quality drops but stability improves dramatically. The goal shifts from pretty screenshots to maintaining playable frame rates above 30 FPS.

Conclusion

Ashes of Creation performance optimization requires understanding what Unreal Engine 5.6 demands from your hardware. Lumen global illumination is the primary GPU cost. Lowering it from Epic to Medium can double your frame rate. Volumetric clouds disabled via console commands provide another 10 to 20 percent FPS for free. View Distance controls CPU load in player hubs. VRAM management prevents stuttering on 8GB cards by keeping Textures and Shadows at Medium. Use DLSS or FSR Quality mode for upscaling but disable Frame Generation in PvP to avoid input lag. Update to the latest GPU drivers and ensure 32GB of RAM to handle the memory leak. With these targeted changes, most systems achieve stable 60 FPS in exploration and playable 30 plus FPS during mass combat events.

FAQ

What are the best Ashes of Creation settings for performance

Set Global Illumination to Medium, Reflections to Low, Shadows to Medium, and View Distance to Medium. Use DLSS or FSR Quality mode for upscaling. Disable volumetric clouds via console command r.VolumetricCloud 0 for an immediate 10 to 20 percent FPS boost. These settings balance visual quality with stable frame rates.

Why is my FPS so low in Ashes of Creation

Lumen global illumination at High or Epic settings consumes 30 to 40 percent of GPU frame time. Volumetric clouds add another 10 to 20 percent. High View Distance overloads the CPU in player hubs. Cards with 8GB VRAM experience stuttering from texture streaming. Lower these specific settings for major FPS gains.

Should I use DLSS or FSR in Ashes of Creation

Yes, upscaling is essential for Unreal Engine 5 performance. Nvidia RTX users should enable DLSS Quality mode. AMD users should enable FSR Quality mode. Both provide significant FPS gains while maintaining visual clarity. Use DLSS on RTX cards for slightly better image quality. FSR works on any GPU including Nvidia.

Should I enable Frame Generation in Ashes of Creation

For PvP and competitive content, turn Frame Generation off. It adds input latency that makes combat feel floaty. For PvE exploration and questing, turn it on to smooth out frame rates. Always enable Nvidia Reflex On plus Boost or AMD Anti Lag when using Frame Gen to minimize added latency.

What console commands improve Ashes of Creation performance

Press Tilde to open console. Type r.VolumetricCloud 0 to disable clouds for 10 to 20 percent FPS gain. Type r.VolumetricFog 0 to remove atmospheric haze. Type r.Lumen.Reflections.Allow 0 to force reflections off. Type stat fps to display frame rate and frame time for testing settings changes.

How much VRAM does Ashes of Creation need

At 1440p High settings, the game uses 10 to 12GB of VRAM. Cards with 8GB like RTX 3070 and 4060 Ti will experience micro stuttering during camera rotation as the GPU swaps textures. Lower Texture Quality to High and Shadow Quality to Medium on 8GB cards to prevent VRAM thrashing.

Should I use DirectX 11 or DirectX 12 for Ashes of Creation

Use DirectX 12 for modern hardware. It enables Nanite, Lumen, and Frame Generation. Expect shader compilation stutters during the first few hours that smooth out as shaders cache. If the game crashes constantly or stutters unplayably, force DirectX 11 via Steam launch options with -dx11 for stability at the cost of visual quality.

Why does Ashes of Creation stutter so much

Alpha Two has shader compilation stutter in DirectX 12 when loading new visual effects. VRAM thrashing on 8GB cards causes micro stutters. Memory leak issues with 16GB RAM force paging to SSD. Slow storage drives cannot stream Nanite assets fast enough. Solutions: update drivers, lower VRAM heavy settings, install 32GB RAM, use NVMe SSD.

What CPU is best for Ashes of Creation

AMD Ryzen X3D processors (5800X3D, 7800X3D, 9800X3D) provide the best MMO performance. The massive L3 cache reduces latency when processing hundreds of player entities. Intel 13th and 14th gen K-series need latest BIOS microcode updates to prevent UE5 crashes from voltage instability.

How do I fix memory leak issues in Ashes of Creation

The Alpha Two client consumes 20 to 30GB of RAM over extended sessions. Upgrade to 32GB RAM if possible. With 16GB, use Process Lasso to automatically trim working set when AOC.exe exceeds 80 percent of system memory. Restart the client every 2 to 3 hours to clear accumulated memory.

Full Performance,
No Cost

Kick off an exciting adventure for free! Just download the app, create your account, and enjoy up to 20 optimizations at no cost.

Muhib Nadeem

Muhib Nadeem

I grew up on frame drops, boss fights, and midnight queues. Now I write about games with the same energy I once saved for ranked.

Level Up
Your FPS

Kills background lag

Instant FPS boost

One-click setup

Table of Contents

You may also like