Skip to content
AI Primer
workflow

Fable 5.2 agents recreate MengTo’s Three.js trailer in Blender in hours

MengTo says Fable 5.2 orchestrated Opus 5.5 agents to recreate his Three.js trailer in Blender in hours. The workflow uses reference images and render checks, with Claude on a MacBook and rendering on Runpod.

4 min read
Fable 5.2 agents recreate MengTo’s Three.js trailer in Blender in hours
Fable 5.2 agents recreate MengTo’s Three.js trailer in Blender in hours

TL;DR

  • An existing Three.js trailer got a Blender rebuild in hours: MengTo says Fable 5.2 orchestrated Opus 5.5 agents to make it.
  • The rendering stayed off his laptop: Claude ran on a MacBook while Blender rendered on Runpod, according to his setup.
  • Scene reuse also produced a playable FPS: MengTo's Japanese-inspired demo built on his sakura environment and fit into HTML under 10 MB.

The café workflow MengTo shared ended with a script finding 45 object intersections after a human spotted a cup clipping into a windowsill. His go-to dream-loop skill can regenerate its own target image after seeing the current build.

Three.js to Blender

MengTo's Blender glow-up began with mostly finished Three.js scenes. He says Fable 5.2 at medium effort coordinated Opus 5.5 agents at high effort to recreate his game trailer in “a few hours.”

Lighting caused trouble initially; he described the transfer as otherwise nearly 1:1, with more detail, in a follow-up.

MacBook control, Runpod rendering

MengTo's hardware split put the work on two machines:

  • MacBook: Claude runs locally.
  • Runpod: Blender renders on remote compute.

He described the connection as MCP plus headless operation. Blender's command-line manual documents rendering over SSH without a graphical display.

The official Blender MCP server exposes Blender's Python API to language models. Its security notice says generated code executes without guards against deleting data or sending it elsewhere.

Three reference images and 13 stages

MengTo also shared a separate café-building workflow by Kamome Ashizawa. Its recipe makes the reference-and-review process explicit:

  1. Inputs: Three reference images and a short shop backstory.
  2. Harness: A CLAUDE.md file plus subagents for planning, modeling, rendering and visual checks.
  3. Build: A plan followed by 13 modeling stages, each rendered from the reference camera angle for comparison.
  4. Asset rule: No downloaded models, textures or HDRIs.
  5. Refinement order: Light and color first, followed by materials, shapes and lived-in clutter.

The original write-up adds an important wrinkle: the visual reviewer had initially passed the cup intersecting the windowsill. After Ashizawa flagged it, the agent added an intersection test covering 326 props.

Dream-loop and five other skills

MengTo's regular skill stack spans visual iteration, interface design and software inspection:

  1. Dream-loop: Image-generated targets, iterative builds and a separate visual critic.
  2. Hairline: Isometric line drawings that respond to the pointer.
  3. Emil Kowalski's skills: Design-engineering and animation guidance.
  4. MengTo's skills: Reusable workflows for designers and builders.
  5. REA: Reverse-engineering how an app or website works.
  6. HTML Demo: Live, time-driven HTML demonstrations of an app.

Dream-loop installs with npx skills add achimala/dream-loop. Its README requires image generation and vision input; subagents are strongly preferred.

A sakura-valley FPS

Existing Three.js work can carry over, MengTo said in a reply. His Japanese-inspired FPS built on an earlier sakura scene and, according to his post, fit into HTML under 10 MB with no image or model files.

He also described downloading open-source textures during development, alongside using references and dream-loop. Ashizawa's no-downloaded-assets rule belonged to the separate café project.

Exact triangle budgets

In a separate experiment, gokayfem reported rebuilding one cat photo in Blender with Fable 5.2 and Opus 5.5, using no textures or image-to-3D model. He said each requested triangle count was met exactly:

  • 100 triangles
  • 200 triangles
  • 500 triangles
  • 1,000 triangles

One reference photo, four exact triangle budgets

A scroll-controlled video hero

MengTo's HeyGen Video 1 landing page used one 30-second, 2K take for the entire hero:

  • Camera route: Floor plan → model → house → interior → sky.
  • Scroll behavior: The sequence plays in reverse.
  • Shared materials: The workflow, prompts and a free template.

A single video take becomes a scroll-controlled landing page

Further reading

Discussion across the web

Where this story is being discussed, in original context.

On X· 8 threads
TL;DR1 post
Three.js to Blender2 posts
MacBook control, Runpod rendering2 posts
Three reference images and 13 stages1 post
Dream-loop and five other skills1 post
A sakura-valley FPS2 posts
Exact triangle budgets1 post
A scroll-controlled video hero1 post
Share on X