Hey Guys Framerates on a mac using flexbuilder are not to be trusted! the reason for this is simple - flexbuilder appears to gradually consume more resources the longer it runs. I have a theory that the drain exists in whatever goes on inside the debugger, but it's impossible to know for sure. when you run a swf from flex, a lot of monitoring is going on from the flex side - progress of methods are tracked etc - this drain seems to be apparent even when you run an application rather than debugging it. If you create a release build of an swf and then run it in a browser, you will always see a marked framerate increase. Conversly, cs3 doesn't appear to suffer from these problems.
The gradual decrease of framerates over time is still a mystery to me though. I've seen framerates drop by as much as 50% over the course of a day, only to be re-estabilshed with a restart. Which is the other strange thing - simply restarting flexbuilder does not reset expected framerates. whatever is causing the slowdown requires a complete reboot to clear. hth Rob On Sat, Nov 22, 2008 at 6:55 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>wrote: > > Yes, I'm also on Mac (fairly fresh MPB) however the fps never exceeds > 9-10. I put 3D stuff within some nested centered canvas/boxes - so > this could be the reason of such a significant drop in fps? > > > On Fri, Nov 21, 2008 at 9:22 PM, Jensa <[EMAIL PROTECTED]> wrote: > > > > No. MXML is converted to Actionscript when compiled, so MXML in itself > > hasn't anything to do with it. The only thing that could cause > > slowdowns was if something in the Flex framework was triggered > > (components being positioned/scaled or something similar). > > > > One question - are you also on a Mac? > > > > J > -- Rob Bateman Flash Development & Consultancy [EMAIL PROTECTED] www.infiniteturtles.co.uk www.away3d.com
