back to the wallSimmonsBench / 67 of 74
3D · REAL-TIME

Build a real-time 3D experience (you pick the concept)

the prompt
Build one real-time 3D experience that demonstrates the absolute ceiling of your 3D and simulation capability. You choose what it is. That decision is part of what's being evaluated. Context you should know: this is going into a video comparing you against other frontier models, shown to a large audience, and your work will be credited to you by name. Every model gets this exact prompt. So go nuts and show people what you're actually capable of. Requirements: 1. **You pick the concept, but the obvious answers are off the table.** Do not build any of the following: - A black hole. No gravitational lensing, no accretion disk, no relativistic ray-marched singularity. Two different frontier models returned this same build last time and the audience will recognize it immediately. - A solar system, planet, nebula, starfield, or any other "space object rotating in a void." - A single hero object floating on an empty background with a turntable camera — a crystal, an engine, a spaceship, an abstract sculpture. Build a **place with real scale that the viewer is inside of and can move through.** Somewhere with a floor, a horizon or an enclosure, a sense of how big it is, and things happening in it at more than one distance. The strongest build of the last round worked because it put the viewer underwater inside a collapsed limestone dome with light falling through a breach in the ceiling — you were somewhere, not looking at something. 2. **Technical ambition is the point, and it has to look genuinely realistic or genuinely art-directed** — photoreal materials and lighting, or a fully committed stylized look executed to a professional standard. Untextured primitives and flat-shaded blobs are failures. Pull from whatever best showcases you — including but not limited to: PBR materials and physically-based lighting, HDRI environments and image-based lighting, post-processing stacks (bloom, SSAO, SSR, depth of field, chromatic aberration, film grain), volumetrics and god rays, atmospheric scattering, custom GLSL shaders, raymarching and signed distance fields, GPU instancing at scale, particle and physics simulation, fluid, cloth and soft-body dynamics, procedural geometry and terrain, water and caustics, character or object animation, inverse kinematics, morph targets, point clouds, LOD systems, deliberate camera choreography. Choose what serves the place you're building rather than working through the list. 3. **Simulation should be doing real work.** The "& simulation" half of this test is usually the part that gets skipped — a beautiful static set with an orbit camera is only half the build. Something in the scene should be genuinely simulated and responsive rather than looped or baked. 4. **You have free reign to look up how to use any of these**, and to add any other technique you think demonstrates more. The list is a starting point, not a boundary. 5. **You are graded on what you left out.** A scene where three things are executed impeccably beats one with every post-processing effect stacked on top of each other. Restraint is part of what's being measured. 6. **Do not hand back the house style.** Dark void, neon or purple emissive glow, a lens flare and a particle field. It reads as a default rather than a decision. If you land on any of it, earn it and make it specific to your concept. 7. **It has to run in real time and be interactive.** The viewer can move through it, orbit it, or otherwise affect it. Target a smooth 60fps — a beautiful scene that stutters is a failed build. 8. **Single self-contained `index.html`.** Any library via CDN. No build step, no server, no API keys. 9. **No hotlinked 3D assets or stock textures, but you may pull in open source libraries freely** — geometry generators, noise libraries, physics engines, shader libraries, anything on a CDN. Generate geometry and materials procedurally or author them yourself. Image generation is available if you want texture or environment plates to treat in-engine, though procedural is usually stronger: ``` python3 /Users/patsimmons/coding/clearhaven-instantly-campaign_1.19.26/clearhaven-os/scripts/vendor/chatgpt-imagegen.py \ "<your prompt>" -o ./assets/<name>.png --size 1536x1024 --timeout 300 --quiet ``` 10. **QA it for real.** Load it, move the camera through the whole scene, stress it, watch the frame rate. Fix anything that stutters, z-fights, clips, or throws console errors. Work completely autonomously. Do not ask for anything until it's finished. DONE when: it loads clean, holds 60fps, is genuinely interactive, something in it is actually simulated, and it's a place with scale rather than an object in a void.
GENERATION · LOCKED
Drag back for older model generations · coming soon
🔒 LOCKED
JAN '25
JUNE '26
All 0 models · same prompt · $0.00 total
sort: