Hmmm, a framework for that could be pretty interesting. Have the ability to specify certain sections of code/certain components as optional based on a current performance metric.
As far as metering, could be as simple as listening to ENTER_FRAME and taking timestamps to determine how long each frame is taking to render/process. Then setting state on an application performance model that views could bind to and tone themselves down appropriately... On Thu, Jul 31, 2008 at 8:58 PM, Josh McDonald <[EMAIL PROTECTED]> wrote: > Hey guys, > > I'm probably going to be embarking on a project soon that can be very > graphically (and hence processor) intensive, and I'd like to know if there's > anything out there to help me determine performance in order to tweak things > to have less detail if it's going slowly, and more if it's not. Or even to > switch from the PPV3D to a simpler 2d scaling based approach on slower > systems. Any ideas? > > -Josh > > -- > "Therefore, send not to know For whom the bell tolls. It tolls for thee." > > :: Josh 'G-Funk' McDonald > :: 0437 221 380 :: [EMAIL PROTECTED] > >
