gtlf-model component reparses same model and creates new texture instances
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
gtlf model component reparses same model for each entity using it even it is referenced via a-assets. It also creates new instances of textures. Having 100 identical entities with gltf-mode="#mymodel" causes slow load time. The entities appear visibly one by one and stats component reports 100 textures if my model has single texture.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the gltf-model component and the a-assets path described in the report, then trace how repeated entity references are parsed and how textures are created. Done means multiple entities using the same referenced model do not reparse it or create duplicate texture instances, while loading remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100