Startup recovery / Save-safe order
Low-Budget Repairs Won't Start
Troubleshoot Low-Budget Repairs startup, black or gray loading screens and shader-cache failures without deleting saves first.
The short version
First identify the exact failure point: a slow first shader compile, a compile with no progress, a grey or black screen afterward, an immediate process exit, and a failure limited to one save are different cases. Start with file verification and a save backup; do not delete LocalLow.
Last verified:
Latest official startup status
Update 5 improved some apartment or home transition crashes, FPS stability and shader compilation failures that prevented launch. Update 6 separately fixed infinite loading when traveling to prison. A black screen, a shader stall and a particular save failing to load are different symptoms.
Use this safe order
- Wait several minutes on the first shader compile and note whether Windows reports Not Responding.
- Quit normally, restart Steam and finish every queued update.
- Verify the integrity of installed files in Steam Properties.
- Disable third-party overlays, injectors and recording hooks for one test.
- Update the GPU driver and restart Windows.
- Try the game once with a new launch log, then report the exact stage where it stops.
Back up LocalLow before any reset
The official Discord troubleshooting conversation identifies %USERPROFILE%\AppData\LocalLow\gray2rgb as local game data and explicitly notes that saves are inside it. Copy the whole gray2rgb folder to a separate safe location before changing individual files. Do not delete the folder as a first step.
First launch or shader compile
A black, gray or apparently frozen first run can be a shader-compilation failure or a slow compile. Record elapsed time, GPU model and whether audio or the loading indicator changes. A community suggestion to force 640×480 is diagnostic only, not a confirmed permanent fix.
Loads fail only on one save
- Duplicate the backup before testing.
- Open Load Game and compare timestamps.
- Try the newest plausible autosave once.
- Try an older known-good manual slot.
- If a new game loads but one save does not, report the save-specific failure without overwriting it.
Include this in a startup report
- CPU, GPU, RAM and Windows version
- Steam build and whether file verification changed anything
- First launch or previously working install
- Exact last visible screen
- Time waited
- Player.log and backed-up save only when support requests them
Status after version 1.0.15
The 1.0.15 changelog lists interaction and localization fixes but does not claim a dedicated shader-compilation crash fix. Recent reports still cover a stalled compile and a grey screen after it, so use the save-safe order above and preserve Player.log.
Match the steps to the symptom
- Progress still moves — allow more time for the first compile and watch CPU or disk activity.
- Progress has stopped — record the time and stage, and preserve Player.log before retrying.
- Grey or black screen after compile — treat it as a separate stage; reinstalling did not help one recent report.
- Menu works but one save does not — do not delete all data; preserve the slot and report a save-loading failure.
Separate intro-cutscene softlock variant
The official August 13 hotfix fixed a specific post-intro house softlock. A separate post-1.0.15 report describes fast dialogue, an unexpected teleport into the building and the next cutscene failing to fire, leaving the character unable to move. This is a new community report, not proof that the official fix was reversed.
Update 4 fixes apartment-entry crash; shader reports remain
The official changelog fixes a crash while entering the apartment. It does not name shader compilation, and that thread received confirmations after the update, so diagnose the two symptoms separately.
Source log
Where this answer comes from
- official sourceSteam — Low-Budget RepairsOfficial Steam listing for the current Windows release and developer details.
- developer sourceDeveloper update — August 14Official August 14 post-launch update describing fixes and work still in progress.
- community sourceSteam Community — DiscussionsCurrent player questions and reports; a post is not treated as developer confirmation.
- community sourceOfficial Low-Budget Repairs DiscordCommunity screenshots and troubleshooting messages from the official Discord, reviewed editorially on August 16.
- official sourceOfficial Update 3 — changelog 1.0.15Official August 18 changelog covering object interactions, Mounting, tiles, heavy objects, unintended breakage and localization fixes.
- community sourceSteam Discussions — shader compilation does not finishRecent thread with multiple confirmations that shader compilation can stop progressing.
- community sourceSteam Bug Reports — grey screen after shader compilationPlayer report of an endless grey screen after compilation; file verification and reinstall reportedly did not resolve that case.
- community sourceSteam Bug Reports — intro cutscene progression softlockSingle detailed post-1.0.15 report of fast dialogue, an unexpected teleport and the next cutscene failing to trigger.
- community sourceSteam Bug Reports — shader compilation crashPlayer report of a shader-compilation crash; it is not a confirmed cause of every startup failure.
- official sourceOfficial Update 4 — August 27 changelogOfficial Update 4 notes covering save and objective-state improvements, hanging-object placement, mission changes, crash and progression fixes, collectibles, tiles, optimization and localization. The announcement does not publish a numeric version.
- official sourceSteam — Update 5September 7 engine, launch and performance changes.
Found a stronger source or an outdated fact? Send Andrew a correction.