The primary bottleneck in New World is CPU Draw Call Latency. In large-scale PvP, the engine struggles to synchronize the animations and spell effects of 100+ players simultaneously. Modifying the user_settings.json allows us to implement a “War-Ready” profile: reducing the internal shadow resolution beyond the menu limits and disabling the “Depth of Field” layers that add unnecessary GPU weight during high-speed combat.
Hardware Compatibility & Expectations
- CPU Bottlenecking: In settlements, your CPU will always be the bottleneck. These tweaks aim to reduce the “frametime jitter” rather than just increasing max FPS.
- VRAM Usage: “Very High” textures require 8GB+ VRAM. If you have a 6GB card, these config edits are essential to prevent “Texture Swapping” stutters.
- DirectX 12 vs 11: New World: Aeternum features improved DX12 support; these config tweaks are optimized to work with the DX12 pipeline for better multi-core scaling.
Backup and Preparation
New World’s configuration is sensitive to formatting. If the JSON structure is broken, the game will reset to defaults.
- Completely exit New World.
- Navigate to your local AppData folder (path below).
- Right-click user_settings.json, select Copy, and save a backup copy on your desktop.
- Open the original file with Notepad++.
File Location
The configuration file is located in your local user directory: C:\Users\%USERNAME%\AppData\Roaming\AGS\New World\user_settings.json
Best Settings for Aeternum Performance
Search for these specific keys within the JSON. Update the values to match this “Performance” profile:
{
"m_visualQuality": 0,
"m_shadowQuality": 0,
"m_lightingQuality": 0,
"m_objectDetail": 0,
"m_textureDetail": 1,
"m_terrainDetail": 0,
"m_waterDetail": 0,
"m_postProcessingQuality": 0,
"m_vSync": false,
"m_depthOfField": false,
"m_motionBlur": false,
"m_maxUploadBandwidth": 100
}
Pro Tip: Changing
m_maxUploadBandwidthto 100 (if your internet allows) can help reduce “Desync” during crowded wars by allowing the client to communicate more frequently with the server’s update tick.
Key Parameters Explained
| Parameter | Recommended Value | Impact |
| m_shadowQuality | 0 | Lowest possible shadow resolution; the #1 fix for town FPS. |
| m_depthOfField | false | Removes the background blur, improving long-range visibility for Muskets and Bows. |
| m_textureDetail | 1 | Set to “1” (Medium) to maintain visual clarity while saving VRAM for player models. |
| m_maxUploadBandwidth | 100 | Optimizes network throughput to combat the “sliding players” effect in PvP. |
| m_postProcessingQuality | 0 | Disables lens flares and bloom that can be distracting during magic-heavy fights. |
In-Game Settings vs. Config
To complement your performance config, match these in-game Visuals settings:
- Max Nameplates: Set to 10. Rendering 50+ nameplates in a war is one of the biggest CPU killers in the game.
- Player Cap: Set Nameplate Amount to the minimum required for your role (Healers may need more).
- Dynamic Resolution Scaling: Set to OFF. This causes a “shimmering” effect that makes it harder to track distant enemies.
- NVIDIA Reflex: Set to Enabled + Boost. This minimizes the input lag between your mouse click and the weapon swing.
Troubleshooting & Common Fixes
- Stuttering in Settlements: This is often caused by the game loading player skins. Ensure the game is installed on an NVMe SSD.
- Textures Not Loading: If the ground looks like mud, increase
m_textureDetailto 2. - Settings Resetting: New World often overwrites the JSON after a patch. Once satisfied, right-click user_settings.json, select Properties, and check Read-only.
Frequently Asked Questions (FAQ)
Does “Low” Object Detail affect gathering?
No. Nodes (Iron, Hemp, etc.) are rendered based on a separate distance flag. Setting Object Detail to 0 (Low) primarily affects distant buildings and non-interactive foliage.
Why disable VSync in the config?
New World’s internal VSync implementation can cause significant “Input Lag.” It is much better to use your GPU’s control panel (G-Sync/FreeSync) or a frame rate cap.
Does this help with War “Desync”?
Partially. Desync is often server-side, but by maximizing your CPU headroom via these config tweaks, your client can process the server’s incoming data packets much faster.
Conclusion and Expected Results
By manually refining your user_settings.json, you are stripping away the heavy post-processing that bottlenecks the Azoth Engine. You can expect more stable frame rates during 50v50 wars, faster loading times in towns, and a significantly more responsive combat experience across Aeternum.