cao_visite_camera
Pilot a virtual visit camera by action sequences ('avancer', 'pivoter_gauche') or keyboard shortcuts, with wall-collision detection. Start from any waypoint or overall view; get step-by-step states and a path for 4K rendering.
Instructions
WHEN the automatic visit is good but ONE view is wrong — the façade is cut off, the ridge is out of frame, you want to step into the next room — and rewriting a whole chemin by hand would be absurd. PILOT the camera with a SEQUENCE OF ACTIONS instead of coordinates: ['avancer x3', 'pivoter_gauche', 'monter', 'zoom_arriere']. Actions are named (avancer, reculer, gauche, droite, the four diagonals, monter, descendre, pivoter_gauche/droite, incliner_haut/bas, zoom_avant, zoom_arriere, vue_initiale, vue_ensemble, piece_suivante, piece_precedente) or given as the KEYBOARD SHORTCUT a human would press in the render studio ('ctrl+8' = forward, numeric keypad laid out as a compass rose). Same grammar both ways, so a view prepared here is reproduced exactly by hand. Start from depuis (any waypoint of a chemin from cao_visite_plan) or omit it for an overall view. POST THE SCENE TOO: it enables wall collision (a step that would end inside a partition is refused and explained, not silently applied) and the room landmarks. Returns {camera, etapes[] (state after EACH action, with the reason for refused steps), chemin[]} — feed chemin straight back to cao_visite_studio to render that exact viewpoint in 4K. Catalogue of actions and keys (free, no key): GET /api/v1/cao/visite/commandes. Requires API key. REST: POST /api/v1/cao/visite/camera.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| murs | No | Walls: plan segments extruded vertically | |
| plan | No | 2D reference lines | |
| boites | No | Boxes (furniture, volumes): center x,y + dims l,p,h (mm) | |
| depuis | No | Starting viewpoint — same shape as a `chemin` waypoint. Omit for an overall view of the building. | |
| actions | Yes | Ordered sequence. Each item is an action code ('avancer'), a keyboard shortcut ('ctrl+8'), a repeat form ('avancer x3'), or {code, repetitions}. 200 items max. | |
| cercles | No | Circles on the 2D plan, alongside plan[] lines: each has a centre and a radius, in the same unit as the plan. Use for round shapes a polyline would render badly — fillets, posts, manholes. | |
| reseaux | No | Plumbing pipe runs (EF/EC/EU/EV/EP/chauffage) — used only by cao_pdf (technical plan + linear-meter quantities per type). | |
| reglages | No | Step sizes. Defaults: 500 mm per move, 250 mm per altitude step, 15° per rotation, ×1.25 per zoom. `grand_pas: true` = the Shift key (×4). | |
| toitures | No | Roofs — used only by cao_pdf. WITHOUT this field: a flat roof is auto-generated over the footprint of ALL walls (legacy default). WITH it: compose freely — each entry can target a subset of walls (via `murs`), letting you build an L-shaped building's roof, or add a dormer on top of a main roof. | |
| plomberie | No | Sanitary fixtures (sink, WC, shower…) — used only by cao_pdf. Same positioning as electricite. | |
| decoration | No | Paint/finish per wall — used only by cao_pdf. Colors the elevations (exterior face) and the axonometric view (face auto-detected by orientation relative to the building's centroid). | |
| ouvertures | No | Doors/windows embedded in a wall — used only by cao_pdf (elevations + axonometric view), no effect on dxf/metres. | |
| electricite | No | Electrical symbols (outlets, switches, lights…) — used only by cao_pdf (dedicated technical plan + quantities), no effect on dxf/metres/render. Position: attached to a wall (`mur`+`position`, like ouvertures) or free (`x`,`y`). |