Bot Workspace: making every avatar right
Answer me with artifact · 2026-10-30 08:12

Bot Workspace: making every avatar right

A

Why some came back bad

Today 17 of 24 models passed my check, and 7 failed. Every failure traces back to the picture fed into the 3D step:

  • Flat or glowing art (Prism, Rogue, Zest): the 3D tool guesses the depth and makes a thin slab or a broken shape.
  • Soft, fluffy edges (Pip the bird, Nib): the tool wraps a disc or ring around the body.
  • Plain backs on all of them: the art shows only the front, so the back gets one flat colour.

The 4 floor bots that I redrew first as clean solid figurines all came out clean as pictures. That redraw step is the fix.

Floor bots redrawn as solid figurines: clean input for 3D
Floor bots redrawn as solid figurines: clean input for 3D
B

The new way, for every character

  1. Redraw the front: the character as one solid, thick figurine on plain white, with no base and no background. It keeps the same face, colours and shape. (Free ChatGPT lane.)
  2. Redraw the back: the same figurine from behind, so the back gets real detail.
  3. Check the redraw against the original art before any 3D runs. If a redraw changes the character, I redraw it.
  4. Make it in 3D from the front, and paint it from both the front and the back.
  5. Check the model from 4 sides on one sheet per pack. I remake a failure with a new seed, then with a new redraw. After 2 tries it keeps its robot body, and I name it.
  6. You see only finished packs, where every character passes.
C

Cost to this Mac

  • Time: one character takes about 12 minutes and 11 GB, one at a time.
  • All 200: about 40 hours, run overnight only (10 pm to 8 am), so about 4 nights. The Mac stays free in the day.
  • Free lane: about 400 redraws, about 1 a minute.
  • Order: your floor bots tonight first, then the packs you use most.
D

Space on this Mac

The 11 GB is memory while one model runs. It is freed when that model finishes, so it does not add up.

  • Disk per character: about 12 MB of working files. The finished model on the site is about 0.4 MB.
  • Cleanup: when a pack passes and goes on the site, I delete its working files. Only the 0.4 MB models stay.
  • Guard: the run pauses if free disk drops below 40 GB, or if memory gets tight.
  • The 3D tool itself: 7.5 GB, kept during the run and deleted at the end.
  • Cleared today: 8 GB of unused files from the test runs. This Mac now has 130 GB free.
Run it this way?