What the source did
- The 2023 Dead Space remake hitched badly at boundary transitions, where the game loads the next area. In his description the image froze for 250+ ms.
- He has mild programming experience and had used AI to make a couple of mods for other games before.
- The game is closed, with no source code, so Claude reverse engineered the executable.
- He says the game was about 80% fixed on day one. In a comment he calls that conservative and says "we could call it 95%".
- To make measurements meaningful he needed identical input each test. Claude built a program that records his input and steers the character back on course, hooked into the camera's x, y and z values. A deterministic run starts the game and crosses a boundary while panning the camera the same way every time.
- A crash turned up in an area he had never recorded a route for. Claude loaded a save there, used screenshots to find the spot, reproduced the crash every time and fixed it.
- The root cause was handled by allocating large blocks of VRAM up front and serving requests from them about 20x faster. He focused on fixes that generalise across the game.
- He measured average stutter over 20 boundary traversals across vanilla, another fix mod and his builds. He says it's a single location on a single PC.
- He lets Claude run tests unattended while he's at work or sleeping. He doesn't read the code syntax himself.
- Reflex is off by default because it makes stutter worse, and it can be enabled in config. Claude didn't want to touch anything near the DRM layer, and nothing needed changing there.
- The mod was featured by Wccftech and Digital Foundry. Digital Foundry updated its article to reflect the AI use, and its piece also had a short spot in a video.
- It's not a commercial product. It's a targeted reverse-engineering fix, and the repo has been public since day one. No official Linux or Steam Deck support, with mixed reports.
“a single location on a single PC (mine), so take it with a grain of salt”— u/lukeman3000 (r/ClaudeAI), Reddit
Summary written by Agent Cookbook from the original post. See the original for the full context. How we source recipes
Our notes
- What it takes
- Claude Code on the PC where you run the game, your own recorded input through each boundary, and saves that reach the areas you want to test. The game is closed with no source, so Claude reverse engineered the executable. Optional: his Ishimura Patch repo, under his own licence.
- Where it breaks
- Results come from one location on one PC. Mods can break with game updates. Reflex makes stutter worse, so it's off by default. There's no official Linux or Steam Deck support. Reverse engineering a game binary is on you, including the game's terms.
- Human checkpoint
- You decide what ships. Publishing or uploading the mod, and any release, are yours. Claude runs tests unattended but doesn't publish.
- Tools involved
- Claude Code, on the PC where you run the game, The 2023 Dead Space remake on PC. There is no official Linux or Steam Deck support, per mixed reports, Your own recorded input through each boundary you want to test, Saves that reach the areas you want to test, so Claude can reproduce a crash, Optional: his Ishimura Patch repo, for the code and build.bat, under his own licence, You, deciding what the test should be and what ships
✓ Verified Source link checked and still live. Notes by Thomas, editor. How we verify
Get their template
Made and published by u/lukeman3000. Start here; it is their original, not ours.
Our adapted version
Ours Our version, based on u/lukeman3000's post and comments. He didn't publish a prompt; this uses only the steps he described. Fill in the [BRACKETS].
Approval rule
Set it up
- Decide what the test should be: which transition you're measuring, and what a pass looks like.
- Record your input running through that transition. Have Claude clean the recording so the camera pan runs at a consistent speed.
- Have Claude build a program that replays the input and steers the character back on course, hooked into the camera's x, y and z values. Every run starts and crosses the boundary the same way.
- Confirm the stutter falls inside the camera pan. Have Claude validate each test: the character where expected, the camera panned correctly.
- Tell Claude to run a test. It launches the program, waits, sometimes edits the program for a new area, then analyses the data and draws conclusions.
- For a new crash, have Claude load a save near it, use screenshots to find the spot, and reproduce it.
- Let the tests run unattended, then compare the average stutter across builds over the same 20 traversals.
Common failures
- Measuring without identical input. Without the recorded route and the camera cleanup, runs can't be compared.
- Generalising from one place. His numbers come from a single location on a single PC.
- Turning Reflex on. It's off by default because he found it makes stutter worse.
- Expecting Linux or Steam Deck support. There is none official, and reports are mixed.
Variations
- Each new area can need its own recorded route. He had Claude edit the test program to add one.
Related setups: Claude Code rebuilt Apple Photos for his Immich server → · Claude Code rebuilt his treadmill screen → · Old Kindle turned into a weather dashboard by Claude Code → · Claude Code fault-test loop found 55 Ceph bugs →
Get the 10 best agent setups. Free.
Plus new recipes every week. One email, no spam.
Unsubscribe anytime. Privacy