Settings & Performance Optimization (ASA)
Practical graphics presets, launch options, console command tips, and rollback-safe tuning steps for better FPS and smoother ARK: Survival Ascended sessions.
- Best for
- Players balancing playable FPS with readable visuals on ASA
- Focus
- The highest-payoff changes first, with clear caveats before you touch riskier tweaks
- Use this guide when
- You want a cleaner ASA setup without guessing which settings actually matter
On this page
Quick performance rule
Start here: safe FPS wins first
ASA can eat performance in several different ways at once, so the fastest route is to remove the biggest visual costs first, then test again before you stack on extra tweaks.
1. Biggest easy gains
- • Lower Resolution Scale to 70-85% on weak hardware or 90-100% on mid-range systems.
- • Disable Motion Blur.
- • Disable Foliage & Fluid Interaction.
- • Disable Virtual Shadows with console or Engine.ini.
2. Retest in the right place
- • Test in the same biome or base every time.
- • Watch both average FPS and frame pacing.
- • Judge clarity while moving, not while standing still.
- • Keep notes so you can undo bad changes fast.
3. Add riskier tweaks last
- • Treat launch options as patch-sensitive, not guaranteed wins.
- • Use Engine.ini only after you know which commands help.
- • Windows security and BIOS changes need caveats.
- • If a tweak feels unclear, skip it and keep the stable gains.
Before you change anything
- Pick one repeatable test area. A busy base, a forest run, and a water-heavy shoreline can all stress the game differently.
- Check your current baseline. Note your render scale, preset, and whether you are using DLSS or FSR before you start.
- Change one group at a time. Do not alter graphics, launch options, and Windows settings in one pass or you will never know what actually helped.
- Keep rollback notes. A simple text file with your old values is enough.
- Favor stable frame pacing over a screenshot number. A slightly lower average that feels smooth is usually better than a spiky higher average.
Good tuning order
- Step 1: Resolution Scale and upscaling choice
- Step 2: Shadows, blur, foliage interaction, cinematic extras
- Step 3: A few console commands with clear purpose
- Step 4: Save only the commands that proved useful
- Step 5: Optional launch options and Windows tweaks
DLSS, FSR, frame generation, and Resolution Scale
Upscaling is usually the first place to look because it changes the cost of the whole frame. It is also the easiest place to overshoot and make ASA look muddy, so tune it with the same care you would give a weapon sight or map readability setting.
NVIDIA DLSS
- • DLSS support starts with RTX 2000-series hardware.
- • Frame Generation is for RTX 4000-series cards.
- • Usually the best quality-per-FPS option when it is available.
- • Start by testing balanced-quality style options before dropping render scale hard.
AMD FSR
- • Works across far more hardware, including non-RTX setups.
- • Good fallback when DLSS is not available.
- • Frame Generation behavior can feel worse on some AMD setups or game versions.
- • If input lag or odd pacing appears, test with frame generation off.
Resolution Scale
- • Works on every GPU.
- • 70-85% is the blunt-force FPS option for weaker systems.
- • 90-100% is a strong starting band for mid-range systems.
- • Native 100% makes the most sense when you already have headroom.
AMD frame generation caveat
If you suspect FSR frame generation is causing input lag or odd responsiveness on your setup, test without it first. The common rollback command is r.FidelityFX.FI.Enabled 0.
| Goal | Starting point | Tradeoff to watch |
|---|---|---|
| Maximum readability | DLSS Quality or 100% Resolution Scale | May not be enough in dense bases |
| Balanced daily play | DLSS/FSR balanced or 90-100% Resolution Scale | Some softness in foliage and distant detail |
| Save weak hardware | 70-85% Resolution Scale plus lower shadows | UI/world sharpness drops first |
Recommended graphics presets by hardware tier
These are starting presets, not laws. The point is to land close to stable performance fast, then move one or two expensive settings after you have a reliable baseline.
High-end PC
RTX 4080-class and above
- • Resolution: native
- • Resolution Scale: 100%
- • Window Mode: fullscreen
- • VSync: off
- • Frame cap: uncapped or monitor-matched
- • Global Quality: High
- • View Distance: Epic
- • Shadows: High, but still consider disabling Virtual Shadows
- • Textures: Epic
- • Effects: High
- • Global Illumination: High
Use this tier to preserve clarity first; do not lower half the menu unless you actually need the extra headroom.
Mid-range PC
RTX 3060-4070 class
- • Resolution: 1080p or your native panel with upscaling
- • Resolution Scale: 90-100%
- • Window Mode: fullscreen
- • VSync: off
- • Frame cap: uncapped or modest cap for steadier pacing
- • Global Quality: Medium
- • View Distance: High
- • Shadows: Medium
- • Textures: High
- • Effects: Medium
This is the common sweet spot: keep textures readable, then buy FPS from shadows, extras, and render scale.
Low-end or FPS-first setup
When smooth play matters more than eye candy
- • Resolution: 1080p or lower
- • Resolution Scale: 70-85%
- • Window Mode: fullscreen
- • VSync: off
- • Frame cap: uncapped unless a cap gives cleaner pacing
- • Global Quality: Low
- • View Distance: Medium
- • Shadows: Low
- • Textures: Medium
- • Effects: Low
If this still struggles, focus on commands and environment costs before you start throwing random launch flags at the game.
Common first cuts
The usual first settings worth reducing or disabling are Foliage & Fluid Interaction, Motion Blur, Cinematic Lighting, and Virtual Shadows. They are not automatically wrong for every machine, but they are frequent offenders when ASA feels heavier than it should.
High-impact console commands
Press TAB to open the console, apply one group at a time, and retest. Commands are useful because they are easy to trial, but that only helps if you stay disciplined about what changed.
Biggest general-purpose cuts
r.VolumetricCloud 0
Cuts expensive volumetric cloud rendering. Good first test in open skies.
r.VolumetricFog 0
Helps when fog and atmospheric effects are eating visibility and performance.
r.Shadow.Virtual.Enable 0
One of the most common performance wins and sometimes a fix for shadow instability.
r.Lumen.Reflections.Enable 0
Useful near water or reflective surfaces when you need relief more than perfect scene fidelity.
Visibility and environment tweaks
r.Water.SingleLayer.Reflection 0
Reduces water reflection cost; useful on maps or routes with lots of shoreline play.
grass.densityScale 1
Reduces grass density from the heavier default behavior, helping both FPS and sightlines.
grass.sizeScale 0.5
Shorter grass can make the world easier to read, especially in PvP or creature tracking.
r.DistanceFieldShadowing 1
A lower-priority test. Use it only as part of shadow comparisons because the benefit can vary by scene and patch.
Recommended test batches
Try a shadow batch first, then a cloud/fog batch, then grass and water. If you apply every command at once and dislike the result, you will not know which command to keep.
Saving commands in Engine.ini
Once you find commands that actually help, save only those. A short clean config is better than a giant tweak list you no longer understand.
Path: ARK Survival Ascended\ShooterGame\Saved\Config\Windows\
Example Engine.ini block
[/script/engine.renderersettings]
r.Shadow.Virtual.Enable=0
r.VolumetricCloud=0
r.VolumetricFog=0
[/script/engine.systemsettings]
grass.densityScale=1
grass.sizeScale=0.5
Use = in the file, not spaces like the live console commands.
Useful habits
- • Keep a backup of the file before large edits.
- • Add only the commands you tested successfully in game.
- • Remove old experiments instead of piling them up forever.
- • If you need to run multiple console commands temporarily, chain them with pipes.
Example command chain
grass.densityScale 1 | r.Shadow.Virtual.Enable 0 | r.VolumetricCloud 0
Steam launch options: safe first, experimental later
Launch options are worth treating carefully because some are patch-sensitive, some are old habits carried over from other games, and some help only on certain rigs. Use them as optional tests, not as a magical required string.
Where to set them
- Right-click ARK in your Steam library.
- Open Properties.
- Stay on the General tab.
- Paste only the options you actually want to test.
Commonly tested bundle
-USEALLAVAILABLECORES -high -lowmemory -nomansky
What the common flags try to do
-USEALLAVAILABLECORES— intended to let the game use all CPU cores.-high— requests higher process priority.-lowmemory— aimed at reducing memory pressure.-nomansky— intended to reduce some sky-related rendering cost.
Patch-sensitive and last-resort flags
These options are worth treating as experimental. Keep them out unless you have a clear reason to test them on your own hardware:
- •
-sm4— major visual downgrade and may no longer be useful depending on the build. - •
-d3d10— same story; treat as a legacy last resort. - •
-novsync— use only if VSync appears stuck on. - •
-maxMem=X— only for targeted testing. - •
-cpuCount=X— only if you have a very specific CPU-threading reason.
Windows optimizations: safe first, advanced last
System-level changes can help, but they carry more tradeoffs than in-game settings. Start with the low-risk toggles before you touch security features or BIOS options.
Safe first-pass checks
1. Game Mode
Settings → Gaming → Game Mode → ON
2. Hardware GPU Scheduling
Settings → Display → Graphics → Hardware-accelerated GPU scheduling → ON
3. Power plan
Control Panel → Power Options → High Performance, or the closest equivalent that avoids aggressive throttling. Laptop players should also watch heat and battery impact.
Advanced or caveat-heavy checks
4. Resizable BAR
Check your motherboard BIOS and GPU support. Useful on modern hardware, but verify it is supported before you start toggling firmware settings.
5. Memory Integrity
Windows Security → Device Security → Core Isolation → Memory Integrity. Disabling it can help on some systems, but it is a security tradeoff, not a universal recommendation.
Rule of thumb
If a Windows tweak changes security posture, firmware, or power draw, leave it until after you have already exhausted the easy wins inside the game itself.
Optional QoL settings for single-player or private servers
This is not client performance tuning, but it matters for the overall experience. If you control the server or your own save, these are the settings most players adjust first to make ASA feel less grind-heavy.
| Setting | Common range | Why players change it |
|---|---|---|
| Taming Speed | 2.0x - 5.0x | Shorter tame windows without skipping the whole process |
| Harvest Amount | 2.0x - 3.0x | Less grind per farming run |
| XP Multiplier | 2.0x - 3.0x | Faster early and mid-game progression |
| Breeding Maturation | 5.0x - 10.0x | Shorter baby-raising cycles |
| Stack Size | 5.0x - 10.0x | Cleaner inventory management |
| Stamina Drain | 0.5x | Longer runs and flights |
| Food Drain | 0.5x | Less routine upkeep |
Player stat settings people often change
- • Health / Stamina / Weight per level: 2.0x-2.5x
- • Movement Speed: enable only if your group wants it; official-style balance leaves it disabled.
- • Fortitude per level: 2.0x if you want temperature management to be less punishing.
Troubleshooting by symptom
When a problem has a clear pattern, troubleshoot the pattern instead of blindly lowering every setting. That keeps the guide useful even when one specific tweak stops helping after a patch.
Problem: constant crashes
- Verify game files in Steam.
- Update graphics drivers.
- Lower texture quality if you suspect VRAM pressure.
- Test
-lowmemoryonly as a targeted launch option, not as a permanent assumption. - Close heavy background applications and overlays.
Problem: stutter or hitching
- Disable Windows fullscreen optimizations for the game executable if the issue appears transition-related.
- Increase or uncap shader cache in your GPU control panel if your driver allows it.
- Move the game to SSD storage if it still lives on an HDD.
- Disable overlays such as Discord or Steam while testing.
- Retest with fewer background apps before you rebuild your whole config.
Problem: low FPS in big bases
- Reduce view distance and shadow quality first.
- Turn off expensive reflections if your base sits near water or heavy lighting.
- Limit decorative light sources where possible.
- Glass-heavy structures and dense clutter cost more than many players expect.
- If you run a private server, review structure count and building habits before blaming only your GPU.
Quick checklist and rollback notes
You do not need every tweak in this guide. The goal is to finish with a cleaner setup than you started with, not the longest tweak list on the internet.
First-pass checklist
- ☐ Lower Resolution Scale to an appropriate band for your hardware
- ☐ Disable Motion Blur
- ☐ Disable Foliage & Fluid Interaction
- ☐ Test Virtual Shadows off
- ☐ Compare one cloud/fog command batch
- ☐ Save only the commands that actually helped
Rollback checklist
- ☐ Remove one recent change group at a time if image quality fell too far
- ☐ Delete experimental launch flags before blaming stable settings
- ☐ Restore your Engine.ini backup if a config edit caused trouble
- ☐ Re-enable security-related Windows features if you tested them and saw no benefit
- ☐ Keep the stable gains; throw out the guesswork