Agree. The pelican benchmark was interesting a year ago when most models struggled and a good pelican indicated an unusually capable model. Now it’s saturated and uninteresting.
A good new benchmark should have awful performance to start and there should be a lot of headroom for improvement. This benchmark is also intentionally difficult and requires the LLM to develop the animation through spatial reasoning and first principals rather than existing video generation pipelines. Similar to how SVG generation was out of distribution for most models a year ago.
I think it's interesting to see them visibly struggling to improve. Claude pelicans aren't much better today than they where 18 months.
Rendering 3d worlds has hugely improved though.
Have you seen pelicans in Simon Willison’s tests? It is still not a pelican on bike I would like to publish :)
Imho we don’t need to make benchmarks that draw the whole 3D world. Pelican’s drawing is really nice in its simplicity and complexity at the same time.
It seems to be an obscene waste of compute time to generate useless 3D worlds that are just a bragging - 3D is really heavy discipline to make it right, see Mark Zuckerberg’s ceased attempt with 3D VR…
Multiply it by thousands times as a lot of people have found out threejs lib and prompt “generate 3D world and make no mistake” are new orange/black.
Do you expect the SVG to emulate a hand-drawn picture, become more realistic, or just a more detailed illustration?
As for the often quoted issues with the bike's frame or problem with the steering column, I can't really tell, I am no bike expert.
I can instead judge how poor of a job it is doing with a LOTR rendition in Three.js, so that seems like a better benchmark.
A general benchmark (even Simon mentioned that it was meant as fun at the beginning) should be quick and easy to run, since we can expect that more people will want to try it out. That’s why I’m more like “team Pelican on a Bike”… :) cheers