On this page
COMMUNITY PC GUIDE

Uncharted PC Troubleshooting

Updated · Checked against SuperMedo Windows v0.3.6, spacepepperoni Linux v0.3.6-linux.81

Match your symptom below, then follow its section. Use SuperMedo Windows v0.3.6 or spacepepperoni Linux v0.3.6-linux.81 before comparing an older error with the current fixes. Close the game before updating or changing its input and graphics settings.

Keep the project version, game number, title ID and game revision with your notes. Those details matter for region-specific fixes and for separating Windows problems from the Linux fork's remaining limits. Preserve the last-run log before launching again if you need to report a crash.

Match the symptom

Symptom Applies to First action
SymptomA game is missing or the launcher asks for its folder Applies toWindows / Linux First actionCheck the selected folder and exact executable name
SymptomThe Linux AppImage will not open Applies toLinux AppImage First actionEnable executable permission
SymptomIllegal instruction or an unsupported CPU message Applies toWindows First actionCheck the CPU generation and program version
SymptomUncharted 2 crashes at the train wreck Applies toWindows First actionMatch the assertion and game revision
SymptomReadSync or iSubMesh loading crash Applies toWindows First actionUse v0.3.6, which includes the v0.3.5 file-read fix
SymptomUncharted 3 crashes at the London bar Applies toWindows First actionUse the current program with the bar-crash fix
SymptomUncharted 3 keeps crashing on Linux Applies toLinux First actionCheck the current work-in-progress limitation
SymptomBlack screen on Intel graphics Applies toWindows Intel HD / UHD First actionIdentify the GPU model and driver
Symptomm_gfxEopTick after a cutscene Applies toWindows First actionCheck the game revision and current frame-reuse fix
SymptomDevice lost in Uncharted 3 Cartagena Applies toWindows First actionSet Display → Frame rate to 60
SymptomBlack squares or blue and white textures Applies toWindows First actionCheck the current graphics fixes
SymptomOne-frame green or black character shapes Applies toWindows Uncharted 3 First actionIdentify the remaining shader problem
SymptomThe game crashes on a 4 GB graphics card Applies toWindows / Linux First actionTurn AA and frame generation off
SymptomWeapons turn black after changing GPU readbacks Applies toLinux First actionRestore Default (relaxed)
SymptomExisting saves are missing Applies toWindows / Linux First actionCheck the chosen saves location
SymptomThe first minutes stutter after updating Applies toWindows v0.3.6 First actionAllow the one-time shader rebuild
SymptomThe frame rate is low or uneven Applies toWindows / Linux / Steam Deck First actionCheck the selected target and active graphics settings
SymptomYou need to send a crash report Applies toWindows / Linux First actionPreserve the last-run log and reproduction steps

Startup

A game is missing or the launcher asks for its folder

The selected folder must contain the corresponding executable directly. Check these names in your existing prepared copy:

Game Collection executable
GameUncharted 1 Collection executableeboot.bin
GameUncharted 2 Collection executablebig2-ps4_Shipping.elf
GameUncharted 3 Collection executablebig3-ps4_Shipping.elf

Open Game → Game folder on Windows, or Files → Game folder on Linux, and select that collection directory. If you selected its parent, the files will be one folder below the location the launcher checks.

On Windows, also inspect Separate game folders if you have used it. A per-game path overrides the shared collection path. Select the correct prepared directory for that game, or return to the shared collection setup. The game-file checklist explains the supported executable layout.

On Linux, check CUSA02320 v1.00 before trying to launch. After correcting the path, return to Library and check the individual game's availability. If it becomes available but then crashes, follow the matching crash section rather than continuing to change directories.

The Linux AppImage will not open

  1. Right-click Uncharted-x86_64.AppImage in the file manager.
  2. Open Properties → Permissions.
  3. Enable Is executable or Allow executing file as program.
  4. Open the AppImage again.

Also check the system condition: 64-bit x86 Linux with glibc 2.41 or newer. SteamOS 3.7+, Debian 13, Ubuntu 25.04, Fedora 42 and Arch are listed examples. If permission is already enabled and the launcher still fails, include the distribution, glibc version and exact error in a report to the Linux project.

Illegal instruction or an unsupported CPU message

For Windows v0.3.6, use Intel Core 4th generation / Haswell or newer, AMD Ryzen, or AMD FX. Intel Core 3rd generation and older still cannot run these games in the selected version.

AMD FX support was added in v0.3.6 by handling its missing MOVBE instruction. If an FX system is still running an older package, update the program first. If it fails on the current version, retain the exact CPU model, error text and log for a report.

Older program versions can stop with 0xc000001d; later versions identify missing instructions. Use the message to check the CPU before changing display settings.

Uncharted 2 crashes at the train wreck

Read the exact assertion. IsFinite(deltaTransform) in character-leg-ik.cpp has a fix in Windows v0.3.6 for EU v1.00. Use the current program and retry that sequence with that revision.

If the same assertion appears on another revision, keep the title ID and application version with the log. That revision is important for extending the fix. If the error instead mentions ReadSync or iSubMesh, use the next section: it concerns incomplete file reads rather than this animation assertion.

ReadSync or iSubMesh loading crash

Windows v0.3.5 fixed reads that could return only part of a game file. The fix is included in v0.3.6. Symptoms include ReadSync file (req/read: ...), or white textures followed by iSubMesh < m_numSubMeshInstances.

Update an older program to the current Windows release, then retry the same sequence. If it recurs on v0.3.6, record the full error and where loading stopped. Include the log and your game revision in the report. Preserve the existing game directory while checking the program version and error.

Uncharted 3 crashes at the London bar

Windows v0.3.4 fixed the London bar crash associated with 0xd9c59b or device lost during the bar fight. The fix is included in v0.3.6.

If you are using an older Windows program, update it and retry the same scene. If the bar still crashes on v0.3.6, record the exact scene, error and game revision, then preserve its log. For a Linux crash, use the Linux limitation below so the report goes to the correct project.

Uncharted 3 keeps crashing on Linux

Uncharted 3 crashes frequently and is not yet fully playable in the selected Linux release. Keep that limit in mind if you are choosing a game for a new Linux installation. Uncharted 2 also has physics glitches; Uncharted 1 reaches gameplay and seems stable.

For a repeatable Uncharted 3 crash, record the chapter, action and current Linux settings, then report it with the Linux log. A current Linux release and valid game directory are the starting conditions. The Windows-specific bar and animation fixes above have their own scope.

Graphics

Black screen on Intel graphics

Windows v0.3.3 fixed the Intel HD 630 black screen by disabling a Vulkan feature on Intel. Use v0.3.6, which includes that fix, and a current graphics driver.

Identify the exact Intel GPU before following another model's result. Older HD 520 hardware can still crash inside the Intel driver. If the current program remains black, preserve the log and include the GPU model, driver version, game and selected display options.

If the window closes with a CPU-instruction message, follow the CPU section. If it stops with m_gfxEopTick, use the next section so the error and its game-revision condition stay together.

m_gfxEopTick after a cutscene

The assertion includes GetRenderFrameParams(frameToFreeInstancesFor)->m_gfxEopTick. It often appeared after the first Uncharted 1 cutscene while the graphics side was still busy preparing shaders.

The Windows frame-reuse fix starts in v0.3.2 and was extended in v0.3.4 to US CUSA02320 v1.02 and EU CUSA02344 v1.02. The current v0.3.6 includes those changes. Update an older program before changing the prepared game data.

If it recurs, include your title ID, game revision and log. Mention whether the cutscene played normally or was skipped, and where the assertion appeared. Keep the full assertion text so it can be distinguished from another cutscene crash.

Device lost in Uncharted 3 Cartagena

For a recurring “GPU crash: the graphics device was lost” in Cartagena square, chapter 2, open Windows Display → Frame rate and select 60 FPS, then start the game again.

The original area-specific fix is included in the current program. If the symptom persists at 60 FPS, preserve last_run.log and report the chapter, game revision, GPU and driver. Keep the selected frame rate with that report, especially if the previous setup used an experimental higher rate.

Black squares or blue and white textures

Windows v0.3.6 fixes black blocks in Uncharted 2, including snowy skies and rocks. The current program also includes the v0.3.4 change for blue or white textures that remained until they were reloaded.

Start by checking the program version. If an older installation shows those symptoms, update and retry the same scene. If the picture is still broken after the update, use Advanced → Clear shader cache on Windows or Files → Clear shader cache on Linux, then start again. Shader rebuilding can add stutter on that next start.

If the problem continues, report the affected surface, chapter and current AA, upscaling and GPU settings with the log. For a one-frame flash on a character, use the next section rather than treating it as a persistent texture problem.

One-frame green or black character shapes

Uncharted 3 can show green or black shapes on a character for a single frame, including Sully's shirt in Cartagena. This remains a known shader-translation problem in Windows v0.3.6.

Keep the location and character name with a report if you encounter it. If the game also stops, preserve the crash log and distinguish the brief visual flash from the error that closed the game. Use the relevant device-lost or startup section for that separate failure.

The game crashes on a 4 GB graphics card

The listed graphics requirement is 6 GB or more of video memory. Cards with 4 GB, including GTX 1650 and RX 570 examples, can exhaust video memory after playing for a while.

Turn Anti-aliasing and Frame generation off in Windows Display or Linux Settings, then start the game again. If it continues to close, record how long it ran, the scene and the current settings with the GPU model. Keep the last-run log for the maintainer.

Weapons turn black after changing GPU readbacks

On Linux, open Advanced → GPU readbacks and restore Default (relaxed). The experimental Off option can reduce floating NPCs for some cases but can also turn weapons into black cubes. Precise is the slower alternative.

Restart the game after restoring the default and check the same scene. If the visual problem remains, include the active readback mode in the report so it is clear which setting produced the picture.

Saves

Existing saves are missing

Check the selected saves directory before moving or deleting anything. A newly selected folder can make an existing save appear absent because the game is looking in a different location.

Project Default saves / log location
ProjectWindows v0.3.6 Default saves / log locationuser\ beside Uncharted.exe; user\last_run.log
ProjectLinux v0.3.6-linux.81 Default saves / log location<game folder>/Saves; last_run.log in that selected saves folder
  1. Open Windows Game → Saves folder, or Linux Files → Saves folder.
  2. Check the configured path against the location used by your earlier installation.
  3. Back up the existing saves directory.
  4. Select the intended existing saves directory in the launcher.
  5. Start the same game and check its save list.

Linux organizes saves under per-game Uncharted 1, Uncharted 2 and Uncharted 3 folders. Use the Files page's per-game entries to inspect them. Check both the parent saves directory and the chosen game when comparing installations.

Windows launcher options are stored in %APPDATA%\uncharted-launcher\settings.json. Linux uses $XDG_CONFIG_HOME/uncharted-launcher/settings.json, or ~/.config/uncharted-launcher/settings.json when that variable is unset. These are launcher settings; keep them separate from the game's saves directory when making a backup.

If the folder is correct and loading still fails, preserve the existing files and describe the save's origin, selected game and error in a report. Include whether it started after a program update or a change of saves path.

Performance

The first minutes stutter after updating

Windows v0.3.6 rebuilds the shader cache once. The first minutes of each game can stutter more than usual while it fills again. Allow that initial rebuild before comparing the same section's behavior on a later run.

Keep the shader cache between ordinary launches. Clearing it starts that work again, so use cache clearing for the specific broken-picture case above. Record whether a performance report comes from the first run after updating or from a later run of the same scene.

The frame rate is low or uneven

Check Frame rate, Presentation, Anti-aliasing and Frame generation in Windows Display or Linux Settings. Begin with a 60 FPS target and record the active settings before changing one of them.

Windows offers 60 and 120 FPS, with 144, 165 and 240 marked experimental. If a problem started after selecting one of the experimental rates, return to 60 and check the same sequence. For the specific Uncharted 3 Cartagena crash, use its section above.

On Steam Deck, keep Steam Deck mode enabled while checking its initial setup. The current formal release targets 60 FPS and also permits 30 FPS. Choosing 30 lowers the target while keeping the mode's other settings. Use the current release's 60/30 target choices in the launcher.

The game's internal rendering remains 1920×1080 while the output window is scaled. Use the display tables to distinguish output size, AA and frame generation before choosing an adjustment. Include the scene, GPU, target and AA/FG choices when reporting continued uneven performance.

Report a problem

Prepare a useful crash report

Use the project you are actually running: SuperMedo Windows issues or spacepepperoni Linux issues. Preserve the failing run's log before starting another game.

Include What to record
IncludeProgram What to recordMaintainer and exact port tag
IncludeGame What to recordUncharted 1, 2 or 3; title ID and game revision
IncludeSystem What to recordWindows version or Linux distribution; CPU, GPU and driver
IncludeReproduction What to recordChapter, location, action and exact error
IncludeSettings What to recordFrame rate, presentation, AA, FG; Deck mode and GPU readbacks if applicable
IncludeLog What to recordlast_run.log from the selected saves directory
IncludeRecent change What to recordProgram update, game-directory change, saves-path change or setting adjustment

Open Log on Windows or Advanced → Show the log on Linux. Windows saves the latest output to the selected saves directory. Linux also rotates earlier logs through last_run.4.log; choose the file corresponding to the failure you are reporting.

Write the shortest sequence that reproduces the problem, then include the full error and matching log. Check the log for personal filesystem paths before sharing it. Keep game files out of the report. If you are reporting input, include the device model and affected binding as explained in Controls.

Sources

Back to top