Preload Component Priority Ordering for Low-Traffic VR Scenes

Question

Preload Component Asset OrderingA-Frame's preload component caches external assets across entity lifetimes, preventing redundant network requests when the same asset is referenced multiple times. However, the component does not expose a priority or ordering mechanism for asset loading. In low-traffic VR workloads, this means low-priority assets may block high-priority ones during scene startup, creating unnecessary latency for critical resources.The 'visible' state of an entity does not automatically cancel preload, requiring manual component disposal or lifecycle hooks to achieve cost reduction. Instanced meshes share geometry via BufferGeometry, and preload caching interacts when the same geometry is referenced across multiple entities, reducing duplicate loads. Changes to the preload component between major releases may affect asset caching expectations.Which assets should receive loading priority when multiple entities reference the same external resource in a low-traffic VR scene? Should high-priority assets be loaded before lower-priority ones, or is there a configuration option to control this behavior?

Tasadduq Burney · Answer

AnswerHigh‑priority assets should be loaded before lower‑priority ones; A‑Frame’s preload component does not provide a built‑in priority flag, so you must control the order yourself.Confirmed factsThe preload component caches an asset after the first network request; subsequent references use the cache.The timing of that first request follows the order in which assets are first encountered in the DOM (or as they are queued by the internal loader).There is no configuration option to set load priority in any released version of A‑Frame.Likely explanationBecause requests are issued as the loader processes entities, the browser may still reorder them under HTTP/2 multiplexing, but the dominant factor is the DOM‑first‑encounter order.Steps for this caseIdentify the assets that are high‑priority (e.g., skybox, main avatar, interaction controllers).Place the entities that reference those assets earlier in the HTML file before any entities that only need low‑priority assets.If you cannot reorder the DOM, attach a dedicated preload component to the high‑priority entities and ensure it runs (e.g., via init) before attaching preload to low‑priority entities.Optionally, create a small wrapper component that sorts your asset URLs by a user‑defined weight and then calls the loader manually.If you observe network requests that do not follow the DOM order, capture a waterfall in Chrome DevTools to confirm whether HTTP/2 reordering is affecting you; otherwise, the steps above are sufficient.

Preload Component Priority Ordering for Low-Traffic VR Scenes

Preload Component Asset Ordering

1 answer

Answer

Confirmed facts

Likely explanation

Steps for this case

Your perspective belongs here.

0 question comments