AUGMENTED THEATRE — STARTER AR SET
==================================

This folder is a complete, working AR set — the same one the Dashboard
stages as its demo. Drop the folder onto the Dashboard's delivery table
and it will import, ready to send to the house. Then take it apart and
replace every piece with your own: it exists to be a starting point.

The full designer's manual lives at
https://augmented-theatre.web.app/#manual
(see "Building an AR set, step by step" and "The ar-set.json companion file").


WHAT IS IN THE FOLDER
---------------------

drawing.jpg        The anchor image. The phone recognises this and the
                   AR set stands on it. Here it is a drawing meant to be
                   printed on an A4 sheet and handed to the audience —
                   but an anchor can as well be a photograph of an
                   object in the venue, or of the stage itself, taken
                   from where the audience will stand. Give yours
                   detail and contrast (at least 640 px across), and
                   make it visually distinct from every other AR set's
                   anchor in the show.

stage.glb          The AR set itself: one glTF-Binary file. This one is a
                   small stage — floor, backdrop, apron, and two
                   screens — authored the way AR sets should be authored:
                   in real metres, Z-up, sized to stand on the 0.21 m
                   printed sheet. The two screens are *named* mesh
                   nodes ("screen-left", "screen-right") with UV
                   coordinates — that is how video finds a surface.

screen-left.mp4    The videos projected onto the two screens. Any
screen-right.mp4   .mp4/.mov/.m4v works; each is bound to its surface
                   by ar-set.json below (naming a video after its surface
                   would work too, and a Blender custom property named
                   "video" on the node is the most portable way).

ar-set.json        The companion file. Every key is optional; this one
                   spells everything out so you can see the shape:

                   marker       which image is the anchor
                   model        which .glb is the AR set
                   widthMeters  the width the anchor really has in the
                                venue, in metres (0.21 = A4 sheet).
                                The whole AR set scales from this number.
                   scale        multiplier bringing one model unit to
                                one metre (1 = authored in metres)
                   projections  surface node name -> video filename


MAKING IT YOURS
---------------

1. Replace drawing.jpg with your own anchor. Measure the real thing
   and set widthMeters to match.

2. Open Blender. Model your AR set in metres, Z-up (Blender's native
   axes), imagining the anchor lying flat at the origin — the AR set
   stands on and around it, facing -Y, towards the viewer. Name every
   surface that will carry video, and UV-unwrap those surfaces.

3. Export as glTF Binary (.glb), one file. Untick "+Y Up" — the
   phones expect the file Z-up and do the turn themselves. Tick
   "Include > Custom Properties" if your video bindings live in the
   model.

4. Replace the videos, update ar-set.json's "projections" (or delete the
   key if your bindings are in the model or in the filenames).

5. Rename the folder — its name becomes the AR set's id and title — and
   drop it onto the Dashboard. The import sheet will tell you plainly
   if anything is missing or ambiguous; nothing is sent until the
   errors are gone.

Keep the whole folder well under 60 MB: every phone in the house pulls
all of it during walk-in.
