[4.0.0-rc.6] Creating a spine object when the loader is busy can lead to a black frame
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 40.3k
- Forks
- 7.2k
- PR merge metrics
- No merged PRs in 30d
Description
Version
*Phaser Version: 4.0.0-.rc6
*Operating system: Windows 11
*Browser: Google Chrome
*Spine Plugin: "@esotericsoftware/spine-phaser-v4": "^4.2.95",
Description
Creating a spine object when the phaser loader is busy can lead to a black frame being rendered on spine object creation
Example Test Code
const spineObject = this.scene.add.spine(0,0, "spine_skel", "spine_atlas"); spineObject.animationState.addAnimation(0, "idle", true);
Additional Information
https://github.com/user-attachments/assets/3d0038e4-5dea-40c0-b9ae-b679539e78cc
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 issue with the provided scene.add.spine example while the Phaser loader is busy, using the listed Phaser, Spine plugin, Windows 11, and Chrome versions. Trace the loader and spine-object creation entry points; done means creating the spine object no longer produces a black frame.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100