Spark198rus/black-pc has a player-confirmed Proton save fix, but our sandbox did not run the game. Use it if you own a supported Xbox copy of BLACK and are willing to troubleshoot a fan port. Skip it if you need a guaranteed campaign replay, native Mac software or faithful Xbox audio. The useful evidence here is unusually specific: players identify where progress stopped, and the maintainer explains which fixes address those failures.
What people use black-pc for
Players have reported saving successfully under Proton, completing the opening level on an old Intel laptop and reaching the bridge mission on an RTX card. Those accounts give you a better starting point than the README's broad playability claim. They describe different machines and different portions of the game, so read each outcome at its stated scope.
| Who used it | What they did | Reported outcome |
|---|---|---|
| Flaviano-Rodrigues | Played on Linux through Steam/Proton and tried the save fix | Reported that saving after the first mission and profiles worked after the fix. Issue #6 |
| An unnamed player in the project's TODO | Played on an i5-4300U laptop with Intel HD 4400 graphics | Completed the first level after an Intel vertex crash was fixed; the project recommends 30 FPS on that laptop. Project playtest notes |
| Mungr3ss | Played on an RTX 3070 Ti | Reported reaching the bridge mission without a crash. Issue #17 |
| aleksejsgx | Tested the port and requested PC usability improvements | Praised mouse menus, then said they would test sprint, checkpoints and cheats once a runnable release arrived. Issue #41 |
| LeanC90 | Played the third level on hard and swapped regional save folders | Reported a level-end pause crash and subsequently unrecognized saved progress. Issue #42 |
Flaviano-Rodrigues's account is the strongest reason to take the Proton path seriously. The original failure arrived after finishing the first mission, exactly when a player expects progress to become durable. Their follow-up reports a successful retest with the targeted fix. That is more useful than a launch screenshot: it addresses the operation that had prevented continuing the game.
What happened when we ran it
Our November 15, 2026 sandbox record marks commit c065917 as NOT RUN: our harness had no supported C++ ecosystem and found no Dockerfile. We did not run black-pc. The configured sandbox had 3 CPUs and 8 GB RAM, with no image recorded. That describes our harness coverage, not a minimum specification for playing BLACK.
| Lab item | Recorded result |
|---|---|
| Checkout | c065917, recorded November 15, 2026 |
| Configured resources | 3 CPUs, 8 GB RAM |
| Image | n/a |
| Execution decision | NOT RUN: no supported ecosystem, language C++; no Dockerfile |
| Installation, build and tests | No results in the controlling lab block |
The practical consequence is that setup ease stays unassessed. There is no gameplay result to turn into a frame-rate recommendation from our hardware, and no successful launch hidden behind the table. The supported player paths described below come from the project's documentation and attributed reports. Our lab's inability to select a recipe is not evidence that the Windows release fails to start.
Where people get stuck: saving and tunnel crashes need different fixes
The maintainer identifies v0.3.0 fixes for both Proton saving and a driver-sensitive vertex crash, while another notebook report was resolved by selecting its dedicated GPU. Treating every second-mission crash as the same defect sends players toward the wrong remedy.
| Symptom and source | What the record says | Useful next action |
|---|---|---|
| Save or autosave crashes, #6 | WildGer traced Wine/Proton's STATUS_NOT_IMPLEMENTED response to an event handle in NtQueryDirectoryFile; the maintainer names commit 1b253f1 and v0.3.0 as the fix | Use v0.3.0 or newer; the maintainer says the earlier DLL patch script is unnecessary |
| Repeatable tunnel crash, #29 | The maintainer says both supplied logs came from v0.2.0 and identifies a vertex-pointer error fixed in commit 98873cf | Try a current release and attach a fresh black.log if the tunnel still crashes |
| Notebook using integrated graphics, #17 | W4rL0ck1 confirmed the notebook selected integrated graphics instead of the dedicated card | Select the Nvidia GPU for black.exe in Windows graphics settings |
| Original game settings reset, #32 | Bluuwolfly supplied a log; the maintainer replied that it was fixed | v0.4.0 release notes specifically say SFX and music volumes are saved with the profile |
The save diagnosis deserves precision. WildGer reported that directories and files were created and profile data could be written. The failing operation was directory enumeration with a non-null event handle under Wine/Proton. Calling that a general Linux filesystem failure would obscure the actual finding. The maintainer's fix removes that event handle, and Flaviano-Rodrigues supplies the player retest.
The tunnel story is different. The Portuguese discussion in #29 includes attempts to reduce resolution, effects and frame rate without solving the crash. The maintainer attributes those logs to passing a pointer before the first-person weapon's vertices, which some drivers read outside memory. Separately, #17 contains a confirmed GPU-selection workaround. Similar locations on screen are insufficient grounds to combine the diagnoses.
Older Intel laptops should start at 30 FPS
The project's TODO recommends 30 FPS on its i5-4300U/HD 4400 laptop and records reduced game speed at 60 FPS. This is the project's observation, not our benchmark. The low Direct3D requirement makes black-pc worth investigating on an older Windows machine, but it says little about whether that machine can keep the game's simulation running at the higher setting.
The current README explains why: when the PC cannot keep up, the game slows down instead of skipping frames. That changes how you should judge a scene. A higher frame-rate setting is a poor trade if walking, combat and animation advance too slowly. Start with the original rate on that class of laptop and compare how the game actually moves, rather than assuming the default is appropriate for every GPU.
The same TODO records a successful first-level playthrough after an Intel immediate-mode vertex crash was fixed. That positive outcome belongs beside the lower frame-rate recommendation. It shows an older laptop doing useful work without turning one completed level into a promise about every mission. Laptop findings, current README.
Windows setup starts with your own supported game files
The current README requires your own NTSC-U or PAL Europe Xbox copy and places the extracted game folder beside the release's port folder. The release does not supply the game's executable or assets. For a player, matching the supported default.xbe hash matters more than having a source checkout full of development tools.
Keep game/default.xbe in the game directory and black.exe with blackrt.dll in port. The README's PowerShell hash check distinguishes the two supported builds from other releases whose code addresses differ. Do that check before interpreting an early launch failure as a graphics defect. PC_SETUP.md is explicitly a developer handoff; its analysis utilities are a different task from launching the downloadable player release. Setup evidence.
Linux has a longer documented route: the current README describes Distrobox, WineHQ Staging and DXVK. A player report through Steam/Proton is evidence for that player's route, not a reason to silently replace the documented instructions. Neither route needs a hosted AI service or an API credential in the published player instructions. Your game files and local compatibility stack are the relevant prerequisites.
black-pc vs BLACK XBE Recomp and xemu
black-pc runs the original Xbox x86 code directly, while TGP482's BLACK XBE Recomp compiles game code for the PC and exposes a broader graphics menu. The PortedGames comparison describes that distinction, and the current upstream READMEs support it. Choose by the hardware path and controls you need, rather than by the shared word BLACK in their names.
| Choice | Documented approach | When to consider it |
|---|---|---|
| Spark198rus/black-pc | Original x86 game code in a 32-bit Windows process, with replacement Xbox services and Direct3D 9 graphics | You want this port's integrated PC settings or are evaluating an older Direct3D 9 Windows GPU |
| TGP482/BLACK-XBERecomp | Native port using Xbox XBE Recomp; its README lists Direct3D 12 and graphics options including HDR output, ambient occlusion and weapon field of view | You want those explicit graphics controls and have suitable hardware |
| xemu | Emulates the original Xbox; the black-pc roadmap uses it as a reference | You want to investigate an Xbox emulation route, including on a Mac, rather than require this Windows port |
PortedGames comparison, BLACK XBE Recomp README, xemu's platform description.
The author's roadmap also explains the Xbox choice over a PS2-derived port: Xbox game code is x86, while the PS2 route would require CPU translation and graphics/runtime work for its GS and vector units. That is an architectural explanation, not evidence that every Xbox replacement service is accurate. Author's roadmap.
What the other reviews get wrong
PortedGames's v0.2.0 description is dated: black-pc's current release is v0.4.0, published November 14, 2026. Its NTSC-U-only restriction also conflicts with the current README and PC_SETUP.md, which list NTSC-U and PAL Europe. Those corrections materially change a player's decision about whether their disc and the reported fixes apply.
There is a second version trap inside otherwise helpful community evidence. In #41, aleksejsgx explicitly deferred testing several additions because they were on main without a runnable release. The later v0.4.0 notes now list mouse menus, sprint, cheats, checkpoint continuation and fast menus. The release notes settle delivery; they do not retroactively supply that user's missing retest. Feature discussion, v0.4.0 notes.
The README's fully playable description should also stay attached to its author. The project's TODO still lists audio work and pending playtests. Readers need those details to understand what playability means here. PortedGames itself says it did not compare the ports hands-on, so its graphics comparison should not be presented as a measured winner. Directory description, project TODO.
Security and maintenance: keep saves separate from downloads
The README says savedata holds the game's saved progress and settings, while black.ini holds port settings. Keep a backup of savedata before experimenting with regional files or changing releases. That is our practical recommendation given LeanC90's account of losing recognized progress after swapping folders, rather than a promise that copying a folder solves every recovery problem.
Use the official repository's release page and supply your own legally obtained game files. The project says its downloads contain no game code or data. A download bundled with BLACK's assets therefore has a different provenance from the release described here. Those boundaries are useful even for someone who never compiles a line of C++.
GitHub records a last push on November 14, 2026, and the sampled issue threads contain specific maintainer diagnoses and release references. That combination supports describing active work on this snapshot. An issue marked closed still needs its final replies read: #6 contains a fix and a positive retest, whereas #34 ends with a request to try the latest version and send logs. Closure alone is a poor substitute for an outcome.
Questions people ask
Spark198rus/black-pc runs BLACK's original Xbox executable directly in a 32-bit Windows process, replacing Xbox services with PC implementations. The loader documentation names the graphics, audio and input replacements. Loader description.
What is Spark198rus/black-pc, and how does it run the original Xbox game on Windows?
It loads your own default.xbe and runs the original x86 game code, with replacement kernel, graphics, sound and input services. The loader describes Direct3D 9, XAudio2 and XInput alongside keyboard and mouse support. It is an unofficial port, and the player supplies the game. Loader README.
How does black-pc differ from BLACK XBE Recomp?
black-pc executes the original x86 code directly; BLACK XBE Recomp uses TGP482's recompilation tool. Its README lists HDR output and ambient occlusion. It also provides a separate weapon field-of-view control. These are documented differences. Comparison source, Recomp README.
Why does black-pc crash when saving or enabling autosave after the first mission?
The Proton failure traced in #6 came from NtQueryDirectoryFile rejecting a non-null event handle, leading later to a crash. The maintainer says v0.3.0 fixed it in commit 1b253f1 and recommends that release or newer. Flaviano-Rodrigues reported successful saving after applying the fix. Save diagnosis and retest.
Why does black-pc crash in the tunnel on Treneska Border Crossing?
In #29, the maintainer identifies a v0.2.0 vertex-pointer defect fixed in v0.3.0. In #17, a different notebook report was resolved by selecting the dedicated GPU. Use the version, selected adapter and fresh log to distinguish those cases. Vertex crash, GPU selection.
Can black-pc run on Steam Deck, and is an AppImage available?
The #6 discussion includes a traced Steam Deck/Proton save crash and its v0.3.0 fix; Flaviano-Rodrigues specifically reports Linux through Steam/Proton. The AppImage request in #2 ended with the maintainer saying there was no Linux-branch maintainer. That request supplies no AppImage download. Proton evidence, packaging request.
Why is black-pc a 32-bit application rather than a 64-bit application?
The port's design runs the Xbox executable's existing x86 code in a 32-bit Windows process. The roadmap and loader description explain that choice more clearly than the brief reply in the AppImage thread. A 64-bit Windows host can run that process, as PC_SETUP.md states. Architecture, Windows setup.
Where can I find black-pc's logs when reporting a crash?
The current README asks for port/black.log on Linux or port\black.log on Windows. The loader documentation says the full log is black.log beside black.exe; it also describes alternate logging arguments for development launches. Attach the log from the failing run and include your release and operating system. Log location, reporting request.
Why does black-pc show a black screen with sound on Intel HD 4400?
Kishilikato reported that symptom in #34, and the maintainer requested a latest-version test and logs if it recurred. The thread supplies no diagnosis. It should not be assigned the cause from the separate tunnel or immediate-mode vertex reports merely because Intel graphics appears in both. Black-screen report.
Why do the original in-game settings, such as audio volume, reset on launch?
Bluuwolfly reported original game settings resetting in #32, explicitly distinguishing them from port settings. The maintainer marked the problem fixed, and v0.4.0 notes say SFX and music volumes now save with the profile. The player-facing distinction is savedata for game state versus black.ini for port options. Settings report, release fix.
Can I navigate menus with a mouse and speed up menu animations?
Yes: v0.4.0 release notes list mouse hover, click, sliders, wheel navigation and right-click back, plus fast menus. The current README puts the fast-menu option under PC SETTINGS > TWEAKS. The original request and appreciative response are in #41. Feature request, released controls.
Can I save mid-mission or resume from persistent checkpoints?
v0.4.0 documents CONTINUE LAST GAME, which resumes a mission from its last checkpoint after restarting. The current README says the entry disappears once the mission is completed or restarted. Describe that specific checkpoint behavior rather than promising arbitrary save-anywhere functionality. Checkpoint release notes, current README.
Does black-pc support sprinting or jumping?
v0.4.0 lists optional sprint on Left Shift, which stops while reloading or shooting. In #41, the requester welcomed sprint and explicitly said there was no hurry on jumping. That conversation supports a shipped sprint option and a request for jumping, without treating both as delivered. Gameplay request, sprint release notes.
What we have not tested yet
We have not played a campaign, reproduced the reported fixes, compared the ports on matching hardware or audited the executable's security. Our controlling lab result is NOT RUN. The community accounts support specific progress and fixes, but we have no independent full-campaign reliability result, picture comparison or measured advantage over BLACK XBE Recomp or xemu.
The supplied research pack also contains a conflicting apt attempt: its install step reports exit 100 and E: Unable to locate package winehq-staging, followed by an install-failed finding and successful teardown. Its run record describes a different sandbox configuration from the controlling lab block. We exclude that attempt's timings and configuration from our setup result pending reconciliation. The package lookup error alone proves neither a game defect nor its underlying package-source cause.
Save recovery is another open evidence gap. LeanC90's level-end pause crash and unrecognized restored folder end with a request to retest v0.3.0 and attach a log directly; no successful recovery follows. The Intel HD 4400 black-screen thread also lacks a successful retest. Those outcomes remain separate from the confirmed Proton save fix. Save and pause report, display report.
Audio fidelity needs a listening comparison. The TODO lists approximate reverb, unmixed effect bins, dropped subwoofer output and incomplete 3D sound behavior. The v0.4.0 notes themselves say real surround speakers and a Windows 8 PC were absent from the author's checks. Its remaining Xbox prompts, stretched widescreen videos and possible timing differences also deserve playtesting. A surround option in a menu does not settle those questions. Audio work, release boundaries.
Native Mac support remains a request in #23, where the maintainer expresses interest and asks about Intel versus Apple Silicon. There is no confirmed native Mac release in these records. Nor do the supplied X, YouTube or Bilibili results provide relevant black-pc player testimony: their PC-case and unrelated results add no corroboration. For a cautious first try, keep a copy of savedata and demonstrate a save, exit and reload on your own machine before committing an evening to the campaign. Mac request.

