Asset management for hunts
Prepare the images and 3D files your hunt and objects need before you build or launch.
In this article, you'll see which assets a Treasure Hunt uses, when each one matters, and how to prepare a clean asset set before launch.
The core asset checklist
Most hunts only need a small, predictable set of files:
| Asset | Where it is used | When it is required |
|---|---|---|
| Hunt banner image | Hunt General tab | Required for the hunt entry point |
| Object 3D asset | Each object | Required for 3D First and AR First objects |
| USDZ version of the object | AR-first object on iOS | Recommended whenever the hunt should work well on iPhone and iPad |
| Treasure hunt map | Hunt Treasure Hunt Configuration | Optional, only when the hunt uses a map |
| Completion question image | Hunt Treasure Hunt Configuration | Optional, only when the final hunt question needs visual support |
| Optional environment or skybox images | Object advanced 3D settings | Optional, only when the object uses those visual settings |
Prepare assets before you build
The cleanest workflow is to prepare the hunt asset set before you begin detailed configuration:
- choose the final hunt banner
- prepare one approved 3D model per object
- keep the GLB and USDZ versions aligned to the same design
- decide which objects need map markers, hints, or advanced 3D visuals
This reduces rework later when you start testing the route on real devices.
Match the asset to the experience mode
| Experience mode | What to prepare |
|---|---|
3D First | The object's 3D asset |
AR First | The object's GLB asset, plus USDZ when you want a better iOS experience |
If you are unsure which mode to use yet, start by validating the model in 3D First, then switch to AR First once the asset, interaction, and route all work as expected.
Hunt-level assets versus object-level assets
It helps to treat the hunt and object assets differently:
- the hunt banner, map, and optional completion-question image support the overall route
- each object's 3D asset supports one discovery moment inside that route
For example, the hunt banner might introduce a "Space Explorer Trail," while each object asset represents a different planet-themed collectible participants discover along the way.
Check the assets before launch
Before you publish:
- open every object once in preview
- test AR-first objects on the devices that matter most
- confirm the hunt banner looks right on the hunt entry point
- confirm map markers and physical placement still match
Use validation as the final asset check
Publish validation is good at catching missing banners, missing object assets, and incomplete AR file sets. Treat it as the last checkpoint, not the first one.
Common asset-related issues
| Validation message | What it means | Fix |
|---|---|---|
Treasure hunt '{{treasure_hunt_name}}' is missing a banner image | The hunt entry point has no banner. | Upload the banner image in General. |
Treasure hunt object '{{treasure_hunt_object_name}}' in {{visualization_mode}} mode requires an asset | The object has no 3D model attached. | Select the object's asset before launch. |
Asset '{{asset_name}}' for treasure hunt object '{{treasure_hunt_object_name}}' is missing a GLB 3D model file | The AR file set is incomplete. | Upload the GLB version. |
Asset '{{asset_name}}' for treasure hunt object '{{treasure_hunt_object_name}}' is missing a USDZ 3D model file | The iOS-friendly AR file is missing. | Upload the USDZ version when you plan to support iPhone and iPad well. |
Related
Configure hunt objects — 3D mode
Attach the asset and finish a 3D-first object.
Configure hunt objects — AR mode
Prepare the mobile file set needed for an AR-first experience.
Test the hunt
Run device checks before you rely on the asset set in a live venue.
3D/AR rendering issues
Diagnose problems caused by missing files, unsupported devices, or asset setup issues.