playcanvas / playcanvas/engine
Improve behaviour when multiple application instances are created
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16.8k
- Forks
- 2k
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 222
Description
At the moment some functionality needs to execute inside the update part of the application for it to work correctly, for example:
getApplication()GraphicsDeviceAccess.get()
This makes it complicated to call engine's functionality from outside of the update.
Specific example: https://forum.playcanvas.com/t/instantiaterenderentity-fails-with-multiple-application-instances/33421
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 reproducing the linked forum scenario with multiple application instances, then trace getApplication() and GraphicsDeviceAccess.get() when called outside the application update. Before coding, clarify the intended behavior and acceptance criteria for engine functionality invoked outside update; the issue does not name 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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100