Performance differences across browsers #365
-
Hi, My game runs great (60 fps) on Chrome for Mac OS, but terribly on Safari and Firefox (< 20 fps). On Safari, it could have something to do with the fact that Safari is not respecting the "crisp: true" setting, and is rendering my game as anti-aliased. In Firefox, the game renders crisp, but it's still slow. https://tailpipe-10-24.larrystone.repl.co/ Any ideas? Or perhaps there's something in the Kaboom rendering code that is browser-specific? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
Update: I've experimented with different approaches to culling offscreen objects. Nothing seems to help in getting Mac OS Safari above 20fps. I've been able to improve Firefox to about 30fps. Meanwhile, Chrome runs beautifully. |
Beta Was this translation helpful? Give feedback.
-
I'll do some profiling and get back to you if identified the source |
Beta Was this translation helpful? Give feedback.
-
More info: I found a performance hog by profiling with Chrome. I then removed that hog and saw that it improved Safari somewhat. Then I noticed this: Safari maxes out at 30fps even when I'm in my title scene (with literally nothing happening except displaying text and waiting for a keypress.) So in short, it seems that Safari is limiting framerate out of the box, so to speak. |
Beta Was this translation helpful? Give feedback.
-
Solved: Safari throttles framerate when Mac OS is in Low Power Mode. Turn it off for maximum Kaboom. |
Beta Was this translation helpful? Give feedback.
Solved: Safari throttles framerate when Mac OS is in Low Power Mode. Turn it off for maximum Kaboom.