Our Python sandbox installed repository dependencies in 6 seconds and completed its recorded build step, but its test command failed. Use uncharted_pc if you own a decrypted PS4 collection dump and accept working through community fixes. Skip it if you want to finish the trilogy without managing builds, saves and chapter-specific faults. The Windows gameplay reports below come from named players and supplied sources.
uncharted_pc brings Drake's Fortune, Among Thieves and Drake's Deception to Windows. The original PS4 game code runs directly on your PC and the graphics are translated to Vulkan. No game files are included. You provide your own decrypted collection dump. SuperMedo's README describes this execution model and the required files. These are the original trilogy games, separate from the official Legacy of Thieves Collection containing Uncharted 4 and The Lost Legacy.
What people use uncharted_pc for
MrBboy95 reported finishing Uncharted 2 after switching to community builds that repaired its chapter 21 truck encounter. Their issue #415 report connects a specific obstruction to a useful outcome: the large truck took damage, aiming blur improved and Xbox prompts appeared. The same thread later records freezes after another update. Choosing a build therefore involves the game and chapter you need to get through, rather than simply selecting the newest download.
| Who used it | What they tried | What they reported |
|---|---|---|
| MrBboy95 on GitHub | Community build community-20261021-0940 for Uncharted 2 | The grenade-launcher section and aiming blur improved, Xbox prompts worked, and they later finished the game. Issue #415 |
| George22x on GitHub | Successive Drake's Fortune builds with an i5-10400 and RTX 4070 | Stable 60 FPS without frame generation in the section tested on a later community build. Issue #493 |
| mohit120nlk-ux on GitHub | All three games on a GTX 1650 laptop after startup troubleshooting | All three games launched, but the reporter lacked stable 30 or 60 FPS and reported cutscenes at 12 to 14 FPS. Issue #636 |
| An unnamed player, reported secondhand by TechPowerUp | Drake's Fortune on an RTX 4060 laptop at 1080p with DLAA | A completed playthrough, mostly 100 to 120 FPS, with a chapter 11 crash that corrupted a save. TechPowerUp report |
Different_Chicken748's Reddit question about Xbox prompts describes another use case: the port worked, but PlayStation prompts made an Xbox-layout controller difficult to follow. MrBboy95's separate GitHub report confirms Xbox prompts working after a community-build change. The two reports connect a controller problem with a successful outcome on a named build, making input behavior another reason to compare releases before changing settings or seeking a separate mod.
What happened when we ran it
Our November 15, 2026 run used commit 4fd77bf, installed repository dependencies in 6 seconds and failed its test command after 4 seconds. The harness recorded a successful build step lasting 1 second. Its configuration listed 3 CPUs, 8 GB RAM and image label ghcr.io/astral-sh/uv:python3.12-bookworm. These are our measurements of the repository harness; the Windows release instructions describe a separate setup path.
| Recorded check | Result | What to take from it |
|---|---|---|
| Dependency installation | Succeeded in 6 seconds; 35 dependencies, 38 MB on disk | Repository dependencies installed successfully. |
| Build step | Succeeded in 1 second | The harness reported success for its selected build step. |
| Test command | Exit 1 after 4 seconds | The suite did not pass. |
| Pytest log tail | 13 failed, 117 passed, 33 skipped, 1 error, 27 subtests passed in 2.36s | The log reports main results and subtests separately. |
| Dependency audit | pip-audit: 0 known vulnerabilities | The recorded dependency advisory check returned zero findings. |
| Repository scan | Tests directory present; 0 CI workflow files; no Dockerfile | These are observations from the measured checkout. |
The visible failures include LauncherTranslationTests::test_each_translation_covers_every_launcher_text. German, Italian and Japanese subtests list missing strings: "Test vibration" and "Connected · Vibration test failed". The harness summary describes "1 collection/setup errors of 131", while the tail separately lists skipped tests and subtests. We retain those reported counts without calculating a passing percentage from totals that use different groupings.
The scanner classified the harness ecosystem as Python, while the supplied GitHub repository API identifies C++ as the project's primary language. The measured checkout contained 2,430 files, approximately 1,146,241 source lines and occupied 108.7 MB. The labels describe different scopes: Python repository checks and the native port's implementation. The recorded build success belongs to the harness step at this checkout.
A missing Compose file stopped the separate deployment check
The separate November 15 hands-on safety step failed because its runner required a Compose file and found none. Its failed safety record names all four paths checked: compose.yaml, compose.yml, docker-compose.yaml and docker-compose.yml. The repository's documented Windows setup instead starts with an unpacked release and a decrypted game folder, so the runner's admission requirement explains the recorded stopping point.
The hands-on summary says deployment used its own Docker Compose stack with every port bound to 127.0.0.1. The failed safety step records the opposite deployment outcome, so we classify the attempt as blocked and retain both records. The separate teardown record reports "ok". Its cleanup outcome is distinct from the failed admission step.
Where people get stuck: progression fixes can trade one fault for another
Issue #415 records a chapter 21 repair followed by an update regression for the same Uncharted 2 player. MrBboy95 confirmed the community build fixed the grenade-launcher section, aiming blur and Xbox prompts. A later build fixed black weapons but introduced freezes after about 10 minutes of gameplay; reverting stopped them. The contributor then proposed disabling the small-buffer readback change to investigate. The issue thread preserves that sequence.
| Symptom | What players or contributors tried | Outcome in the thread |
|---|---|---|
| Uncharted 2 characters sink or float | BB_GUEST_MXCSR=9fc0, or BB_READBACKS=0 |
One test had fewer floating NPCs, with some remaining. Another workaround produced black weapon cubes. Issue #33 |
| Uncharted 3 characters fall through floors | Updated builds | Magister1235 reported improvement; kolok73 later reproduced the chapter 14 fall-and-death loop. Issue #727 |
| Uncharted 3 black weapons, blurry aim and missing geometry | Aim and brightness fixes; readback changes | The contributor reported no frame-rate cost for the aim fix, but 72 to 45 FPS for the brightness fix in Cartagena. Later reports included missing objects, textures and graphical glitches in Yemen. Issue #601 |
| Uncharted 1 grenade launcher kills Drake | Aiming higher, direct hits, or the suggested health cheat | brruunnoo got through the jet-ski section with direct hits on barrels or enemies. Issue #699 |
Disabling readbacks produced black weapons in issue #33, while the brightness fix reduced Cartagena performance from 72 to 45 FPS in issue #601. A setting that gets a player through one obstruction can therefore change another part of the experience. Keep an unchanged save and record each setting you alter, so a later failure can be compared with a known starting point instead of several simultaneous changes.
Issue-based crash fixes can contain malicious commands
Issue #220 warns about fake fixes that download and execute a remote script with administrator privileges. The warning's author inspected the posted command without executing it. driftywinds separately reported resetting their PC after executing it, and later comments described further malicious posts. The warning thread explains why a familiar crash name or release number in an issue title is no assurance that its proposed command comes from the project.
The community README says fixes come through its releases and tells users not to run commands posted in issues. It also documents automatic save backups before launch, keeping the last 10. Community release and save documentation covers both obtaining fixes and retaining progress. The chapter 11 save corruption described in TechPowerUp's secondhand playthrough report gives the backup policy a concrete use beyond convenience.
uncharted_pc vs community, Mevlock, Linux and Legacy of Thieves
Mevlock's development fork requires a decrypted collection dump at version 1.02. That requirement belongs alongside its shader-preparation workflow when choosing between builds. Community releases have player-confirmed chapter and input improvements, while Pepin208 documents a Linux route with different supported dumps. Upstream remains the baseline Windows project, and its README credits contributions from several forks. The player discussions explain both why someone switched and why they later rolled back.
| Choice | Why consider it | What changes your decision |
|---|---|---|
| SuperMedo upstream | The baseline Windows project with versioned fixes | Match its requirements and release history to your game. Upstream README |
| Community build | Player-confirmed chapter 21, mouse and prompt improvements | #415 also records freezes after an update. Community documentation and player report |
| Mevlock development fork | Shader preparation before play and CPU-side translation changes | Requires a decrypted version 1.02 collection dump; its speed figures come from one RTX 5080 PC. Mevlock README |
| Pepin208 Linux fork | Native Linux runner and AppImage without Wine | It specifies glibc 2.39 or newer and EU CUSA02320 1.01 or US CUSA08034 1.00 dumps. Linux documentation |
| zorde23 port with Lossless Scaling | George22x used a 30 FPS baseline with generated frames | They reported smoother output with more input lag. Issue #493 |
| Official Legacy of Thieves Collection | Uncharted 4 and The Lost Legacy on PC | It contains different games from the trilogy reviewed here. Digital Foundry review |
Mevlock documents building each game's shaders before play rather than when an object first appears. Pepin208 reports testing the Linux fork on an AMD RX 6700 XT with Mesa RADV and KDE Plasma Wayland. These details make the alternatives useful for different setup decisions. The community record uses the hookmanuk repository address while describing drakolordx7's build; older issue links use the drakolordx7 address.
The supplied X release-card record identifies another variant: an OpenXR VR build for Drake's Fortune. Its card says Uncharted 2 and 3 are still not ready. That scope makes the VR release a distinct choice. A flat-screen trilogy report and a VR release announcement answer different questions, even when their repository names overlap, so the game named on the release matters as much as the project name.
What the other reviews get wrong
Hysen Labs excludes third-generation Intel Core processors, but upstream documents Ivy Bridge support from 0.3.7. The community README separately lists second-generation Sandy Bridge with AVX, SSE4.2 and POPCNT. CPU advice therefore needs the build name. Hysen's conclusion, upstream CPU history and community requirements describe different support boundaries rather than one universal processor requirement.
Hysen also presents flashing Uncharted 3 character shapes as an unresolved shader-translation problem. Upstream identifies the specific Sully-shirt defect in Cartagena as a cloth-solver race and records its fix in 0.3.9. Separately, Hysen's conclusion calls v0.3.6 the newest tag and October 17 the last push. The supplied latest-release API record identifies v0.3.15, published November 15, 2026; the repository API record records a push that day.
Hysen's categorical exclusion of 4 GB cards also misses the distinction between launching and acceptable performance. Community requirements allow 4 GB with frame generation off, while the GTX 1650 reporter launched all three games but reported poor frame rates. Similarly, the Reddit suggestion that Xbox prompts probably cannot change conflicts with upstream's feature list and MrBboy95's confirmation. These corrections replace blanket answers with the named build or reported outcome.
FAQ
Xbox prompts are supported in upstream's feature list, and MrBboy95 confirmed them working in a community build. Different_Chicken748 asked about changing PlayStation prompts to an Xbox layout in the supplied Reddit thread. The remaining questions concern startup, hardware, progression and input problems raised in the supplied synthesis and issue discussions. Their answers retain the game, build or hardware attached to each reported result.
Is uncharted_pc real, and how can I distinguish genuine releases from malicious crash fixes?
uncharted_pc is an unofficial trilogy port whose documentation requires your own decrypted PS4 collection dump. The community README directs users to releases for fixes and rejects commands posted in issues. Issue #220 describes fake fix posts that executed a remote script with administrator privileges. Use the named project's release history when choosing a download. Community README, malicious-post warning.
Can I change PlayStation button prompts to an Xbox layout?
Yes: upstream lists Xbox prompts, and MrBboy95 confirmed Xbox buttons after changing community builds. Different_Chicken748's Reddit question describes a working port with prompts that did not match their controller. The community-build report also confirmed improvements to aiming blur and the chapter 21 grenade-launcher section. Consult the chosen release's controls and features when comparing it with that report. Upstream features, player confirmation.
Why do all three games launch to a black screen?
Issue #636 describes startup stopping after XeSS loaded and before Vulkan started. Its troubleshooting included driver updates, closing overlays, disabling implicit Vulkan layers and XeSS, and trying the community build. Users subsequently reported games running. The GTX 1650 reporter then described unstable frame rates and cutscenes at 12 to 14 FPS, separating successful startup from the subsequent performance problem. Black-screen discussion.
Can uncharted_pc run acceptably on a GTX 1650 or another 4 GB GPU?
The GTX 1650 reporter launched all three games but still lacked stable 30 or 60 FPS, with cutscenes at 12 to 14 FPS. Upstream recommends at least 6 GB video memory and warns about memory exhaustion on 4 GB cards; community requirements allow 4 GB with frame generation off. Those documents give different minimum and recommended configurations. Player outcome, community requirements, upstream requirements.
Can Ivy Bridge or Sandy Bridge CPUs run it, and which fork supports them?
Upstream records Ivy Bridge support from 0.3.7 and excludes Sandy Bridge in its known-problem entry. The community README lists Sandy Bridge with AVX, SSE4.2 and POPCNT. Read the requirements for the specific fork you plan to use, because the shared project name conceals this difference. Upstream attributes Ivy Bridge support to rewriting instructions absent from those processors. Upstream history, community CPU requirements.
How do I fix characters sinking, floating, or falling through floors in Uncharted 2 and 3?
Issue #33 records fewer floating NPCs after a floating-point-state change, with some still floating, and black weapon cubes after a readback workaround. In #727 an update helped one reporter, while kolok73 later reproduced the chapter 14 respawn loop. Preserve a save from before the obstruction and record the chapter, dump and build when reporting it. Physics discussion, floor-falling report.
Why are weapons black and aiming blurry, and what performance do the fixes cost?
Issue #601 reports that the aim fix cost no frame rate in the contributor's tests, while the brightness fix changed Cartagena performance from 72 to 45 FPS. The discussion also connects disabled readbacks with missing geometry, and later reports describe further visual problems in Yemen. Change one setting at a time and retain its name alongside the result. Graphics-fix discussion.
How do I stop the grenade launcher from killing Drake during the jet-ski mission?
brruunnoo reported getting through the jet-ski section by hitting barrels or enemies directly and avoiding most other surfaces. Other supplied comments suggest aiming higher or using the health cheat. The same discussion describes explosions at Drake's feet when firing at many targets, explaining why players changed their aim or used the cheat to progress. Grenade-launcher discussion.
How do I fix gamepad-like mouse aiming in Uncharted 1?
JAVADOPERATOR reported much better mouse movement after switching to the community launcher. Its documentation describes raw mouse aiming that turns the aiming camera directly without a stick speed cap. The original issue describes difficulty aiming accurately with mouse movement that felt like gamepad input. Identify your launcher and release when comparing your aiming problem with that report. Mouse-input report, community documentation.
How do I get past the large truck in Uncharted 2 chapter 21?
MrBboy95 confirmed the grenade-launcher section worked after using community-20261021-0940. The supplied synthesis associates that release with fixes #382 and #381; the issue excerpt explicitly identifies #382 as enabled by default for Uncharted 2. The player also reported corrected blur and Xbox prompts. Keep the working release available because the same thread records freezes following another update. Chapter 21 report.
Can I use a 30 FPS baseline with frame generation to reach 60 FPS?
George22x reported smooth 60 FPS from a 30 FPS baseline with frame generation, alongside noticeable input lag. Their experiments included zorde23's version and Lossless Scaling. Later, the current community build held 60 FPS without frame generation in the section they tested. They reported an i5-10400 and RTX 4070 and were playing on a 60 Hz television. Frame-generation discussion.
Why does a powerful GPU still stutter below 60 FPS?
George22x's i5-10400 and RTX 4070 report describes CPU overload while struggling to hold 60 FPS. Successive community builds improved the tested section until it held 60 FPS without frame generation. The report attaches the symptom to both a processor and a build, alongside the graphics card. Include those details and the location when collecting a useful performance report. CPU-bottleneck discussion.
What we have not tested yet
Our run checked repository dependencies and harness tests at 4fd77bf; we did not build or play the Windows port. Graphics performance, controller vibration, save recovery, VR, multiplayer and complete trilogy playthroughs remain outside that run. The safety-blocked deployment attempt supplies no gameplay result, and its deployment summary conflicts with its failed step. The supplied v0.3.15 release is separate from the measured checkout.
The supplied tail leaves the other test failures and collection/setup error unexplained. Actual runtime and operating-system versions require raw toolchain logs; the configured image label does not establish them. Translation-coverage failures do not measure every language's launcher experience. The pip-audit finding covers the recorded dependency advisory check, rather than native-code security, release binaries or stranger-linked downloads. The supplied video excerpt does not identify its terminal command or connect it to #220's payload.
The supplied reports do not establish reliable complete playthroughs across all three games on current identified builds, universal grenade-launcher repair, recovery of the corrupted save, or complete removal of malicious issue posts. The proposed small-buffer readback diagnostic in #415 has no completed retest in the supplied discussion. The Sully-shirt fix concerns that named defect; other Uncharted 3 graphics and floor-falling reports remain separate findings.
Linux documentation names an RX 6700 XT desktop under Wayland; our run supplies no Intel, NVIDIA or Steam Deck compatibility result. Mevlock's shader preparation lacks an independent comparison across GPU vendors, and its speed claim comes from one PC. The RPCS3 video has no extract for comparison. A useful next run would replay the reported chapter blockers on named releases with the same saves and settings, preserving a rollback copy before each change.


