PC & saves
PC performance settings: crowd density, memory and stutter tradeoffs
Start with a graphics preset, then compare one setting on the same route. Update 4 adds Crowd Density, Pooling and Hybrid CPU Optimization. Lower crowd density can offer a small performance improvement; disabling Pooling reduces memory use but can increase stutter. The right choice depends on the symptom you actually have.
Update 6 fixes leaks between areas and releases leftover lighting/reflection resources. It also makes lists faster. These changes are not a promised FPS increase on every PC, a repair for every crash or a measured benchmark by this Wiki.
Nivalis Nights / PC performance
Match the option to the symptom.
- Low FPS
Compare a preset and crowd density.
- Memory pressure
Pooling off trades memory for possible stutter.
- Long sessions
Confirm Update 6 and record the same transitions.
On this page
Make a useful baseline
- Record your game build, GPU, CPU, memory, resolution and chosen preset.
- Choose one busy outdoor route and an area transition you can repeat.
- Distinguish sustained low FPS, short stutters, rising memory use and a crash during loading.
- Change one relevant option, repeat the same route and record the result.
- Keep the change only if it improves the symptom without an unacceptable tradeoff.
Choose the option that matches the problem
| Option or change | What the source establishes | Decision |
|---|---|---|
| Crowd Density | Fewer characters; a small performance boost is possible. | Compare a busy scene. Do not assume it fixes all GPU or loading limits. |
| Pooling | Turning it off saves memory but may add stutter. | Try it for memory pressure; compare frame pacing as well as RAM. |
| Hybrid CPU Optimization | For Intel CPUs with performance/efficiency cores, including 12th generation and later/Core Ultra. | Check your CPU first; this is not a universal AMD or old-Intel tweak. |
| Low-memory area loading | The previous area unloads before the next, allowing longer loads to reduce memory pressure. | A longer transition can be a memory tradeoff rather than proof the fix failed. |
| Update 6 resource cleanup | Area-to-area leak, leftover rendering resources and list performance fixes. | Confirm the installed build; record any remaining reproducible case. |
Use the official PC checks before speculative fixes
The FAQ recommends current graphics drivers, closing unnecessary background applications and verifying the game through Steam. On a laptop, connect power, use the appropriate performance mode and ensure the game uses the dedicated GPU where available. Compare the machine with the game’s stated requirements.
The dated FAQ says native DLSS/FSR is unsupported by the game’s Unity engine version. It describes future evaluation, not an available toggle. This guide provides no unofficial DLL, frame-generation mod or launch command. Brightness and Thunder Intensity are visibility options, not an established FPS fix.
A remaining crash needs a specific report
Record the exact area, transition, save, settings and steps that reproduce it, plus your hardware and any error. Compare the same case after updating before declaring the memory issue resolved. Keep a separate save backup.
For Deck, use the dated Deck input and performance reports; PC option descriptions do not establish an official Verified rating or identical Proton behavior. Success here is a repeatable improvement or a documented unresolved case, not a universal “best settings” claim.
Sources & version
Use the version and source dates listed for this article. Developer fixes, dated creator demonstrations and player reports are distinguished; a current review does not turn an older source into a new-build gameplay test. We do not claim our own gameplay reproduction.