Project settings
Settings that apply to the whole project, whichever space a visitor is in.
Display
Preload the AR project makes the experience start more reliably by fetching content up front. It trades a longer wait at the start for fewer stalls once running — worth it for anything with large models.
Analytics
Connect several counters at once. Each takes the id from that service:
| Service | Looks like |
|---|---|
| Yandex Metrica | 87946806 |
| Facebook Pixel | 1234567890123456 |
| Google Analytics | UA-56589716-1 |
A counter added without an id is flagged as a warning rather than silently doing nothing.
Loading screen
The first thing anybody sees, so it is worth a few minutes.
| Setting | Options |
|---|---|
| Background | an image (cover, contain or fill) or a colour |
| Logo | your logo — JPG around 525×525 works well |
| Start button | on or off, with its own colour, text colour and label |
| Onboarding | the prompts explaining what to point at |
| Loader | on or off, which style, and a custom animation |
Replacing it entirely
Above those fields is a Preset selector. Leave it on the default and you get the built-in screen described above.
Choose + Add new and a script takes over both screens outright — the one the visitor taps and the one that fills up. Because that script declares its own settings, whoever uses it afterwards gets a form to fill in rather than code to edit; if it declares none, the panel says so.
That is the route for a branded opening that the built-in fields cannot express. → Loading and the launch screen
Browsers refuse to play audio until the visitor interacts with the page. Without a button to press, your first sound will not play and it will look like a bug.
Languages
Set the default language, and optionally ask visitors which they want on launch.
Controls
Scene rotation access lets visitors rotate the scene themselves, and you choose which axes they may rotate around.
Restricting axes is usually right: an object that can be tumbled freely ends up upside down, and visitors rarely realise that is what they did.
Capture
Let visitors take a photo or record video of what they are seeing. This is the feature that gets an AR experience shared, so it is worth enabling whenever the content is worth showing off.
Project scripts
Behaviour that runs everywhere in the project, in every space. Each slot points at a script or patch file and can be switched off without removing it.
This is the right home for anything that has to survive moving between spaces — a score, a visitor's choices, a session timer.
Domain
Every published project already has an address of the form example.arclip.design. That
address, and the snippet for embedding the project in a page, live in the publish dialog
rather than here.
This section is for putting the project on your own domain instead.
- Type the domain —
ar.example.com, or the bareexample.com— and press Connect. - Point that name at AR Clip in your DNS.
- The status under the field tracks the connection; it turns to connected once the platform has verified the domain and issued its certificate.
Disconnect releases it again.
The exact record to create belongs to the platform rather than to the editor, and it can differ between plans and regions. Ask before you edit DNS — a guessed record simply never verifies.
ar.example.com needs one record and leaves your main site alone. Putting a project on a bare
example.com means moving the whole domain's traffic, which is rarely what anyone wants for a
campaign.
Next: VPS scenes