Start with a clean baseline
Use one repeatable area to compare changes. Record resolution, display mode, frame cap, upscaling choice, controller or keyboard input and whether the issue happens during travel, combat or menus. Without a baseline, every setting change becomes another guess.
Change one category at a time. Test display and frame pacing before changing visual quality, then test input focus and controller mapping separately.
- Record the current settings before changing them
- Test in the same scene
- Separate performance, display and input checks
Troubleshoot in a safe order
Confirm the game and platform launcher are updated, then check drivers and background overlays. If a problem appears only after a patch, compare the update note with the setting that changed instead of deleting every configuration file immediately.
Keep backups before editing configuration files. A clean rollback is more useful than a long list of undocumented tweaks.
- Check official update and platform notices
- Disable one overlay or variable at a time
- Back up configuration before manual edits
Performance is part of combat clarity
A stable image and consistent input path make timing easier to read. Prioritize the settings that preserve clarity in motion, then adjust detail settings around that baseline. The best setting is the one you can repeat, not the one that looks impressive for one screenshot.
- Prefer consistent frame pacing over a single peak number
- Keep combat readability in mind
- Record hardware and driver context when reporting an issue