DEV Community

JANCTION Render
JANCTION Render

Posted on

Rendering Blender 5.3 glass dispersion from an AI agent, with no local GPU

https://render.janction.jp

Blender 5.3 came out this week, and JANCTION Render runs it on cloud GPUs as of today. I wanted one shot that shows what 5.3 can do: faceted glass that splits light into colour. This post is the log of making it from an AI agent over MCP, including the two mistakes I made on the way, with the measured time and cost.

Three glass gems rendered with Blender 5.3 Cycles, with rainbow fringes on the facets

The setup

  • JANCTION Render connected to the agent over MCP: https://render.janction.jp/mcp
  • No Blender and no GPU on my machine. The agent writes a bpy script, the service runs it in Blender 5.3 on its GPUs and sends back images
  • Every preview comes back with a short critic verdict (ok / check / fix) and a price for the full render before anything is charged

Try 1: the glass came out black

The first script set Dispersion on the Principled BSDF and used a dark room with thin light strips behind the gems. The preview came back in 5 seconds and the gems were almost black, with no colour at all.

The reason: in Blender 5.3 the dispersion controls of the Principled BSDF sit under Transmission and are named:

p = mat.node_tree.nodes["Principled BSDF"]
p.inputs["Transmission Weight"].default_value = 1.0
p.inputs["IOR"].default_value = 2.4
p.inputs["Transmission Dispersion Scale"].default_value = 1.0
p.inputs["Transmission Dispersion Abbe Number"].default_value = 12.0
Enter fullscreen mode Exit fullscreen mode

My script looked for an input called Dispersion, did not find it, and silently skipped it. The dark room did not help either: glass only shows what is around it.

Try 2: brighter floor, one narrow spot

I made the floor a light grey, put one spotlight behind and above the gems so the pool of light falls towards the camera, and fixed the input names. The next preview showed the rainbow fringes on the facets, and the critic said ok.

Mistake 2: 72 identical frames

I wanted the gems to turn slowly over 72 frames. I rendered 10 frames first, then all 72, and every frame was the same picture. The keyframes were wrong:

# wrong: frame_set() re-evaluates the animation and resets the value I just set
g.rotation_euler = new_value
sc.frame_set(72)
g.keyframe_insert("rotation_euler")

# right: give the frame to keyframe_insert
g.keyframe_insert("rotation_euler", frame=1)
g.rotation_euler = new_value
g.keyframe_insert("rotation_euler", frame=72)
Enter fullscreen mode Exit fullscreen mode

Rendering 10 contiguous frames before the full job is what caught it cheaply. After the fix, the 10-frame test showed the gems moving and no black or duplicate frames, so I ran the full job.

Numbers (measured on 2026-11-11)

Job Settings GPU time Wall time Charged
Preview 1280x720, 32 samples, 1 frame 2.8 GPU s 5 s 1 JPY
10-frame test 1920x1080, 128 samples 59.9 GPU s 19 s 6 JPY
Final 1920x1080, 128 samples, 72 frames 267 GPU s 1 min 25 s 27 JPY

About 3.7 GPU seconds per 1080p frame. The final ran in parallel chunks, so 267 GPU seconds took under a minute and a half.

The scene

The full script is about 90 lines: a light grey floor, five thin emissive strips in the back, one spotlight, three icospheres with the glass material above, and a camera. If you connect JANCTION Render to Claude, Cursor or Codex, you can ask for it in one sentence ("render three glass gems with dispersion in Blender 5.3") and let the agent write its own version.

Try it

  • MCP: https://render.janction.jp/mcp
  • Browser (send a .blend): https://render.janction.jp/start
  • New keys get some free GPU time; after that it is 0.1 JPY per GPU second

https://render.janction.jp

Top comments (0)