-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sprite in container not playing animation #6052
Comments
I am facing the same issue. Here is another repro: https://jsfiddle.net/sushovande/muafr6jc/ Note: the workaround is the manually add the same sprite to the scene again, that forces it to be updated. |
… in the same frame were not correctly removed from the UpdateList. Fix #5803 #5817 #5818 #6052 * `ProcessQueue.isActive` is a new method that tests if the given object is in the active list, or not. * `ProcessQueue.isPending` is a new method that tests if the given object is in the pending insertion list, or not. * `ProcessQueue.isDestroying` is a new method that tests if the given object is pending destruction, or not. * `ProcessQueue.add` will no longer place the item into the pending list if it's already active or pending. * `ProcessQueue.remove` will check if the item is in the pending list, and simply remove it, rather than destroying it.
Thank you for submitting this issue. We have fixed this and the fix has been pushed to the |
it still repros on 3.60.0-beta-9 https://jsfiddle.net/sushovande/wjec9qh8/2/ |
This is fixed. Test case here: http://labs.phaser.io/view.html?src=src/bugs/6052%20anim%20in%20container.js&v=dev |
Version
Description
When adding a sprite to a container and playing an animation, the animation is not playing (stuck on first frame). Found this bug in newest version (3.55.2), found a forum thread about this, but it seems no one issued a bug?
Forum thread with description: https://phaser.discourse.group/t/sprite-inside-container-doesnt-play-animations-in-phaser-3-53-and-newer/9765/4
Example Test Code
Additional Information
pinning Phaser to version 3.52.0 resolves the issue
The text was updated successfully, but these errors were encountered: