← ClaudeAtlas

signature-360listed

Build a production 360 virtual tour from a Blender scene to a working web viewer, the way the the cinematic reference residence tour was built: a persistent headless Blender server, equirectangular Cycles renders in quality tiers, generation-prefixed publishing with instant rollback, and a dependency-free WebGL panorama viewer with doorway-aimed hotspots, a floor-plan minimap and a view cone. Trigger on "360 tour", "virtual tour", "panorama", "equirect", "walkthrough of the apartment", "make a 3D showroom", "render the rooms", "panorama viewer", "Blender render pipeline", "photosphere", or when a property, hotel, venue or interior needs a navigable 360 experience on the web. Do NOT use for video-based tours or for generic Blender modelling help. For the surrounding website design use signature-design instead.
sva-admin/signature-skills · ★ 0 · Web & Frontend · score 67
Install: claude install-skill sva-admin/signature-skills
# Signature 360 A working eight-room residence tour, rendered in Blender and delivered as one HTML file with no 3D library. This skill is the pipeline, including the mistakes, because the mistakes cost more than the code did. Drawn from a shipped client project. The project itself is private, so the room names, coordinates and figures below are illustrative; the settings, the measured costs and the failure modes are real. ## What the pipeline actually is ``` .blend scene | persistent headless Blender server on a dedicated port | detached python drivers, one per render generation v pNN-<room>.jpg 4096x2048 equirectangular, Cycles pNN-<room>-m.jpg 2048x1024 mobile variant, made at publish time | publisher rewrites ONE string in the viewer v tour.html dependency-free WebGL, hotspots, minimap, view cone ``` Four ideas carry the whole thing: **a Blender that stays alive between calls**, **quality tiers so you never wait for a look-dev render**, **generation prefixes so publishing and rollback are one string change**, and **a viewer that aims its hotspots at doorways rather than at cameras**. ## The three laws These are the expensive ones. Everything else you can rediscover cheaply. ### 1. Trust the output file, never the client **"Render stalled" is almost always false.** Blender finishes the render and writes the file, while the python client times out and reports `[Errno 32] Broken pipe` immediately after a `Saved:` line.