https://www.booooooom.com/2016/05/09/bicycles-built-based-on...
I am not a mechanical engineer, so even prompting well with ME lingo probably will take some effort.
Totally agree though, anyone with a vague understanding of how bikes works ignores the pelican because they know the bike is unrideable in the first place.
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.
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.
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.