playcanvas / playcanvas/engine
Reference-counted Assets
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16.8k
- Forks
- 2k
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 222
Description
Hi!
What about using reference-counted assets feature to better handle Asset lifecycle (for example: loading assets only when they are needed and unloading them when they are no more needed (there is not any asset reference bound to given asset))?
Take a look at my proposition of reference-counted assets feature (that already exists in one of my projects, it's tested and works well):
https://gist.github.com/PsichiX/a0e6efdb9920fe58e39b
Right now i have to use hand-written plugin that hooks into PlayCanvas to solve that but it cannot be so simply integrated with all assets pipeline so it will be better if Assets pipeline will be able to handle reference-counted assets life-cycle :)
Cheers! ^^
Btw. how to assign proper labels to this 'issue'? :D
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 by reading the linked reference-counted assets proposal and comparing it with PlayCanvas's existing assets pipeline. Define how references, loading, and unloading should integrate with that pipeline, then confirm the expected lifecycle behavior before implementation; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100