Start with the publisher's pre-ticket checks
Naughty Dog asks players to verify game files, update drivers and ensure shader compilation is complete before a ticket. Its support article also notes background apps, internal SSD use, audio routing and controller details may matter for some PC issues; these are diagnostic branches, not guaranteed fixes.
| Symptom | Record first | Publisher check |
|---|---|---|
| Crash | Trigger, build, crash report and repeatability | Verify files and current drivers; use built-in crash reporter |
| Poor performance | Scene, settings, HUD CPU/GPU and shader state | Wait for shader compilation; update game/driver |
| Audio/controller issue | Output device, controller and connection | Check Windows Sound output; DualSense haptics require wired connection per FAQ |
| Save/loading error | Platform, save profile and exact message | Preserve the file and attach only if support requests it |
References: Naughty Dog: Submitting a technical support ticket · Naughty Dog: The Last of Us Part I PC FAQ
Attach only evidence that helps reproduce the issue
The publisher lists issue type, hardware, driver, RAM/storage, OS, game settings/version, location/activity, DxDiag, save data and log.txt among useful details. Its Windows save/log path includes the Steam or Epic ID subfolder, so files may expose local profile paths or account-related identifiers.
- Write a concise title and exact expected-versus-actual behavior, including the location/activity and last action.
- Record CPU, GPU, driver, RAM, storage type, Windows version, game build and graphics/audio settings.
- Verify the installation through the correct store and make sure shader compilation has completed if performance is involved.
- Use Naughty Dog's current instructions to collect the requested log/crash report/save; create DxDiag only if relevant to the case.
- Review filenames and file contents for local usernames, machine paths or unrelated personal information; redact where support permits.
- Submit through the publisher's official ticket route and keep the ticket reference; do not attach the entire Documents folder or post raw files in public discussions.
References: Naughty Dog: Submitting a technical support ticket · Naughty Dog: Why The Last of Us Part I shaders build again · The Last of Us Part I Steam Community Discussions
Before you play
- The exact issue and reproduction steps are written.
- Hardware/game/driver versions are recorded.
- Correct store and platform are stated.
- Only relevant files are attached through official support.
- Personal paths/identifiers are reviewed first.
Frequently asked questions
Can I post DxDiag publicly?
Prefer the official support ticket. Diagnostic files can contain identifying system details; review and redact where appropriate.
Does this page submit my ticket?
No. The worksheet is local to the browser and does not send files or contact Naughty Dog.
Do the PC paths apply to PlayStation?
No. They are PC diagnostics; use current console support for a PlayStation issue.
Sources & revision notes
Editorial revision: November 7, 2026; not a gameplay test date. The reference notes identify source limits and version differences.
- Naughty Dog: Submitting a technical support ticket (Official)
The publisher asks for issue type, CPU/GPU, driver, RAM/storage, OS, settings, game version, location/activity, reproduction detail and relevant diagnostic files. Logs and DxDiag may contain local identifiers; redact unrelated personal data before sharing.
- Naughty Dog: The Last of Us Part I PC FAQ (Official)
Naughty Dog's PC FAQ covers the shader cache, performance HUD and PC-specific settings. It is not a console troubleshooting guide; its instructions can change with patches.
- Naughty Dog: Why The Last of Us Part I shaders build again (Official)
Naughty Dog lists hardware changes, driver updates, reinstalling and Steam file verification as situations where shaders may rebuild. If rebuilding happens outside those cases, the article recommends a support ticket; this is dated PC guidance.
- The Last of Us Part I Steam Community Discussions (Community)
External user-generated PC/Steam discussions. Match the current build, hardware, driver and whether shaders completed; old launch reports may describe already-fixed issues.
November 7, 2026: first publication, reorganized the publisher's ticket fields with a privacy check. No diagnostic report was created.
How we research and correct guidesNo affiliate links or paid placement. Commercial disclosure.