# WuWa-Configs ships five Engine.ini tiers and the UserEngine.ini trap that breaks them

> WuWa-Configs is a set of prewritten Engine.ini files and optional launch options for Wuthering Waves, arranged as five GPU tiers plus ray tracing variants, aimed at players who want a specific frame rate or visual level rather than the game's default preset. The trap is UserEngine.ini: if it exists in the Config folder, the shipped Engine.ini quietly stops working.

**AlteriaX/WuWa-Configs** — WuWa configs to improve visuals or performance

- Repository: https://github.com/AlteriaX/WuWa-Configs
- Stars: 1,778 · Forks: 82
- Language: Unknown
- License: not declared
- Published: 2026-10-16 · Updated: 2026-10-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/alteriax-wuwa-configs

## The install is a file copy into WindowsNoEditor, not a mod loader

There is no installer and no launcher integration. You pick one config, copy Engine.ini and any of the other ini files into the game's saved config directory, and the game reads them on next launch. The target path differs by distribution:

```
...Wuthering Waves\Wuthering Waves Game\Client\Saved\Config\WindowsNoEditor (Launcher)
...Wuthering Waves\Client\Saved\Config\WindowsNoEditor (Steam)
```

The repository layout is plain enough to inspect before you copy anything: five numbered directories from Config 1 to Config 5, an RT Configs directory for ray tracing variants, a Common directory holding the optional files, and nothing else but the README.

One piece of advice in the README is easy to miss. The comments you add inside the file will disappear when the game launches, because the engine rewrites it. So any note you leave yourself inside Engine.ini is temporary, and keeping your own notes somewhere else is the only way they survive an update.

## UserEngine.ini silently overrides what you just installed

This is the failure mode worth understanding before anything else. The README marks it as important: the current Engine.ini will not work properly unless you delete UserEngine.ini if you still have it. That file lives one level up from where you copy the config:

```
...Wuthering Waves\Wuthering Waves Game\Client\Config (Launcher)
...Wuthering Waves\Client\Config (Steam)
```

There is a second half to the same trap. If you previously added -EngineIni=Engine.ini to the Steam launch options or to an exe shortcut, that argument has to come out too. Leaving it in place keeps pointing the game at an explicit file and can keep your new Engine.ini from taking effect.

The symptom of getting this wrong is that nothing visibly changes after a careful install, which is exactly the situation the FAQ opens by warning people to read the instructions before asking on Discord. If a config appears to do nothing, check those two locations before changing anything else.

## Five configs chosen by GPU, not by a frame rate target

Configs 1 through 5 are ordered from the most demanding to the least, and each lists the cards it was written for across NVIDIA, AMD and Intel. Config 1 covers RTX 5090, 5080, 5070 Ti, 4090 and 4080 on the NVIDIA side and RX 9070 XT plus 7900 XTX on AMD, with no Intel entry. Config 3 is where Intel Arc appears, listing B580, B570, A770, A750 and A580 alongside GTX 1660 and RX 7600 class parts. Config 5 is the bottom of the list, down to GT 1030, MX 450, Radeon Vega iGPU and Iris Xe.

The README is direct about how to use the table: if your card is not listed, look it up on TechPowerUp and judge by relative performance, then take the nearest tier. It also states plainly that you do not have to follow the table exactly, and that any config can be used to reach your target frame rate or visual level.

That flexibility is real, but it moves the work to you. Each config is a starting point in an Unreal Engine ini file, and the values that produce your target are not enumerated anywhere in the README. Tuning means reading the file and adjusting settings yourself, with the in-game Graphics Quality Preset still available afterwards. The FAQ confirms that changing in-game settings is allowed and will not override what the ini files set, which is what makes that combination workable.

## The Common folder adds an unsupported 120 FPS option and removes mouse smoothing

Two optional files live in the Common directory, and both exist to work around restrictions rather than to raise quality. DeviceProfiles.ini is what makes the Ultra Quality Preset and the 120 FPS option appear on GPUs that do not officially support them. The README links the official announcement and states the requirement plainly: a CPU that supports 120 FPS.

That caveat is the whole point. The option becomes visible, and whether the machine can hold the frame rate is a separate question the ini file cannot answer. Expect to tune downward after enabling it.

Input.ini disables mouse smoothing and field-of-view scaling, which is a preference change rather than a graphics fix. Copy it only if you want aim and framing to behave that way, since nothing in the ini files relates to it.

One FAQ entry covers the failure these files can cause: if character shadows vanish or textures go blurry, switch to another Graphics Quality Preset and back to the same one, then customise afterwards.

## Launch options set the renderer, the resolution and the resource tier

The README lists a set of launch arguments that apply to Steam and to exe shortcuts. The resource tier argument -krqlv takes UHD, HD or SD and is described as required, because the game will not launch without it. Resolution is set with a pair:

```
-SkipSplash Skip intro videos
-dx11 Launch the game with DX11
-dx12 Launch the game with DX12
-ResX Sets horizontal resolution (example usage: -ResX=2560)
-ResY Sets vertical resolution (example usage: -ResY=1080)
-krqlv Sets the resource tier, values: UHD, HD, SD (example usage: -krqlv=UHD)
```

Note that -SkipSplash only skips the intro videos. It does not skip the launcher, and there is no documented argument for frame rate, fullscreen mode or a config file path other than the -EngineIni=Engine.ini one the README tells you to remove.

## The FAQ answers the ban question with an anecdote

The FAQ is short and answers the questions people actually ask. Read-only ini files are unnecessary. Game updates do not reset the ini files to default, so you do not need to redownload after every patch, though the README suggests trying the latest version if something breaks. In-game settings can be changed and will not override the ini values.

The fourth answer is the one to read carefully: the ban question is answered with the maintainer's own practice rather than with an official policy. The answer is that the maintainer has been editing the ini files since release with no issues. That is a statement about one person's account, not a guarantee from the publisher, and the repository carries no statement from the developer about permitted configuration changes.

What the rest of the repository offers is documentation rather than argument: an explanations and image comparisons site, a separate page for using old colour settings, and a decrypt page for the log file.

## Ray tracing lives in a separate directory with no GPU guidance

The top-level listing includes RT Configs/ alongside the five numbered tiers, but the README's GPU table covers only the standard configs. No hardware requirements, no explanation of which ray tracing options are enabled or disabled, and no comparison against the stock preset are given for the RT directory.

The references listed at the end of the README are Unreal Engine 4.27 command references and documentation plus a UE forum link, which tells you the settings vocabulary these files draw on but not how they map onto current game behaviour. The explanations site linked near the top is where the before-and-after comparisons live.

The last push was on 2026-09-30 and the repository has no GitHub releases, so there is no tagged version to pin to and no changelog to check when a patch changes something. Downloads come from the repository itself, and the ko-fi link at the bottom is the author's support page.

## Conclusion

WuWa-Configs is worth using if your GPU sits in one of the five listed tiers and the stock preset overshoots or undershoots your target, since each tier is a starting point the README explicitly says you do not have to match exactly. Skip it if you are on a Linux or Steam Deck install, if you rely on an existing UserEngine.ini tuned by another mod, or if you want ray tracing values, because those live in a separate RT Configs directory with no GPU table attached. First check the Config folder for UserEngine.ini and remove it, then remove any -EngineIni=Engine.ini you previously added to the Steam launch options, since leaving either in place is what makes the config appear to do nothing.

## FAQ

### Where do I copy the WuWa-Configs ini files?

Into the game's saved config directory: ...Wuthering Waves\Wuthering Waves Game\Client\Saved\Config\WindowsNoEditor for the Launcher, or ...Wuthering Waves\Client\Saved\Config\WindowsNoEditor for Steam. Copy one Engine.ini from the config tier you chose, plus any of the optional files from Common.

### Why is nothing changing after I install WuWa-Configs?

The README states the current Engine.ini will not work properly if a UserEngine.ini still exists, and that file sits one level up in the Config folder. You also need to remove -EngineIni=Engine.ini from the Steam launch options or exe shortcut if you added it earlier.

### Can I get banned for editing these ini files?

The FAQ says no, and the only support given is that the maintainer has been changing the ini files since release with no issues. That is a personal account rather than a policy statement from the publisher.

### Do I need to redownload the config after every game patch?

The FAQ says game updates do not reset the ini files to default, so a redownload is not required. If you hit problems, the README suggests trying the latest version of the config.

### How do I unlock the 120 FPS option on an unsupported GPU?

Copy DeviceProfiles.ini from the Common folder, which makes the Ultra Quality Preset and the 120 FPS option appear. The README notes that you must have a CPU that supports 120 FPS for it to be usable.

### Which config should I use for my graphics card?

The README maps Config 1 through Config 5 to GPU lists across NVIDIA, AMD and Intel. If your card is not listed, look it up on TechPowerUp and compare relative performance, and note that the README says you can use any config to reach your target frame rate or visuals.

## Sources

- [AlteriaX/WuWa-Configs on GitHub](https://github.com/AlteriaX/WuWa-Configs)
- [Issues](https://github.com/AlteriaX/WuWa-Configs/issues)
- [README](https://github.com/AlteriaX/WuWa-Configs/blob/main/README.md)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/alteriax-wuwa-configs