PC Graphics & Performance
A controlled PC tuning and fault-isolation ladder for image quality, frame pacing, crashes and current Patch 1.16 graphics changes.
Use this page to make one measured change at a time. It does not promise a universal frame rate: Pearl Abyss states that published performance results are internal tests, and real results depend on hardware, drivers, resolution, scene and settings.
Establish the baseline
Section titled “Establish the baseline”Record:
- CPU, GPU and RAM;
- Windows version;
- launcher and game version;
- GPU driver;
- display resolution and refresh rate;
- graphics preset;
- upscaler and quality mode;
- frame generation state;
- ray tracing, Ray Reconstruction or Ray Regeneration state;
- HDR state;
- the exact scene and action used for testing.
Confirm the system meets Pearl Abyss’s current requirements before diagnosing settings.
Supported technologies
Section titled “Supported technologies”Pearl Abyss officially lists:
- AMD FSR 3 and 4;
- NVIDIA DLSS 4 and 4.5;
- Intel XeSS 3;
- AMD FSR Ray Regeneration;
- NVIDIA DLSS Ray Reconstruction;
- frame generation on PC.
Patch 1.16.00 implemented AMD FSR SDK 2.3.0, added FSR Upscaling 4.1 support for Radeon RX 7000-series GPUs and updated Ray Regeneration to 1.2.0.
Tuning ladder
Section titled “Tuning ladder”- Start from a stable preset.
- Set the intended output resolution and refresh rate.
- Choose one upscaler and disable competing reconstruction options.
- Test without frame generation to establish real render performance.
- Reduce the settings with the greatest visible scene cost.
- Retest the same route for several minutes.
- Enable frame generation only after base frame pacing is stable.
- Add HDR and advanced ray features one at a time.
- Keep the final settings only if a save-and-reload test remains stable.
Stutter diagnosis
Section titled “Stutter diagnosis”- repeat the same route to separate shader or asset warm-up from persistent stutter;
- close overlays and capture tools one at a time;
- confirm the game is on the intended GPU;
- check temperature and clock behaviour without changing overclock settings;
- compare frame pacing before comparing average frame rate;
- test a capped frame rate below the unstable peak;
- record whether the fault begins after a menu, cutscene, fast travel or character switch.
Crash diagnosis
Section titled “Crash diagnosis”- Preserve saves.
- Return CPU, GPU and memory tuning to known-good settings.
- Verify game files through the installed launcher.
- Record the current driver before changing it.
- test with overlays disabled;
- test the exact failing action once;
- collect the crash time, location and action;
- check Patch 1.16 notes and Current Known Issues;
- submit a reproducible report if the fault remains.
Do not delete saves or configuration folders as a first response.
Image-quality diagnosis
Section titled “Image-quality diagnosis”For blur, ghosting, flicker or unstable edges:
- compare native output with one upscaler;
- disable frame generation temporarily;
- test depth of field, motion blur and sharpening separately;
- confirm dynamic resolution is not changing the test;
- verify the display is using the intended resolution and HDR mode;
- capture the same frame with settings and patch recorded.