[F8]Dev frame rate different from browser?

A few points I've picked up along the way that all relate to this thread.

1. It's possible to get preview speed in IE, but thats because IE will happily pull in all the system resources the plugin asks for, whilst firefox doesn't seem to let anything max out. IE is better if your game isn't sharing system resources with anything else, but IE will suffer a greater speed hit when a game suddenly starts sharing a page with lots of ads.

2. Wmode does weird things to flash/firefox, especially with key input. Another bug that you might want to watch out for is that certain keys get translated from one keyboard layout to another. Try entering a @ symbol into an input field - with flash8/firefox/wmode(any)

3. Optimise your games from the beginning, both in terms of filesize and framerate. If you monitor both carefully as you go along and consider discarding/reworking anything that generates a noticable hit, you'll end up with pretty good results. Fixing this kind of stuff at the end is a nightmare.

4. Lastly, try to factor in changing framerates when you build the game, rather than hoping it'll play at the same speed on everyone's machine. Things like making the movement frame-independant, making graphical settings user or auto adjustable and maybe skipping a few of those cool particle effects if the fps drops below 25.

Just to show that it wont change in Flash9 either:
http://flexblog.faratasystems.com/?p=118

Simple conclusion - higher framerate gives more inaccurate results between browsers, computers, other programs running, and all reasons you can think of.

And while not exactly into the subject, I still wish to link to bit-101 too:
http://www.bit-101.com/blog/?p=910
I too like to use enterframe events instead of timers :)

Sorry man, but I have to correct a couple inaccuracies:

Quote:

---

Originally Posted by VENGEANCE MX

Here's a scale of framerates:
11 fps - consistent speed on PCs and Macs
12 fps - half speed that eyes normally see motion at; basically double-framed professional animation, also default framerate in Flash for this reason
16 fps - speed at which eye can perceive things as a constant motion rather than a series of separate frames; minimum acceptable speed for a game to play at
21 fps - consistent speed on PCs and Macs
24 fps - speed at which eyes normally see motion at; used in professional animation and projection cinema, best if you want to show organic movement fluidly
25fps - PAL video broadcast rate
30fps - NTSC video broadcast rate
31 fps - smooth, consistent speed on PCs and Macs; used in the vast majority of Flash games, and also about the highest speed you can reasonably expect the Flash Player to keep up
50 fps - framerate of PAL television; (Broadcasts use up 2 frames to form one image, so then a PAL television broadcast is actually 25fps); Console video games don't need to combine 2 frames, so they are capable of using the full available frame rate (50fps) if optimized properly.
60 fps - framerate of NTSC television; (Broadcasts use up 2 frames to form one image, so then a PAL television broadcast is actually 30fps); Console video games don't need to combine 2 frames, so they are capable of using the full available frame rate (60fps) if optimized properly.[/B]
120 fps - maximum framerate in Flash, only usually used in speed experiments

---

I just didn't want anyone to confuse what a television is capable of displaying, versus what you actually get from a NTSC or PAL broadcast. Lucky for us, video games don't have to interlace two frames together.

Ah yeah, forgot about interlacing. Silly me. :)