Establish a clean baseline
Record the game version, operating system, CPU, GPU, memory, storage location, resolution, driver version, and whether modifications are installed. Reproduce the problem in the same location and weather when possible.
Back up important configuration or save data using the platform's supported method before making broad changes.
For crashes or failed launch
Compare the machine with the current official requirements, update supported graphics drivers and system components, verify game files through the storefront, and remove unsupported modifications or overlays from the test.
Record the exact error message and whether the crash occurs before the title screen, during loading, or in a specific quest. That distinction is more useful than ‘the game crashes.’
For stutter or unstable frame times
Use one repeatable route and change a single setting between tests. Monitor whether the GPU is saturated, whether the CPU is limiting frame delivery, and whether background tasks or storage activity coincide with spikes.
Prioritize stable frame pacing over a higher average that repeatedly drops. Upscaling and frame generation can change presentation and latency; compare them with the same base conditions.
When to contact support
If a clean, updated installation still reproduces the problem, submit the hardware and software details, error code, reproduction steps, and troubleshooting already attempted. Check the support portal for known issues before assuming a local component has failed.
Create evidence before changing settings
Choose one repeatable route and record resolution, display mode, preset, upscaling, frame generation, driver version, and whether overlays or modifications are active. Note whether the problem occurs during traversal, combat effects, menus, or loading.
Change one variable, repeat the same route, and keep the result only when the same symptom improves without creating a worse problem elsewhere. This produces a usable support record and prevents a random combination of changes from hiding the original cause.
- Record the baseline.
- Reproduce the same scene.
- Change one variable.
- Compare frame-time behavior and stability.
- Keep or revert the change.
Practical scenarios
Average FPS is high but play feels rough
Situation: Repeated frame-time spikes interrupt camera and input despite an acceptable average.
Better response: Use a repeatable route, monitor frame-time consistency, close background interference, and change one likely bottleneck setting at a time.
The game crashes after an update
Situation: An old configuration, overlay, or modification remains active.
Better response: Record the error, verify files, remove unsupported modifications from the test, update supported drivers, and reproduce on a clean baseline.
A settings change helps once
Situation: One run appears smoother, but the test used a different locale state or background workload.
Better response: Repeat the same route under the recorded baseline before keeping the change, and note whether frame-time spikes occur in the same places.
Common mistakes to correct
- Copying settings from different hardware
- Changing every option simultaneously
- Reporting no error code or reproduction step
- Treating frame generation as a cure for all bottlenecks
- Treating one non-repeatable run as a confirmed fix
Frequently asked questions
Is there one best settings preset?
No. Hardware, resolution, target frame rate, driver, game version, and scene determine the appropriate compromise.
Should every stutter be fixed by lowering graphics?
No. CPU limits, shader activity, storage, drivers, background software, and frame pacing may be involved.
What information should a support report include?
Hardware, operating system, driver, game version, error code, exact reproduction steps, modifications, and troubleshooting already attempted.
What is the minimum useful performance report?
Include hardware, resolution, game and driver versions, key settings, modifications or overlays, the exact scene, the symptom, and reproducible steps.
Review scope
Reproducible diagnostic workflow using official support guidance; no invented benchmark results.
Sources and verification
We use first-party documentation for game systems and support guidance. Explanations and recommendations are independently written. No third-party screenshots are used, and we do not claim first-hand testing without a documented test record.
Reviewed by the Wilds Field Guide Editorial Team. See our editorial policy and corrections process.