QUICK ANSWER

Troubleshoot ReStory airbrush paint stuck at 0%, missing color, wrong palettes, Freestyle painting, invisible strokes, and current player-reported bugs.

01

Quick fix order

Confirm that the current order actually includes a painting objective. Select the Airbrush tool, open the palette control, choose the color or palette named by the order, and verify that brush size and opacity are above zero. Rotate the device to a broad exposed face and test one short stroke. If the progress counter remains at 0%, undo once, save in a new slot, reload, restart the game, and retest before changing several settings at once.

  • Read the exact paint objective
  • Equip the Airbrush rather than a cleaning brush
  • Select the required palette for customer work
  • Raise opacity and brush size above zero
  • Test a clear, paintable outer surface
  • Save, reload, and retest on the current build
02

Required palette or Freestyle?

Customer orders can specify a particular palette or finish. Using a different owned color may produce a visible design in Freestyle but still leave the job objective incomplete. Freestyle is the creative mode: the official customization announcement says the Airbrush and purchased palettes can be used to create custom device designs. For a paid order, treat the task text as the authority and match the requested palette before assuming the counter is broken.

ModeColor ruleSuccess check
Customer orderUse the palette named by the objectiveRequested paint progress increases
FreestyleUse any palette you ownPaint appears; no customer objective is required
Unclear objectiveReopen the ticket before paintingDevice and requested finish match the job
03

Paint appears but progress stays at 0%

This usually means the stroke and the objective are being evaluated differently. Confirm the correct customer device, requested palette, and paintable face. Avoid internal boards, glass, screens, labels, or parts that the game does not accept as exterior paint targets. Make one controlled stroke on the main shell, then check the objective before covering the whole device. If the correct palette and surface still leave 0%, preserve the save and record the mismatch as a reproducible report.

04

Airbrush moves but no color appears

Check opacity first, then brush size, palette selection, and the target surface. Try a high-contrast color on a broad shell so a faint stroke is not mistaken for no stroke. If Undo becomes available even though nothing appears, the game may be registering input without rendering paint; this behavior has been described in current Steam reports. Do not keep painting blindly. Undo, save separately, reload, and compare the same device and settings after restart.

05

Reports after version 1.0.010r

Multiple players are currently reporting Airbrush failures, including devices that cannot be painted and orders blocked at the painting stage. These are player reports after 1.0.010r, not an official statement that every Airbrush failure has one cause or one guaranteed fix. Palette mistakes, zero opacity, an invalid surface, and a save-specific bug can look similar, so use the checklist before filing a report.

06

What to include in a useful bug report

Record the game build, device model, order source, exact objective text, selected palette, brush size, opacity, and whether Undo activates. Capture the device and 0% counter in one screenshot. State whether Freestyle works, whether another device accepts paint, and whether the same save fails after a full restart. That evidence helps distinguish a palette mismatch from an input, rendering, target-surface, or progression problem.

07

Airbrush troubleshooting checklist

Change one variable at a time and stop after the first confirmed result.

  • Current build is 1.0.010r or later
  • The job includes a paint objective
  • The correct device is on the bench
  • The required palette is selected
  • Opacity and brush size are above zero
  • The test stroke is on an exterior shell
  • A separate save exists before reload
  • The report includes objective, settings, screenshot, and build
SOURCES

Research links

These are the primary pages used to check the facts and current release context in this guide.

Verification note

Official information, observable release behavior, and community reports are deliberately separated. A community report is not presented as a universal fix until it can be reproduced or supported by current patch notes.