## QR and offline QR failures

- Confirm Share is enabled, then confirm whether the station is in cloud relay mode or offline QR mode.
- For cloud mode: verify internet and relay connected status before blaming QR generation.
- For offline mode: verify hotspot availability, SSID accuracy, and that guest phones join the same local network.
- Test QR from real phones, not only desktop previews.

## Email delivery failures

- Check queue state first: pending, uploading, failed, or sent.
- Open the failed queue item and inspect error message, recipients, and attached files.
- Recheck SMTP sender settings, required fields, and template placeholders after any config change.

## Print failures

- Confirm printing is enabled in both Share Settings and the active Share preset.
- Confirm the selected printer is online and paper settings match the expected format.
- If processed-source printing fails, test with input or fallback mode to isolate recipe/output timing issues.

## Portal and link persistence failures

- Confirm relay service is running and authenticated.
- If session is invalid, sign in again and rerun a full end-to-end share.
- If offline QR mode is enabled, remember that portal relay delivery is bypassed.

## Missing recipient export

- Export email CSV from Share Settings Logs after applying the intended filters.
- If export is unexpectedly empty, confirm there are queue records in the selected state/date scope.


Sharing or delivery issues

- Use a sharing station at the guest handoff point so staff can confirm a result, show the QR code, or send the email.
- Use a replay station on a larger screen when guests or staff should browse finished sessions.
- Use kiosk or guided mode for public-facing screens that should stay on a narrow, event-specific flow.


Choose station roles

- From Devices, send a station to the correct event page instead of walking to the screen and typing a URL by hand.
- For public screens, keep the station pinned to its event role so guests cannot wander into operator-only parts of the app.
- If a screen shows the wrong page during the event, correct it from Devices and confirm the physical display updates.


Keep stations on task

- Test every station on the real event network before doors open, especially tablets, TVs, and older browsers.
- Confirm power, screen sleep settings, fullscreen mode, Wi-Fi or Ethernet stability, and the station name shown in Devices.
- Walk the real guest flow once: capture, review, share, scan QR, open the link, and replay the result on the intended screen.


Pre-event checklist

- Open the station page on each tablet, TV, kiosk, or operator browser, then confirm it appears online in Devices.
- Give each station a practical name based on its physical location, such as Share counter, Replay TV, or Staff tablet.
- Keep the Devices page open during setup so you can see which screens are connected before guests arrive.


Register and identify screens

| Shortcut | Action |
| --- | --- |
| Ctrl + , | Toggle dashboard layout editor. |
| Ctrl + L | Cycle dashboard display mode (normal / locked / minimal). |
| Escape | Close the dashboard layout editor. |


Dashboard & layout

| Shortcut | Action |
| --- | --- |
| Ctrl + Shift + mouse wheel | Zoom into the area under the cursor. |
| Ctrl + Shift + 0 | Reset magnification to 1x. |
| Escape | Reset magnification to 1x. |


Screen magnifier

| Shortcut | Action |
| --- | --- |
| Ctrl + Shift + H | Go to the dashboard. |
| Ctrl + 1 … 9 | Jump to Quick Nav slot 1–9 (configurable in Quick Nav settings). |
| Ctrl + Shift + O | Open the current page in an external browser. |

Quick Nav presets are configured in Settings > Quick Nav. Each preset can hold up to 9 pages mapped to Ctrl+1 through Ctrl+9.


Navigation

| Shortcut | Action |
| --- | --- |
| F11 or Alt+Enter | Toggle window fullscreen (or browser fullscreen in a web session). |
| Ctrl + Shift + F9 | Cycle demo window size presets (16:9 / 9:16 / 1:1). |
| PageUp | Toggle black screen overlay (for long-exposure photography). |
| Escape or click | Dismiss the black screen overlay. |


Window & display

| Shortcut | Action |
| --- | --- |
| ← / → | Previous / next dataset. |
| ↑ / ↓ | Previous / next frame. |
| PgUp / PgDn | Previous / next iteration. |
| G | Go to frame number. |
| Scroll wheel | Zoom in / out (at cursor). |
| Click + drag | Pan (when zoomed). |
| Double-click | Toggle fit ↔ 100%. |
| + / − | Step zoom in / out. |
| 0 | Fit to screen. |
| 1 | 100% zoom (1:1). |
| F | Cycle fit mode (fit / width / height). |
| B | Cycle background (black / white / checker). |
| C | Cycle guide overlay (off / crosshair / 3×3 / 4×4). |
| ? | Show / hide shortcuts. |
| Escape | Close inspector. |

These shortcuts are active when the Frames inspector is open.


Frames inspector

| Shortcut | Action |
| --- | --- |
| 0 … 5 | On the dataset detail page, clear or set the saved star rating. |
| Escape | Cancel pending transfer, dismiss bulk-action bar, or exit selection mode. |
| Ctrl + , | Open Library settings. |


Library

| Shortcut | Action |
| --- | --- |
| ← / → | Previous / next dataset. |
| 0 … 5 | Clear or set star rating on the current dataset (0 = clear, 1 = one star, 5 = five stars). |
| Escape | Close settings panel, or go back. |
| Ctrl + , | Open Quickview settings. |

Rating shortcuts work on the Quickview page and on the Quickview dashboard tile.


Quickview

| Shortcut | Action |
| --- | --- |
| F10 | Capture a JPG screenshot of the app window immediately. |
| Ctrl + F10 | Capture a JPG screenshot of the app window after a 2-second delay. |
| F7 | Start recording the app window. While recording: pause or resume. |
| F8 | Stop recording and save the clip. |

Recordings are saved in the active working folder under sessions/, each in its own folder named after its final MP4. Screenshots are saved separately under screenshots/.

Demo camera overlay shortcuts work after the overlay is configured. Camera 1, Camera 2, and Both view cycling becomes available once Camera 2 is running.

> Note: the demo-camera-overlay shortcut table from the original in-app help (camera bubble position/resize/zoom keys) is app-shell specific and was intentionally left out of this first migration pass; it can be added as its own page once its module ownership is confirmed.


Screeva

## What this export contains

- Export from Share Settings Logs to download a CSV of email queue recipients.
- Each row includes recipient email, dataset folder, status, sent date, plus configured custom fields.
- The export reflects queue history and filters, so apply your date and state filters before exporting.

## Why teams use it

- Post-event handoff to marketing or CRM systems.
- Delivery auditing for sent versus failed batches.
- Field-level analysis when custom form data is captured during sharing.

## Good practice

- Export at least once during rehearsal to validate field mapping.
- Keep a final export snapshot at event close for reporting and recovery workflows.

Download email list

## Core email flow

- Use email sharing when guests should receive a delivery link after operator confirmation.
- Keep templates, subject line, and reply-to aligned with the event brand before the first capture.
- Use required terms and custom fields only where compliance or follow-up needs justify the extra steps.

## Controls that affect delivery quality

- Enable multiple recipients only when operators are expected to send one capture to several contacts.
- Keep direct download available when email inbox access may be delayed on site.
- Verify SMTP sender configuration and test against real inbox providers before launch.

## Queue operations

- Monitor queue state for sent, pending, uploading, and failed jobs.
- Use queue details to inspect dataset path, attached files, subject preview, and rendered email body.
- Retry failed items from queue actions after fixing config or connectivity issues.


Email sharing

## What offline QR mode changes

- Offline QR mode bypasses cloud relay delivery and serves files from the local machine.
- The share modal shows two QR codes: one for joining Wi-Fi and one for opening the local download page.
- This mode is intended for venues with unstable internet or fully offline operations.

## Setup requirements

- Configure a dedicated sharing hotspot and set the expected Wi-Fi SSID in Share Settings.
- Keep the sharing station and guest phones on that same local network segment.
- Test with real phones before doors open. Do not rely on desktop browser simulation for this mode.

## Operational cautions

- If guests cannot join Wi-Fi, the download QR will still fail even if the code scans correctly.
- If the station sleeps, reboots, or changes network, retest both QR codes immediately.
- Use portal delivery instead when links must remain reachable after the local station is gone.


Offline QR sharing

## Define the output set before opening Share

- Decide which outputs are actually needed at handoff: image, video, combined media, thumbnail, and any print-specific version.
- Keep output naming clear so operators can quickly identify what is guest-facing versus archival.
- Use Process recipes to lock branding, overlays, framing, and ratio choices before the first live capture.
- Keep the output list lean. Too many variants slow down review and increase wrong-action clicks at the station.

## Match outputs to the delivery path

- QR and direct download should point to files that are light enough for phone delivery on event Wi-Fi.
- Email delivery should use the same branded files guests expect from QR, unless you intentionally send a different variant.
- Printing should have its own prepared source strategy (input, processed, both, or auto) so print quality is predictable.
- Portal delivery is best when links must stay valid after the booth machine powers down.

## Operator checklist before doors open

- Confirm one complete flow for each promised action: QR, email, print, and portal link when enabled.
- Confirm filenames and sorting make sense when multiple outputs are attached to the same capture.
- Confirm terms and custom fields only collect what the event actually needs.


Plan deliverables

## When portal delivery is the right choice

- Use portal delivery when links must remain active after the local sharing station is offline.
- Use it for events where guests often open media later, not only on-site.

## Dependencies to verify

- Confirm internet reachability and relay connection from Share Status.
- Confirm the app has a valid login session. Invalid or expired sessions can block relay startup.
- Keep offline QR mode disabled when you need cloud relay behavior, because offline mode bypasses relay delivery.

## Operational notes

- Run a full phone test from scan to final open link before guests arrive.
- Keep one operator check focused on relay and portal status after any network change.


Portal delivery

## Enable printing in the right places

- Turn on printing in Share Settings, then enable the print action in the Share preset used at the station.
- Refresh the printer list and choose a preferred printer before the event starts.
- Set paper size and copy limits so operators cannot accidentally overload a printer line.

## Choose print source strategy

- Input: fastest path from original files.
- Processed: uses branded outputs from recipes.
- Both or auto: useful when some captures have processed files and others do not.
- Enable fallback to input when processed files might not be ready in time.

## Live print workflow checks

- Test single and bulk print flows from the actual Share station.
- Verify quantity prompts only if your team needs per-job copy overrides.
- Watch print job status (queued, printing, completed, failed) during early event traffic.

Printing

## When to use QR sharing

- Use QR sharing when guests scan from the station and complete delivery on their own phone.
- Use it for single captures or multi-select batches from the Share screen.

## Configuration points that matter

- Choose QR placement for operator clarity: overlay on media preview or hidden from inline cards.
- Tune QR size and overlay position so the code stays readable on your actual sharing display.
- Keep direct download enabled when guests should save files immediately after opening the share page.
- Enable "require email before QR" only when your event needs contact collection before phone handoff.

## Live-operation checks

- Confirm Share is enabled and relay status is connected when using cloud QR mode.
- Scan from at least one Android and one iPhone device on the event network.
- Confirm both single-item and bulk QR flows if operators will share multiple captures together.


QR sharing

## Full pre-event test sequence

- Capture one real sample and verify all expected outputs exist.
- Run one QR share from the station screen and open it on a real phone.
- Run one email share and confirm inbox delivery, template rendering, and link behavior.
- Run one print job if printing is enabled, including copy-count behavior when quantity prompts are enabled.
- Run one portal delivery validation when cloud relay mode is expected.

## Validate details, not only success

- Confirm filenames and output variants are understandable to operators.
- Confirm terms, custom fields, and required email gates match the event policy.
- Confirm timing is acceptable under normal venue network conditions.

## Record and fix before go-live

- Log every mismatch (wrong branding, missing output, failed queue item, broken QR, print error).
- Fix settings first, then rerun the same test path until results are stable.


Run a test share

- When a result looks correct, promote that dataset as the active reference from the dataset menu in Library or from the Camera Alignment module itself.
- Future datasets on the same untouched rig can reuse the active reference automatically, so you do not need to align every capture again.


Set the active reference

- For markerless alignment, keep the arc within ~120 degrees, centre the subject, favour textured clothing, and light evenly.
- If a camera was bumped, analyze a fresh capture and promote it as the new reference.


Alignment failed

- Default. Cloud/3D runs Xangle-hosted 3D camera registration with no local install. Use this when you want managed processing and fast setup.
- RealityScan/3D is a full desktop 3D camera registration workflow via RealityScan (Epic Games, Windows only). Use this when you want a local 3D workflow and reusable reference files for later processing.
- Track/2D is an in-app 2D alignment path. No external tool is required, but it is meant for fixed arcs and does not recover real 3D camera poses.

## Engine comparison

On clean, properly lit datasets, all three registration engines can produce the same alignment result. For the cleanest alignment, follow the capture guidelines above.

- **Cloud/3D**: Efficiency 7/10. No extra app to install. There is no warranty on result quality, but it is generally good in normal capture conditions.
- **RealityScan/3D**: Efficiency 9/10. Excellent quality in most setups, but it requires a RealityScan license from Epic Games and runs on Windows only.
- **Track/2D**: Efficiency 5/10. Fast and fully in-app. Best for fixed arcs, not full 360 rigs.


Choose the engine

- Cloud camera registration runs on Xangle workers, so no extra software installation is required.
- Images are uploaded only for the active job and are deleted after results are downloaded.
- Usage is measured with camera registration credits: one registration job costs one credit, regardless of camera count.
- Credits are consumed only when the cloud registration job completes successfully.


Cloud camera registration

RealityScan is the default 3D alignment engine in Camera Server. Epic's official install flow is:

1. RealityScan runs on Windows only. Download and install the Epic Games Launcher from the official RealityScan download page.
2. Open the launcher, create or sign in to your Epic Games account, then open the RealityScan tab under the Unreal Engine section.
3. Install the latest RealityScan build. In Camera Server, you can usually leave the RealityScan path empty so it auto-detects the install under C:\Program Files\Epic Games.
4. If RealityScan was installed somewhere else, paste the executable path manually in the Alignment settings.
5. Run one reference dataset from Camera Alignment or Library to confirm Camera Server can launch RealityScan headlessly and write the reference files.

## Cost and licensing

- Epic currently lists RealityScan as free for students, educators, educational institutions, and individuals or companies under $1 million USD in annual gross revenue.
- Above the $1 million USD revenue threshold, Epic sells yearly RealityScan seats. The public license page currently lists CA$1,697 per seat per year and also advertises a 30-day trial.
- Check the official RealityScan licensing page before budgeting or purchasing seats, because public pricing and terms can change.

## Learning and support

- Epic Developer Community provides RealityScan documentation, tutorials, sample datasets, and community forums when you need to learn the tool or troubleshoot the install.


Install RealityScan

An in-app alignment engine that straightens an arc of photos without RealityScan or any calibration markers. It works directly on the images by tracking the center subject from one camera to the next.

## When to use it

- Best for a fixed camera rig where the cameras do not move between captures. Align once, then reuse the result as the active reference for every later dataset.
- A fast, fully offline alternative to RealityScan or COLMAP that needs no external tool and no markers.
- It produces a 2D similarity transform per camera: shift, rotate, and uniform zoom. That is enough to straighten orbit or arc captures, but not enough for full 3D photogrammetry.

## Capture requirements

- **Up to 120 degrees of arc.** Beyond roughly 120 degrees, adjacent cameras stop sharing enough of the same view and the match can drift. Keep the total arc at 120 degrees or less.
- **A centered subject is required.** The engine locks onto whatever sits in the middle of the frame, so the subject must stay roughly centered in every camera.
- **Texture helps.** Dress the subject in patterned or detailed clothing when possible. Flat or single-colour surfaces give the matcher less to lock onto.
- **Light it properly.** Even, bright lighting gives crisp detail to match. Harsh shadows, blown highlights, or a dim subject reduce the number of usable features.

## How it works

- The first camera is the reference. Each following camera is matched to its neighbor, and those small steps are chained back to the reference to stay in the high-overlap region.
- Matching runs inside a centered region of interest so the subject, not a busy background, drives the alignment.
- A common interior crop is computed so every aligned frame stays inside the valid image area with no black edges.

## Tuning the settings

- **ROI width and height (%).** This is the size of the center region used for matching. Widen it if the subject fills the frame; tighten it if the background is pulling the alignment away from the subject.
- **Max ORB features.** Raise it for low-texture scenes to find more matches, but expect slower processing. Lower it when the subject is already richly textured and speed matters more.
- **Sub-pixel refinement iterations.** These are the ECC sub-pixel refinement passes. More iterations can sharpen the lock at the cost of time; the default is a good balance.

## Reusing the result

- When the alignment succeeds, the computed transforms are saved and the dataset becomes the active reference.
- Later datasets captured on the same untouched rig automatically reuse those transforms. If you physically move or re-aim any camera, run the alignment again to refresh the reference.

## Important boundary

Track/2D is purely 2D. It does not recover real 3D camera poses, so it is meant for straightening orbit or arc turntable shots, not for full photogrammetry or Gaussian-splat reconstruction.


Track/2D alignment

- If any camera is bumped, re-aimed, re-focused, or moved during the event, capture a fresh alignment shot and promote it as the new reference before continuing.
- If the rig changes a lot between captures, enable auto re-align for new datasets instead of relying on one long-lived reference.


Recover from a bumped camera

## How to get a strong camera registration

- Frame the subject in the center so each camera sees the same central mass instead of edge clutter.
- Use even, stable lighting and avoid flicker, harsh shadows, or blown highlights.
- Keep the subject still so every camera captures the same moment in time.
- Prefer textured clothing or surfaces so the alignment engine can match the same 3D environment more reliably.

## What RealityScan writes

- Reference XMP sidecars for each registered camera.
- registration.csv for the aligned camera rig.
- A sparse point cloud for the 3D alignment preview.
- Optional: native COLMAP export for downstream processing when that setting is enabled.


Xangle Orbit

Troubleshooting

Sharing or delivery issues

QR and offline QR failures

Email delivery failures

Print failures

Portal and link persistence failures

Missing recipient export