have entities wait on assets in order to make use of xhrloader cache #1700
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Entities were not waiting for assets to load This caused duplicate asset fetching if an asset was defined in
<a-assets>and an entity was also fetching an asset through a component.This makes entities wait for
<a-assets>(if exists) to load. This ensures all<a-asset-item>s have been fetched and made into theTHREE.Cacheused byTHREE.XHRLoader. Subsequent fetches from loaders (e.g.,ColladaLoader,OBJLoader,MTLLoader) will automatically pull from the cache.Depended on #1689, which has been merged.
Changes proposed:
<a-assets>to load if exists.