Build a repeatable baseline
Use a backed-up world and record your game build, CPU, GPU, memory, resolution and whether mods are active. Choose a 60-second route you can repeat: standing at base, walking through it and turning the camera toward the same structures. Keep weather, background apps and player count as similar as practical.
Write down average FPS if your overlay offers it, but also record the symptom: short freezes, consistently slow rendering, delayed interactions or movement snapping backward. Two runs with the same average can feel different if one freezes regularly. Do not present an overlay's momentary peak as sustained performance.
Repeat the baseline twice. If the two runs vary widely, stabilize the conditions before comparing a setting. A busy server changing while you test can overwhelm a small graphics adjustment.
| Run | Change | What to record |
|---|---|---|
| A1 and A2 | None; repeat the route | Usual FPS range, freezes, input feel and scene. |
| B | One lower resolution or render-scale step | Whether slow rendering meaningfully changes. |
| C | Restore A, then reduce one costly visual option | Whether the benefit is worth the visual loss. |
| D | Restore A, then compare a quiet area | Whether the problem follows the base rather than all scenes. |
Use the symptom to choose the next test
Resolution or render scale is a useful first variable because it changes how many pixels the GPU must process. If a substantial reduction helps consistently, graphics load is worth investigating further. If it barely changes the problem, stop sacrificing image quality and inspect another cause. This is an inference, not a definitive diagnosis of CPU or GPU utilization.
When available, try lower shadows or effects one at a time. Keep textures within your card's memory budget; do not assume the highest setting is free because it looked fine in an empty area. Upscaling modes are hardware- and version-dependent, so read the option description in your build rather than following a universal DLSS/FSR instruction.
| Symptom | Comparison to run | What it can suggest |
|---|---|---|
| Low FPS everywhere | Substantially lower resolution, same route | A consistent gain points toward graphics workload. |
| Only a large base stutters | Quiet area versus base, same settings | World complexity or simulation deserves investigation. |
| Character snaps back while image remains smooth | Same client solo versus shared server | Network/server behavior may be involved. |
| Problems appeared after mod/update | Clean test world and recorded prior setup | A compatibility regression rather than a permanent hardware limit. |
| Long freezes during other PC activity | Repeat without the competing task | Memory, storage or background contention may be contributing. |
Treat server pressure separately
Pocketpair explicitly notes that increasing base counts, worker limits and Pal spawn rates raises processing load. If your group increased those settings before the problem began, compare a backed-up test instance near defaults before buying a bigger machine. Never silently change another player's live world.
A lower client graphics preset cannot repair a server that is overloaded or unreachable. Ask whether all players experience delayed actions at the same moment. If only one player is affected, compare that player's connection and hardware. If everyone is affected together, server observations become more useful.
References: Pocketpair: performance-sensitive server settings
A safe reset path and a useful support report
If installed files may be damaged, Steam provides verification under Properties → Installed Files. Preserve settings and mod notes first; verification is not a promise to remove extra mod files. For driver problems, use the GPU manufacturer's official support channel rather than an unrelated 'FPS booster' executable.
Send support a compact reproduction: game build, hardware, solo/server, active mods, exact location, the repeated symptom and the single change that affected it. 'It lags' requires guessing; 'the same 60-second route freezes only at this base, while a quiet area does not' gives someone a test.
After finding a stable configuration, set a frame-rate cap your system can usually sustain and repeat the route. Keep the clearer image if a change produces no repeatable benefit. The goal is stable play, not accumulating tweaks.
References: Steam Support: verify integrity of game files
Before you play
- Hardware, game build and mods recorded.
- Same route repeated with one variable changed.
- Rendering, network and server symptoms kept separate.
- No untrusted booster or registry script installed.
Frequently asked questions
What FPS improvement should I expect?
No numerical gain is promised. GamerWin has not run hardware benchmarks for this article; use the repeated comparisons on your own machine.
Should I lower every setting at once?
That may be a temporary baseline, but it cannot show which setting helped. Restore and compare one variable when diagnosing the cause.
Sources & revision notes
Editorial revision: September 11, 2026. Source notes give the scope of each reference; the revision date is not a gameplay test date. Official documentation describes the publisher's system; community sources can contain errors. Use your installed game's own descriptions when they disagree.
- Pocketpair: performance-sensitive server settings (Official)
Reference checked on September 11, 2026.
- Steam Support: verify integrity of game files (Official)
Reference checked on September 11, 2026.
Reworked the generic settings advice into a reproducible comparison worksheet; added source boundaries and separated client FPS from server delay.
How we research and correct guides