Asset Loading And Content

Last reviewed: 2026-06-30

Asset Sources

Source	Current use
Assets/StreamingAssets	Config JSON, camera shot JSON, bot policies, generated screen HTML, Reveal assets, sample media.
Remote/local HTTP URLs	Sample config points to http://localhost:8000/anuvatest/... for images/audio.
Scene serialized assets	Sets, lighting, cameras, materials, render textures, canvases, bot references.
Prefabs	Assets/AnuvaSets/Prefabs/AnuvaRoom_EV.prefab.
Resources	DOTween settings and plugin resources.
Addressables/AssetBundles	Unity modules are installed, but first-party Addressables/AssetBundle loading was not confirmed.

Runtime Loading

Content	Loader
Presentation config	UnityWebRequest.Get() to local file URL or remote URL.
Scene image	UnityWebRequestTexture.GetTexture().
Voiceover/background audio	UnityWebRequestMultimedia.GetAudioClip().
Camera shots	File.ReadAllText(Path.Combine(Application.streamingAssetsPath, "CameraShots.json")).
Bot arm policies	File.ReadAllText(Path.Combine(Application.streamingAssetsPath, "BotArmPosePolicies.json")).
Bot motion plan	Sibling of config source or generated fallback.
Virtual screen generated HTML	Vuplex WebView loads file:///.../StreamingAssets/AnuvaVirtualScreens/generated/*.html.

Local Vs Remote Assumptions

The sample config assumes a local content server at localhost:8000. The Python Server docs say Python validates local content URLs before render.start; Unity still performs its own fetch/retry and fails preparation if required media cannot be loaded.

For local editor playback without Python, the developer must ensure referenced URLs are reachable or use local file paths/StreamingAssets.

Unsupported Or Unconfirmed

• Dynamic Addressables or AssetBundle loading for sets/bots/media: Unknown / not confirmed in repo.
• Runtime bot prefab selection by studio.bot.botId: Unknown / not confirmed in repo.
• Runtime set prefab selection by studio.set.setId: Unknown / not confirmed in repo.
• Remote media authentication/signing: Unknown / not confirmed in repo.