EA Motive's 2023 Dead Space remake has suffered from 250+ ms level-streaming hitches on PC since launch. Modder lukeman3000's Ishimura Patch (Nexus Mods, GitHub) tames those traversal stutters by intercepting Direct3D 12 memory calls at runtime, built over 100+ hours of directing Claude with an automated input-replay harness.
I haven't tested the patch on my own copy. This report draws on lukeman3000's r/ClaudeAI write-up, the ishimurapatch.cpp source comments, and benchmarks from Digital Foundry and Wccftech.
| Benchmark / Metric | Unmodified Dead Space (2023) | With Ishimura Patch |
|---|---|---|
| Wccftech 1% lows | 83.9 FPS | 157.6 FPS (+88%) |
| Wccftech 0.1% lows | 35.7 FPS | 98.6 FPS (+176%) |
| Digital Foundry worst spike (Ryzen 5 5600 + RTX 4070 Ti Super) | Over 120 ms | Under 25 ms |
| Creator 20-crossing average (single test boundary) | 374.33 ms | 16.71 ms (v0.3.13) / 1.20 ms (v0.4.0 preview) |
| Estimated AI token cost | N/A | \$2,300–\$2,500 across ~3 weeks |
Why Frostbite stuttered, and how the ASI avoids Denuvo
According to the engineering notes in ishimurapatch.cpp, an Event Tracing for Windows (ETW) capture at the game's lift boundary revealed why Dead Space (2023) freezes when crossing doorways. In a single 98.8 ms worst frame, the Frostbite engine made 447 separate CreateCommittedResource calls (4 MB or smaller) on one job thread. Direct3D 12 makes each resource resident at creation and blocks the thread on the kernel paging fence (PerNodePagingOperation::Wait), costing roughly 0.2 to 0.3 ms per request.
Because Dead Space.exe is wrapped in Denuvo (and lukeman3000 noted in the Reddit thread that Claude refused to touch anything near Denuvo), ishimurapatch.asi never patches the game executable. Instead, it uses MinHook to intercept d3d12.dll!D3D12CreateDevice, the D3D12 device vtable, and the kernel wait call. It suballocates small GPU resources as placed resources (CreatePlacedResource) inside a few large pre-allocated heaps, serving allocation requests roughly 20 times faster.

The unattended test harness that steers Isaac while you sleep
In the r/ClaudeAI thread, lukeman3000 explained that they have mild programming experience and no interest in reading C++ syntax by hand. To verify whether each code change helped without human movement variance, they had Claude build a deterministic test runner.
The harness hooks Isaac's x/y/z coordinates and camera angles, launches the game, walks across a streaming boundary while panning the camera at a constant speed, and logs PresentMon frame times. That let Claude run A/B experiments unattended while lukeman3000 was asleep or at work. When a crash cropped up in an unrecorded area of the ship, Claude loaded a save file, used screenshots to navigate to the room, reproduced the crash 100% of the time, and fixed it.
"I personally have no shame as it relates to my use of AI... I respect everyone's opinion and people are of course free to use or not use the mod for any reason - I just want the damn game to work." — u/lukeman3000 on r/ClaudeAI
After Nexus Mods introduced an AI disclosure requirement, lukeman3000 added the AI tag on Nexus and notified both Wccftech and Digital Foundry. Digital Foundry editor William Judd updated his November 3 feature to note that solo modders armed with an AI subscription are now shipping engine-level fixes that publishers leave behind.






