The primary goal for Wuthering Waves performance optimization is Database-Level Frame Liberation. While the game officially supports 120 FPS, it is often hidden from the settings menu unless you have specific “validated” hardware. This configuration focuses on using a database browser to force-enable the 120 FPS setting and supplement it with Engine.ini tweaks to reduce the game’s notorious micro-stuttering.
Hardware & System Prerequisites
- SQLite Browser: You will need a free tool like “DB Browser for SQLite” to open the
.dbfile. - Monitor Refresh Rate: Ensure your monitor is actually set to 120Hz or 144Hz in Windows; otherwise, the game will still appear choppy despite the unlock.
- CPU Cooling: Unlocking the frame rate in an open-world game significantly increases CPU load. Monitor your temperatures during long farming sessions.
File Location
The database and configuration files are located in the game’s installation directory (not AppData):
Database Path (For 120 FPS): [Wuthering Waves Install]\Wuthering Waves Game\Client\Saved\LocalStorage\LocalStorage.db
Engine.ini Path (For Stutter Fixes): [Wuthering Waves Install]\Wuthering Waves Game\Client\Saved\Config\WindowsNoEditor\Engine.ini
Technical Configuration (Step-by-Step)
Phase 1: Unlocking 120 FPS (Database Method)
- Close the game and launcher completely.
- Open DB Browser for SQLite and click “Open Database.”
- Navigate to the
LocalStorage.dbfile. - Go to the “Browse Data” tab.
- Find the row where the key is GameQualitySetting.
- In the “Value” field, locate the text:
"KeyCustomFrameRate":60and change it to"KeyCustomFrameRate":120. - Click “Write Changes” and close the browser.
Phase 2: Engine.ini Stutter Fix (Code Block)
To ensure the game actually reaches 120 FPS smoothly, add these lines to the bottom of your Engine.ini:
# Wuthering Waves Stutter & FPS Optimization 2026
# Source: GameEngineer.net
[SystemSettings]
# Improves frame pacing and reduces micro-stutter
r.GTSyncType=1
r.OneFrameThreadLag=1
r.D3D11.UseAllowTearing=1
r.D3D12.UseAllowTearing=1
# Forces the game to use all available VRAM for textures
r.Streaming.FullyLoadUsedTextures=1
r.Streaming.MipBias=0
# Disable Cinematic Blur for better combat clarity
r.MotionBlurQuality=0
r.DepthOfFieldQuality=0
r.SceneColorFringeQuality=0
Strategy for Rover-Velocity Smoothness
To maintain a stable 120 FPS during intense combat:
- The Database Reset: If you change your graphics settings inside the game menu after performing this fix, the game may overwrite the
LocalStorage.dband reset you to 60 FPS. If this happens, you must repeat Phase 1. - V-Sync Conflict: Once 120 FPS is unlocked, ensure V-Sync is OFF in-game. Use the NVIDIA Control Panel to set a “Max Frame Rate” of 120 to prevent your GPU from overworking in the menus.
- Shadow Resolution: In Wuthering Waves, “Ultra” shadows have a massive performance cost. Set Shadows to Medium; this is the best way to maintain 100+ FPS in densely populated areas like Jinzhou.
Key Performance Parameters
| Parameter | Recommended Value | Impact |
| CustomFrameRate | 120 | Unlocks the engine cap for high-refresh play. |
| GTSyncType | 1 | Vital for fixing the UE4 “frame pacing” stutter. |
| Motion Blur | 0 | Increases visibility during fast Echo-switching. |
| Shadows | Medium | Saves significant CPU/GPU resources for higher FPS. |
Frequently Asked Questions (FAQ)
Is this “modding” and can I be banned?
This method modifies a local settings database, not the game’s executable or memory. It is the same as changing a .ini file in other games and is generally considered safe.
Why is my FPS still stuck at 60 after editing?
Double-check your GPU settings. If “Vertical Sync” is globally forced ON in your NVIDIA/AMD panel, it will override the game’s internal unlock.
I don’t see “GameQualitySetting” in the database.
Ensure you are looking in the “Browse Data” tab and that you have selected the correct table (usually LocalStorage). If it’s missing, change a setting in-game and restart to force the database to update.
How do I fix the “read-only database” error?
This happens if the game or the launcher is still running in the background. Check your Task Manager and kill all “Wuthering Waves” processes before editing.
Conclusion and Expected Results
By manually forcing the 120 FPS value in the LocalStorage.db and applying Engine.ini sync tweaks, you are bypassing the hardware restrictions of the standard PC client. You can expect vastly improved combat responsiveness, the elimination of the “60 FPS drag” during traversal, and a much more fluid visual experience on high-refresh-rate monitors.