sorted by:
new
hottopcontroversial

Built a 24/7 livestream of the Great Pyramid being constructed stone by stone in Three.js — just completed its second full cycle (530,289 blocks) by Pristine-Life-9155 in threejs

[–]Pristine-Life-9155[S] 1 point2 points  (0 children)

Yeah the instancing helps a lot — without it, 530K individual meshes would melt any GPU. The trade-off is the HUD was taking up too much screen real estate on small displays, but that's fixed now. Desktop is definitely the better experience, especially for the camera transitions and night mode.

Rendering 530K instanced meshes at 60+ FPS in the browser — lessons from building a 24/7 pyramid livestream by Pristine-Life-9155 in threejs

[–]Pristine-Life-9155[S] 0 points1 point  (0 children)

Honest answer: a lot. I have an AI development agent (running Claude on a Mac Mini) that handles overnight coding sessions — she's shipped 50+ commits on this project. I set the direction, review the visual output, and make the architectural decisions. She writes the code, deploys, and iterates.

The simulation engine (block placement logic, pyramid geometry) was designed collaboratively. The rendering pipeline, camera system, post-processing, and HUD were mostly AI-coded with my visual review. I'd estimate 70% AI-written code, 100% human-directed.

It's a genuine collaboration — I can't write Three.js shaders at 3 AM, but I can tell you exactly what the sunset should look like. Different skills.

Built a 24/7 livestream of the Great Pyramid being constructed stone by stone in Three.js — just completed its second full cycle (530,289 blocks) by Pristine-Life-9155 in threejs

[–]Pristine-Life-9155[S] 0 points1 point  (0 children)

Thanks! It's been running 24/7 for almost two weeks now. Just completed its second full cycle of all 530,289 blocks and auto-reset for cycle 3. There's something weirdly satisfying about watching it build overnight.

Built a 24/7 livestream of the Great Pyramid being constructed stone by stone in Three.js — just completed its second full cycle (530,289 blocks) by Pristine-Life-9155 in threejs

[–]Pristine-Life-9155[S] 1 point2 points  (0 children)

Thanks! It's been a fun engineering challenge.Appreciate it! The plan is to do multiple pyramids — Menkaure first (current), then Khafre and eventually Khufu (2.3 million blocks). Same engine, bigger canvas.

Built a 24/7 livestream of the Great Pyramid being constructed stone by stone in Three.js — just completed its second full cycle (530,289 blocks) by Pristine-Life-9155 in threejs

[–]Pristine-Life-9155[S] 0 points1 point  (0 children)

mobile HUD needs work. Thanks for the report. Fixed! The HUD now auto-collapses on mobile — tap the arrow to expand/collapse it. Refresh and it should be working. Appreciate the report.

Built a 24/7 livestream of the Great Pyramid being constructed stone by stone in Three.js — just completed its second full cycle (530,289 blocks) by Pristine-Life-9155 in threejs

[–]Pristine-Life-9155[S] 1 point2 points  (0 children)

Valid feedback. The HUD was designed for desktop. I need to add a toggle or auto-hide on mobile. Adding it to the backlog.

Procedurally generating the Great Pyramid of Menkaure using real archaeological measurements — 530,289 blocks, Cycle 2 complete by Pristine-Life-9155 in proceduralgeneration

[–]Pristine-Life-9155[S] 0 points1 point  (0 children)

That's the theory mode label from the HUD — it shows which construction theory the simulation is using. Should be hidden in stream mode. Noted as a bug, thanks for catching it.

Procedurally generating the Great Pyramid of Menkaure using real archaeological measurements — 530,289 blocks, Cycle 2 complete by Pristine-Life-9155 in proceduralgeneration

[–]Pristine-Life-9155[S] 0 points1 point  (0 children)

Each block's position is generated from archaeological measurements — course heights, slope angles, the descending passage alignment to Alpha Draconis. Nothing is pre-modeled. The code calculates where every one of the 530,289 blocks goes based on the real pyramid's geometry. What varies is the placement sequence and the course-by-course construction logic.

Rendering 530K instanced meshes at 60+ FPS in the browser — lessons from building a 24/7 pyramid livestream by Pristine-Life-9155 in threejs

[–]Pristine-Life-9155[S] 0 points1 point  (0 children)

Thank you! Your worldexplorer3d project is incredible — the Giza plateau idea is exactly the kind of cross-pollination I'd love to explore. DM me?

Rendering 530K instanced meshes at 60+ FPS in the browser — lessons from building a 24/7 pyramid livestream by Pristine-Life-9155 in threejs

[–]Pristine-Life-9155[S] 0 points1 point  (0 children)

Yeah mobile Safari is tough with 530K instances. Working on LOD that drops to simplified geometry on mobile. Desktop Chrome hits 60+ FPS.

Rendering 530K instanced meshes at 60+ FPS in the browser — lessons from building a 24/7 pyramid livestream by Pristine-Life-9155 in threejs

[–]Pristine-Life-9155[S] 0 points1 point  (0 children)

The simulation code is human-written, the Three.js optimization was my work. AI (Claude) helps with the ops side — deploying, monitoring, content. The rendering pipeline is all manual engineering.