Hello Kirupa!
While making a flash game, I’m encoutering something pretty weird. My framerate is set to 60 and I have a function that listens to enterFrame events and calls getTimer() to calculate the time between steps. That usually works nicely, however when I run the swf in flash player 10.3 or 11 standalones, the time delta is detected for many steps as being ‘0’ because getTimer() returns exactly the same thing as on the previous step. The flash movie as such doesn’t skip frames (except it looks bad since everything moves according to the time delta) and the framerate is 60 as it should (EDIT: Not actually true, 0 ms frames are skipped). It doesn’t even happen every time. Sometimes I run it with the aforementionned players and it’s just fine, apparently for no reason. I have tried the debug and release players and the problem happens with both.
For now this isn’t a huge problem. I’m targeting flash player 10.0 and it works well with that standalone player, as it does with 10.1. Not targeting 10.3 might be part of the problem I guess, but I have no idea really. At any rate, I was wondering if anyone else encountered that problem before, and hopefully would know the cause. I have found nothing about it on the web so far.
Technical info: I’m using flashDevelop 3.3.2 and the Flex 4.1 open source sdk
EDIT: It would seem it’s not a getTimer problem. The time delta between frames is reported correctly but faulty frames do last 0ms.
Thanks for any help!