Spine Canvas plugin display issues
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: 3.55
- Operating system: MacOS
- Browser:
Description
Display issues appear when using the Spine Canvas plugin. WebGL plugin doesn't show any issues, but display issues and alpha weirdness with Canvas plugin.
Example Test Code
Many spine demos on Phaser site don't work when 'Force Canvas' button is pressed, like this one:
http://labs.phaser.io/edit.html?src=src/spine/basic%20spineboy.js&v=3.55.0
If the Config is edited to use Phaser.CANVAS, part of the spine game object isn't displayed. I have seen multiple issues with timelines affecting spine objects' alpha values, most notably when another tween in the game is setting the alpha of its target. The Spine object's alpha values change during the running of the other tween. Again, this behavior doesn't occur when Phaser.WEBGL is used in the game config.
Additional Information
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
Run the linked spineboy demo with Phaser.CANVAS and compare it with Phaser.WEBGL. Start with the Spine Canvas plugin and the Phaser.CANVAS configuration, using the missing display parts and alpha changes during another tween as reproduction criteria. Done means the Spine object displays correctly and its alpha remains stable in Canvas mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100