Fable 5 vs Opus 5 for 2D Sprites

I gave Fable 5 and Opus 5 the same task: create knight sprites for a medieval 2D isometric game.

Both models produced good, usable sprite packs with 8 facing directions and smooth animations. The main differences were in scope, detail, and how the sprites were made.

- Fable 5 created a small, focused pack. It drew classic pixel art directly in code: 3 animations (idle, walk, attack), one colour scheme, and clear instructions in a README. Simple and easy to drop into a game.

- Opus 5 went much further. It built a small 3D model of the knight in code and rendered it into pixel art. The pack has 6 animations (adding guard, hurt, and death), 4 team colours, a separate shadow layer, a machine-readable manifest for game engines, and preview images and GIFs.

By the numbers: Fable 5 shipped 10 files at 174 KB, while Opus 5 shipped 49 files at 9.3 MB - about 8 times more animation frames overall.

At a high level, Fable delivered a clean starting point, while Opus delivered something closer to a complete production asset pack.

Both models can clearly create useful game art. The difference is how far they take the job before calling it done.

The knight isn't drawn frame-by-frame; it's rendered by generate_knight.py from a tiny 3D model. The body is described as simple primitives (sphere chains for limbs and armor, a disc for the shield, a quad for the sword blade). Each animation is a function that poses the joints per frame, then the whole model is rotated in 45° steps to get all 8 facings from a single pose. Primitives are projected with a simple isometric camera, depth-sorted, and drawn straight to 48×48 pixels with hard-edged shapes, a limited palette with ball-style shading, a 1px silhouette outline pass, and a baked drop shadow. Frames are then tiled into the three sprite sheets at 1× and 2×.

Tools - Python 3.13 with Pillow 12 for all rendering (no other dependencies), visual iteration by inspecting rendered contact sheets between tweaks, Playwright to test the preview page, and the artifact page as the animated viewer with embedded downloads.

The sprites were not drawn. They were rendered. A knight is defined once as a rigged 3D figure built from oriented boxes and ellipsoids. For each frame, the rig is posed, rotated to the required facing, and raycast through a fixed isometric camera. The resulting surface normals are quantised into a small hand-authored colour ramp, giving pixel art out the far end. Because one model feeds every frame, all 8 facings and all 6 animations agree on proportion, lighting and palette by construction, and any change to the knight re-renders everywhere in about 15 seconds.

Build me some knight sprites which I can use in my new medieval 2D isometric game. The game doesn't exist yet I am starting with sprites - this is the first thing we are building.