Yeah, that's a good point. My basic pelican test doesn't allow the model to render their work and iterate on it. The 3D models all come from agent systems that are rendering with Blender or screenshotting with Playwright along the way.

Have you looked at assbench.com? Even with threeJS rendering, screenshotting with Playwright, and iteration (check the prompt) some of the models are shockingly bad. I wonder whether the rendering quality is affected by the requirement for skin physics on click; if so, it raises a valid question about models creating pretty pictures but break when interactivity is required.

(As I said in a separate comment above, results are all bikini-clad and not revealing. However, whether it is NSFW is up to you/your work policies.)

If you allow rendering and iteration on the basic pelican test, does it improve the final output?

I’d really like to see what each model comes up with if given a basic harness to render and iterate. They’ve all gotten pretty good at basic one shot pelicans, but seeing what they do when given a direct goal, and even getting a time lapse of each image as they edit and adjust would be really fun.