DEV Community

Ed Orellana
Ed Orellana

Posted on Originally published at flockbay.com

Opus 5.5 vs GPT-6.1 Sol in Blender: One Cost 7x More

Last time, four AI models built this dwarf miner with no Blender, written out as text. This time the two best, Claude Opus 5.5 in Claude Code and GPT-6.1 Sol in Codex, get Blender, and they have to animate the walk themselves. Same prompt, same reference picture. Each ran Blender from scripts it wrote, exported the character, and made a small Godot game where he walks back and forth with his feet planted.

Source: https://flockbay.com/blog/opus-5-5-vs-gpt-6-1-sol-build-a-rigged-character-in-blender-for-godot/ · Updated 2026-10-09

The test

Then all four dwarves, with and without Blender, were filmed in the same studio and measured the same way: geometry under the floor, triangles, the clips as imported, and how far a planted foot moves in each game.

The prompt

The exact prompt both got:

Build a game-ready 3D character for a Godot game: a stocky dwarf miner with a thick braided beard, a leather helmet with a lamp on the front, a wool shirt under a leather apron, a wide belt, heavy boots, and a pickaxe in his right hand. Make him look like the reference picture. Build him in Blender. Blender 5.1 is installed on this PC and blender is on your PATH: run it in the background from your shell, with blender --background --python and scripts you write, and keep those scripts and your .blend in a folder named blender in this game, so he can be built again from them. Everything about him is made in Blender by your scripts: the mesh, the materials, the skeleton, the skinning, and two animation clips you key yourself, named Idle and Walk. Both loop, and the Walk is a walk cycle that stays in place. Export him as one .glb into this game. Anything that ships with Blender is yours to use. Don't use Flockbay's modeler or its asset library, don't use Tripo, Meshy or any other 3D tool or service, and don't download anything: no model, rig, animation, texture or add-on. He has to look right from every side, not just the front, and hold together while he walks: his knees, elbows and shoulders bend cleanly, his beard and apron move with him, nothing pokes through, and the pickaxe stays straight and in his hand. Keep him within a triangle budget a game could ship. In the game he is about a dwarf's height in metres, stands on the floor and faces -Z, Godot's forward. Then put him in the game: one small scene with a floor, a light and a camera at his side, where he walks back and forth across the floor on his own, playing the Walk clip and turning round at each end, with his feet planted, not sliding. Make it the game's main scene. Use Blender from your shell to build him and to look at him. Run and test the game only through Flockbay's tools: flockbay_play, flockbay_run_headless, flockbay_script_errors, flockbay_game_input, flockbay_game_get, flockbay_game_set, flockbay_game_screenshot, flockbay_last_run and flockbay_stop. Don't start Godot from your own shell, and if one of those tools can't do something you need, say exactly what was missing in your handover. Look at your own work, fix what you see, and hand him over when you think he's done.

What was judged

The character against the reference, and beside the dwarf the same model built without Blender: silhouette, proportions, colours, hands, from every side.

The walk it keyed: the four poses, the joints, the feet, the seam, in the studio and in its own game.

The build: a clean import, triangles, materials, file size, bones and skinning, height and facing.

How it worked: Blender runs, renders it looked at, Plays, what it fixed between them.

What it cost, beside the same model's run without Blender: minutes, tokens, and the estimated API bill.

In the video

  • 0:00 Last time: no Blender
  • 0:13 The rules this time
  • 0:35 Claude Opus 5.5's dwarf
  • 1:09 Why a walk slides
  • 1:56 GPT-6.1 Sol's dwarf
  • 2:34 Where both slip: the turns
  • 3:09 Under the hood: two ways to plant a foot
  • 3:52 The bill
  • 4:17 The pick

It ran in Claude Code, on Flockbay’s MCP server

Claude Opus 5.5 ran in Claude Code for 37 minutes on the prompt above, with Flockbay’s tools connected over MCP: 22 calls to Flockbay’s tools and 88 to Claude Code’s own. Every call, from the run’s transcript:

Tool Calls
Bash 43
Read 27
Edit 10
Write 8
flockbay_game_screenshot 5
flockbay_run_headless 5
flockbay_play 4
flockbay_script_errors 4
flockbay_guide 3
flockbay_game_get 1

Godot’s output caught the first bug

The first check that failed was flockbay_run_headless on res://tests/dwarf_model_test.tscn. The lines it returned that name the problem:

Ran res://tests/dwarf_model_test.tscn headless: it quit by itself with exit code 1 after 0.02 s of game time (frame 1 of 300).
[12] FAIL Idle does not loop
[13] FAIL Walk does not loop
Enter fullscreen mode Exit fullscreen mode

The next edit went to res://blender/build_dwarf.py

The next edit Claude Code made after that check, through Bash:

sed -i "s/    return lambda co: chain_w(co, \[H, K, A\], \['Hips', f'Thigh_{s}', f'Shin_{s}', f'Foot_{s}'\], \[0.06, 0.05, 0.03\])/    # weighted by height on the leg's own axis, so the trousers and the boot\n    # shaft over them get the same weights and bend as one\n    return lambda co: chain_w(V(H.x, leg_y(co.z), co.z), [H, K, A], ['Hips', f'Thigh_{s}', f'Shin_{s}', f'Foot_{s}'], [0.06, 0.05, 0.03])/" blender/build_dwarf.py
Enter fullscreen mode Exit fullscreen mode

res://scenes/dwarf_walker.gd as it was handed over

Lines 1 to 40 of 95, from the game folder at the end of the build.

extends Node3D

## Walks the dwarf miner back and forth across the floor, playing his Walk
## clip and turning round at each end.
##
## The body is never given a speed. Every physics tick the foot that is on
## the ground (the one that landed most recently) is pinned where it was, and
## the body goes wherever the clip's legs push it. On the straight that is the
## clip's own stride speed; through the turn the planted foot pivots on the
## spot. Either way the feet stay planted and never slide.

## How far either side of the middle he walks before turning round.
@export var half_length := 1.9
## How fast he turns round, in degrees per second.
@export var turn_speed_deg := 120.0

## Where in the Walk clip each foot lands, as a share of the stride. Set by
## blender/build_dwarf.py, which keys the clip.
const LEFT_LANDS := 0.0
const RIGHT_LANDS := 0.5

var _anim: AnimationPlayer
var _skel: Skeleton3D
var _ball := {}
var _going := 1.0
var _turn_left := 0.0
var _turn_sign := -1.0

## Readings for checking him in a running game.
var planted := ""
var planted_ball := Vector3.ZERO
var ground_speed := 0.0
var turning := false

func _ready() -> void:
    _anim = find_child("AnimationPlayer", true, false) as AnimationPlayer
    _skel = find_children("*", "Skeleton3D", true, false)[0] as Skeleton3D
    for clip in ["Idle", "Walk"]:
        _anim.get_animation(clip).loop_mode = Animation.LOOP_LINEAR
Enter fullscreen mode Exit fullscreen mode

Download Flockbay free: Built in Flockbay, a free AI game maker built on Godot. https://flockbay.com/free-ai-game-maker/

Related: Four AI models build the same character with no Blender, How to make games in Claude Code, How to make games in Codex

I make Flockbay, a free AI game maker built on Godot. The original is on flockbay.com.

Top comments (0)