3D, VR & spatial ·
Same brief, two AI models, wildly different sprite packs
One brief - knight sprites for a medieval 2D isometric game - given to two models, and the packs that came back are not the same thing. One drew classic pixel art directly in code: 3 animations, one colour scheme, a README, 10 files at 174 KB. The other wrote a 3D model of the knight in code, rendered it, and flattened it back to pixels: 6 animations including guard, hurt and death, 8 facing directions, 4 team liveries, 1024 unique frame cells, a separate shadow layer and an engine manifest. 49 files, 9.3 MB, roughly 8x the animation frames.
The interesting part is not which is better, it is that they disagreed about where the job ends. Same sentence, same skill level, wildly different idea of "done" - one read it as a starting point to build on, the other as a production asset pack to ship. Sprite work like this used to be a contractor and a two week turnaround; the bottleneck now is writing a brief specific enough to get the scope you actually wanted.
Made by u/bobo-the-merciful. This write-up follows the original post; it is not an independent product test.
Keep up with what gets built.
Read the daily AI briefing, browse the tools, or sign up for briefing email updates.