To improve server performance in Ark: Survival Evolved, you adjust engine settings in the GameUserSettings.ini file, primarily the [/Script/ShooterGame.ShooterGameUserSettings] and [ServerSettings] sections. The most impactful settings are MaxFrameRate, PreventSpawnAnimations, ServerCrosshair, and bUseFixedTimeStep, along with disabling unnecessary visual effects and limiting structure/tame counts. This article explains each setting, how to edit the file safely, and what to expect in terms of performance gains.
Background: Why Ark Servers Lag
Ark is an Unreal Engine 4 game, and its dedicated servers run the full game logic, including physics, AI, and structure rendering (even without a visible screen). The server’s CPU is the bottleneck: every dinosaur, structure, and player action is simulated continuously. Common causes of server lag include:
- Too many wild dinos and spawns – the game constantly checks and respawns creatures.
- Large structures with many pieces – each piece adds to the network and physics load.
- High player counts – more players means more network traffic and more AI activity.
- Unoptimized engine defaults – Ark’s default settings are aimed at client visuals, not server throughput.
How Engine Settings Work on a Server
Unlike client settings, server engine settings are stored in GameUserSettings.ini (in the ShooterGame/Saved/Config/WindowsServer folder). The server reads these on startup. Key sections:
[/Script/ShooterGame.ShooterGameUserSettings]– general graphics and engine toggles.[/Script/Engine.Engine]– physics and tick settings (rarely used, but some admins add it).[ServerSettings]– gameplay-related settings that also affect performance (e.g.,DinoCountMultiplier).
Editing these files requires stopping the server, making a backup, and then restarting. Incorrect values can prevent the server from starting, so always test on a copy first.
Key Settings to Change for Better Performance
These are the most effective settings to adjust, in order of impact:
- MaxFrameRate=60 – Limits the server’s tick rate. Default is 0 (unlimited), which can waste CPU. 30 or 60 is fine; 60 is recommended for smooth player movement.
- PreventSpawnAnimations=True – Disables the spawn-in animation for dinos, reducing CPU load when many creatures spawn.
- ServerCrosshair=False – Disables the crosshair on the server (it’s a client setting, but disabling it reduces network data). Actually, this is client-side; the server setting that matters is
bDisableStructurePlacementCollision? No – the real performance one isServerNetTickRate? Keep reading. - bUseFixedTimeStep=False – In Unreal Engine, a fixed time step forces the server to update physics at a constant rate. Setting it to False can reduce CPU usage, but may cause inconsistent physics. Most admins leave it as is.
- NetServerMaxTickRate=30 – Controls how many times per second the server sends updates to clients. Lower = less CPU and bandwidth, but can feel laggy. 30 is a good balance.
- DinoCountMultiplier=0.5 (in
[ServerSettings]) – Halves the number of wild dinos, directly reducing AI load.
How to Edit the INI File Safely
Follow these steps to change settings without breaking your server:
- Stop the server process.
- Navigate to
ShooterGame/Saved/Config/WindowsServer/and openGameUserSettings.iniwith a text editor (Notepad++ recommended). - Find or create the
[/Script/ShooterGame.ShooterGameUserSettings]section. It usually exists near the top. - Add or modify lines like
MaxFrameRate=60andPreventSpawnAnimations=Trueunder that section. - For
NetServerMaxTickRate, add it under[ServerSettings](not the engine section). - Save the file, then start the server and monitor the console for errors.
If the server fails to start, restore the backup and check for typos (e.g., missing equals sign, extra spaces).
Common Misconceptions and Mistakes
One common mistake is confusing client-side graphics settings with server settings. For example, ViewDistanceQuality and TextureQuality do nothing on a dedicated server because there is no GPU rendering. Another is setting MaxFrameRate too low (e.g., 10) – this will cause rubber-banding and delayed inputs. Also, some guides recommend bSpawnAllowDinos=False which disables all wild dinos – that’s a gameplay change, not a performance tweak, and it makes the game empty.
Another misconception is that increasing NetServerMaxTickRate improves performance. It actually increases CPU and bandwidth usage – the opposite. Lowering it to 20-30 reduces load, but below 20 makes the game feel unresponsive.
Comparing Performance Settings: What Actually Helps
Not all settings are equal. Here’s a comparison based on typical server reports:
- MaxFrameRate=60 – High impact, low risk. Prevents the server from running at 200+ FPS and wasting CPU.
- PreventSpawnAnimations=True – Medium impact, no downside. Reduces CPU spikes when many dinos spawn.
- NetServerMaxTickRate=30 – Medium impact, but can affect player experience if set too low.
- DinoCountMultiplier=0.5 – High impact, but changes gameplay (fewer dinos to hunt/tame).
- bUseFixedTimeStep=False – Low impact, may cause physics glitches. Not recommended.
- StructurePreventDecay – Not a performance setting; it affects decay timers.
Costs and Hardware Considerations
Engine settings can only do so much. If your server still lags after optimization, the hardware is likely insufficient. Ark servers are CPU-intensive, especially with many mods. A dedicated CPU (e.g., Intel i7 or AMD Ryzen 7) with high single-core performance is recommended. RAM is also important – 8GB is the minimum, but 12-16GB is safer for larger maps with mods. Upgrading your hosting plan or dedicated machine is often the only real solution for high player counts (50+).
Alternatives to Engine Settings
If editing INI files isn’t enough, consider these alternatives:
- Use a server manager tool like Ark Server Manager (ASM) – it provides a GUI for many settings and helps avoid typos.
- Install performance mods like ARK Server Performance (if available for your version) – but be cautious with mods, as they can introduce their own issues.
- Reduce map size – play on smaller maps like The Center or Ragnarok instead of the massive Aberration or Extinction.
- Schedule restarts – Ark servers accumulate memory leaks; a daily restart can help maintain performance.
Frequently Asked Questions
Q: What is the best MaxFrameRate for an Ark server?
A: 60 is the sweet spot. It provides smooth gameplay without wasting CPU. Setting it to 30 can save more CPU but may feel slightly less responsive for players. Never set it below 20.
Q: Where do I put NetServerMaxTickRate in the INI?
A: It goes under [ServerSettings], not the engine section. For example: NetServerMaxTickRate=30. It controls the network update rate, not the game tick rate.
Q: Will these settings work on a Nitrado or G-Portal server?
A: Yes, most hosting providers allow you to edit the INI files via their control panel. Look for a “Config Files” or “Expert Settings” section. The file path is the same, but you may need to use their built-in editor.
Q: Can I change these settings without restarting the server?
A: No, engine settings are read at startup. You must restart the server for changes to take effect. Some settings like DinoCountMultiplier may require a full world save and restart to apply cleanly.
Q: Why does my server still lag even after setting MaxFrameRate=60?
A: If the CPU is still maxed out, the bottleneck is likely too many dinos or structures. Try lowering DinoCountMultiplier to 0.5, and ask players to limit their base size. Also check for mods that are poorly optimized.
Q: Is it safe to set PreventSpawnAnimations=True?
A: Yes, it’s a common and safe setting. It only removes the visual spawn animation for wild dinos, which has no gameplay impact and reduces CPU spikes.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Microsoft Surface Duo: The Foldable Phone Story
- Samsung SM-T813 Hard Reset: Step-by-Step Guide
- Mafia Clash Codes: Real Meanings & Usage
- Remove Programs from Mac: Full Uninstall Guide
- Project Sentinel Morning Digest: Data Stack Failure Alerts
- Best KVM VPS Hosting: Top Picks & Guide