Tutorial — Packaging Builds for Each Surface

Augmented Traveler local tutorial. Back to Unreal — Tutorials · headsets: Tutorial — OpenXR Headset Builds · streaming: Tutorial — Pixel Streaming 2 · kiosk: Kiosk — Process

How to turn the studio project into installable builds:

• a Windows kiosk;
• an Android APK for Quest, Vive standalone and Android XR;
• Pixel Streaming servers;
• visionOS on the Mac seat.

Draft. Toolchain versions change with hotfixes. Check the 5.8 release notes and Epic's platform requirement pages before installing.

1. Key ideas

• Cook: convert assets for one platform.
• Package: put the cooked content and executable into a build.
• Deploy/Launch: install on a device and run.
• Build configurations:

• 5.8 changes:
  • Zen server is now the default store for cooked output;
  • Incremental Cooking is in Beta; use it for faster iteration, not for release builds until proven.

2. Toolchains

3. Package from the editor (simple)

1. Platforms → (target) → Package Project. Choose an output folder: Builds/<Surface>/<Date>_<Version>/.
2. Set the configuration (Development or Shipping) under Platforms → Packaging Settings first.
3. Project Settings → Packaging:
   • list the maps to cook (only that surface's levels);
   • turn on Use Pak File / IoStore;
   • leave out editor-only and test content.

4. Project Launcher profiles (repeatable)

Use Platform → Project Launcher and make one custom profile per surface. Save it and check it into source control:

Automation later: the DevOps engineer turns these into command-line BuildCookRun scripts on the build machine.

5. Kiosk specifics

1. Shipping build. Start it full-screen with -fullscreen. Add Pixel Streaming arguments only for streaming builds.
2. Windows kiosk set-up: a dedicated local user, auto-login, auto-start (Task Scheduler), no notifications, power settings "never sleep".
3. Watchdog: a small service restarts the app if it stops responding, and restarts it nightly. Logs go to a folder the dashboard reads.
4. Offline fallback: the program runs monologues if the conversation service is unreachable (Tutorial — Authoring a Q&A Experience with Ambient Idle).
5. Hardening checklist: owned by the kiosk integrator (Kiosk — Process).

6. Versioning and QA

• Build names: AT_<Surface>_<Config>_<YYYYMMDD>_<changelist>.
• Keep the last 3 shipped builds of each surface for rollback.
• QA runs the device matrix on every Shipping build: kiosk PC, Quest 3, and one Android XR device if in scope.
• Record known issues in the build notes.

7. Check before a venue build

• Shipping configuration; no dev console
• Only that surface's maps and characters cooked (size check)
• Runs from cold boot to program with no input (kiosk)
• Offline fallback works with the network unplugged
• Build notes and version recorded; previous build kept

Sources

• Epic, Packaging your project: https://dev.epicgames.com/documentation/unreal-engine/packaging-your-project
• Epic, Using the Project Launcher: https://dev.epicgames.com/documentation/unreal-engine/using-the-project-launcher-in-unreal-engine?lang=en-US
• Epic, Build configurations reference: https://dev.epicgames.com/documentation/en-us/unreal-engine/build-configurations-reference-for-unreal-engine
• Epic, Preparing projects for release: https://dev.epicgames.com/documentation/en-us/unreal-engine/preparing-unreal-engine-projects-for-release
• Epic, Android development requirements: https://dev.epicgames.com/documentation/en-us/unreal-engine/android-development-requirements-for-unreal-engine
• Epic, UE 5.8 release notes (Zen, incremental cooking, toolchains): https://dev.epicgames.com/documentation/unreal-engine/unreal-engine-5-8-release-notes?lang=en-US
• Full list: Sources — 2026-09-19