Skip to content
Technical CentreKnown issues, diagnostics and performance
CurrentPatch 1.17.00

PlayStation 5 Setup & Troubleshooting

Save-safe PlayStation 5 and PS5 Pro setup, performance diagnosis and issue-reporting procedure.

Evidence
Official source
Verified
2026-08-08
Spoilers
No spoilers

This procedure covers PlayStation 5 and PlayStation 5 Pro without treating PC-only features as console settings.

Pearl Abyss officially lists:

  • FSR 3 for the base PlayStation 5;
  • upgraded PSSR for PlayStation 5 Pro;
  • no console frame-generation support.

Do not follow PC guides that require driver installation, DLSS, XeSS, PC frame generation or manual configuration-file editing.

  • install the current game update;
  • install the current PlayStation system software;
  • confirm sufficient console storage;
  • set the television or monitor to its intended game mode;
  • confirm HDR only when the display supports it correctly;
  • configure subtitles, minimum font size, camera and accessibility;
  • create a manual save before long sessions;
  • allow cloud synchronisation to finish before changing console or using Cross-Save.
  1. Record the exact action, location and error.
  2. Return to the title screen and reload a new manual save.
  3. Close the game completely and start it again.
  4. Restart the console.
  5. Confirm the game and system are updated.
  6. Reproduce the same action once.
  7. Check Current Known Issues.
  8. Report the patch, console model, display mode, save state and steps.

Do not delete local or cloud saves during diagnosis.

  • compare the available in-game modes without changing television processing at the same time;
  • use one fixed route for comparison;
  • record whether the issue appears in gameplay, menus, cutscenes or all three;
  • disable unsupported display features rather than forcing them;
  • retest HDR separately from the performance mode;
  • confirm the fault remains after a full game restart.

A smooth short scene does not prove every region or encounter will behave identically.

  • confirm the expected controller profile;
  • remove remapping temporarily only after recording it;
  • reconnect the controller through the console;
  • test one other game to distinguish device from game behaviour;
  • reload the affected save;
  • record the exact prompt and action that fails.

Patch history contains multiple control fixes. A repeated issue on the current verified patch should be reported as a current reproduction, not assumed to be the older resolved defect.

Before downloading, uploading or replacing a copy:

  • identify the newest save by timestamp and progress;
  • create a new manual slot;
  • wait for cloud synchronisation;
  • use the dedicated Cross-Save slot and in-game workflow;
  • verify the destination copy before continuing;
  • never overwrite both local and cloud copies during uncertainty.

Continue with Save, Cloud & Cross-Save Recovery.

Include:

  • PlayStation 5 or PlayStation 5 Pro;
  • current verified patch;
  • system software state;
  • display resolution, HDR and performance mode;
  • controller and remapping state;
  • quest, encounter, location or menu;
  • exact reproduction steps;
  • screenshot, video or error code;
  • whether a fresh game restart changed the result.