← ClaudeAtlas

web3d-realism-performancelisted

How to make a real-time browser 3D scene (three.js, React Three Fiber, CesiumJS, WebGL/WebGPU) look more photorealistic while keeping or improving its frame time, and how to film it. Covers measuring frame time and visual change, cheap wins (draw order, batching, skipping shader work), baked lighting (Cycles lightmaps, reflection probe), PBR, vegetation impostors, glTF optimisation, CAD models repeated many times, real-place landscapes from elevation data (terrain, relief, treeline, matching photos) and frame-exact demo videos of a live WebGL app. Use whenever the user wants a web 3D scene to look better, more realistic or more "premium", faster or smoother, mentions frame rate, draw calls, jank, GPU cost, lightmaps, baking, shadows, reflections, PBR, forests, CAD models, LOD, soft 3D on phones, terrain or DEM scenes, matching a place to photos, or a screen recording, demo video or clip of a 3D app, even if they don't name these techniques.
saad-git-007/claude-skills · ★ 1 · Web & Frontend · score 74
Install: claude install-skill saad-git-007/claude-skills
# Photorealism and performance for web 3D scenes Lessons from building and tuning a three.js portfolio scene (a glass pavilion on a sea cliff, a forest, about 250 draw calls): 11 measured optimisation iterations cut mean frame time by 22% with no visible change, and a Cycles light bake added soft bounce light for +3% frame time. The two goals are not in conflict as often as it seems. Most of the real cost in a typical scene is wasted work (pixels shaded and then painted over, lights evaluated where they add nothing), and most of the realism comes from light that can be computed once, offline, instead of every frame. ## The working loop Everything below depends on being able to answer two questions with numbers: *did this make it faster?* and *did the image change?* Set that up before touching the scene, because intuition about GPU cost is wrong surprisingly often (in the project, a depth pre-pass, strict front-to-back sorting and plain PCF shadows all looked like wins and were not). 1. **Make the scene deterministic.** Pin every animation (wind, water, clouds, rotating props) to a fixed time before measuring. Unpinned tree sway alone made identical code differ by 2% SSIM. 2. **Benchmark fixed poses on a real GPU.** Headless Chrome with a GPU: `--use-angle=gl-egl --ignore-gpu-blocklist --enable-gpu` (Linux) and `env -u DISPLAY` so it uses EGL rather than a virtual X display. Software WebGL (SwiftShader, llvmpipe, Playwright's default) says nothing about GPU cost,