/render-lab is an isolated experiment for photo-informed Blender scenes. It
keeps the existing editor/viewer intact and loads its rendering dependencies only
on this route. It is not a replacement for the native renderer or a production
release of the photo reconstruction pipeline.
npm ci
PUBLIC_ENABLE_ANALYTICS=false npm run dev -- --host 127.0.0.1
Open /render-lab and choose a self-contained GLB. Files are decoded in browser
memory; there is no upload, persistence or Firebase integration. External image
and buffer URLs are rejected before loading. Inputs are limited to 128 MiB, 16 MiB
of JSON metadata and two million mesh vertices. This remains a developer preview,
not a hardened loader for arbitrarily hostile assets.
For a private local startup model, explicitly set
OPENPLAN3D_RENDER_LAB_ASSET=/absolute/path/to/model.glb on the dev command. The
Vite middleware serves that one file only to loopback clients, with no-store and
same-origin resource headers. It is disabled in builds and never copies the
asset into static, Git, a deployment or Firebase. Without this opt-in, the page
starts empty and the local file picker works in production too. The route does
not initialize the app’s analytics when opened directly.
three-gpu-pathtracer 0.0.24 / WebGL 2, six light bounces, 1024-pixel
material textures, 3×3 render tiles and progressive accumulation to 512 samples.The material/geometry contract is standard GLB, shared with Blender. Apply mesh modifiers and explicitly export UV texture maps. Blender procedural nodes are not automatically portable: bake micro-normal, roughness and tile patterns before claiming equal material fidelity. The local study exports its captured wood sample, modeled cloth geometry and a tile image; procedural textile bump remains unbaked. Furniture is photo-guided modeling, not photogrammetry. Camera alignment has only qualitative inspection; measured reprojection remains pending.
Remaining: bake all material maps, compare matching Blender/browser cameras and lighting quantitatively, exercise touch/mobile/other GPUs and context loss, add browser regression coverage, tune adaptive resolution/denoising, and connect to the shared geometry preparation and app jobs. The upstream WebGL path tracer has announced a future WebGPU migration; this pinned prototype does not precommit the production renderer to either backend.
References: path tracer API, planned WebGPU migration.
The same viewer can be published without SvelteKit’s server or the main app:
NODE_ENV=production npm run build:render-lab
The default output is /tmp/openplan3d-render-site; set RENDER_LAB_OUTPUT to
choose another build directory. This build includes no Firebase SDK, analytics,
server routes, private files or models. It opens with the local GLB picker.
Only after the model owner explicitly authorizes public distribution, set
VITE_RENDER_LAB_MODEL=/demo.glb during the build and copy the approved derived
GLB to the output directory as demo.glb. The hosted model is downloadable;
a hard-to-guess preview URL is not access control. Full original scan bundles and
capture photos must not be included. Hosting the viewer does not move rendering
to Firebase: rendering still runs on each visitor’s GPU.
September 8, 2026: viewer-only build deployed to
https://openplan3d-render-lab.web.app in Firebase project openplan3d, on the
separate Hosting site openplan3d-render-lab. It contains four static files
(1,120,431 bytes before compression) and no private model or media. The main App
Hosting app and the default Hosting site were not changed. Visitors choose a
local GLB; rendering stays in their browser. Public distribution of the apartment
model was not authorized and remains excluded.
September 9 update: the user explicitly authorized making the latest derived
floorplan-full-walls-v4.glb the automatic default on this site. The new build
loads that public asset at startup; local file loading remains available. The
five-file deployment includes the approved GLB, but no raw scan archive or full
capture-photo collection. Rendering still runs in the browser. The model remains
outside Git. The live model’s SHA-256 matches the local source:
cf74c27ece38ed61c7969b7367f81adc12bda2fcc51a4e7455f11130762477aa.
See the archive handoff for exact files,
deployment reproduction and the separate native release status.