Skip to content
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

Frame Rate (Sprite Anims) Bug on 3.80+ #7018

Open
SoulStyx opened this issue Jan 26, 2025 · 1 comment
Open

Frame Rate (Sprite Anims) Bug on 3.80+ #7018

SoulStyx opened this issue Jan 26, 2025 · 1 comment

Comments

@SoulStyx
Copy link

SoulStyx commented Jan 26, 2025

Version

  • (BROKEN) Phaser Version: >= 3.80.0
  • (WORKING) Phaser Version: <= 3.70.0
  • Operating system: Windows
  • Browser: Chrome

Description

Seems to be a bug around setting the frameRate property in sprite.play(). When playing the animation, it just completely ignores the frameRate value set. I've only been using the createFromAseprite method, so this might be unique to that.

Reproduction

See playground link for reproduction of issue: https://phaser.io/sandbox/XSzcWL4a

I've purposely set the frameRate to 4, to make the issue more obvious to see.

When using Phaser 3.70 and below, frameRate works as expected.
When changing the Phaser version to 3.80+ the frameRate is ignored.

@photonstorm
Copy link
Collaborator

This only happens with Aseprite animations, as they override everything else. The change was made and documented in 3.80 - so this needs checking to see if altering it would have even more unintended side effects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants