CODEWITHSUNDEEP
javascripthtmlfirefoxcreatejseaseljs
Mark Dolbyrev
Mark Dolbyrev

Reputation: 1997

CreateJS: poor/strange framerate in Firefox

I'm at the early stage of building my own game framework, based on CreateJS (especially on the feature of exporting everything from Flash IDE). And found out that framerate of CreateJS (EaselJS) is much worse in Firefox than in Chrome/IE.

Also, it seems that the framerate of app (which might be changed using Ticker.setFPS) doens't matter. It looks like Firefox has some problems with rendering (I've tried to use 60fps and 30fps, and in both cases there were problems, it looks like FF doesn't have any stable time/logic of rendering).

I've tried to play with Ticker.timingMode (set it to Ticker.RAF_SYNCHED), but it didn't help either.

And also, I've found a lot of similar topics/questions in the Internet, and no any clear answer.

So, I was wondering, if there is any way to improve framerate/rendering in FF or we should work with it as it is now?

P.S.: It looks like the problem, probably, partially might be on the CreateJS side, because I've found few nice HTML5 games (as I know they don't use CreateJS) with smooth and nice animations in FF. Here an example: https://www.netent.com/games/slots/dazzle-me/

Upvotes: 0

Views: 632

Answers (1)

Lanny
Lanny

Reputation: 11294

EaselJS just facilitates Canvas drawing operations and updates. I have built a number of applications and games without FireFox-specific performance issues using the CreateJS framework, so while there might be something that is happening through CreateJS causing the issue, it is more likely related to the content and how CreateJS is used.

Different browsers have different issues and performance differences, including how they handle vectors, large images on the GPU, etc. Without seeing code or an example, it is hard to pinpoint where the performance is going.

  1. What have you tried so far to isolate the performance?
  2. Do you have a lot of large images, text, or vector content?
  3. Are you using filters or Shadows?
  4. How are you determining that the framerate is not working? RAF_SYNCHED attempts to normalize the computer's RAF framerate (usually about 60 fps, but dependent on lots of things).
  5. Do you have a lot of children (like particles) going on?
  6. Are you checking mouse position or hitTesting often?

If you can provide more info, code samples, working demos, etc you can likely get a better diagnosis of what is happpening.

Upvotes: 2

Related Questions