Hi Troy, The way Macromedia has explained this is that Director projectors don't actually hog the cpu, they just eat up unused cycles. If I recall correctly, this is aimed to handle animation. Other types of processing can afford to wait--being off by a tenth of a second may not really matter--but a tenth of a second in an animation produces a jerk in the motion.
When another application requests cycles, Director supposedly plays nicely. Regards, Daniel > > Maybe I'm the only one seeing this one - idle projectors in OSX > consuming huge CPU resources for no apparent reason. I notice on my > Powerbook that the CPU fan comes on whenever there is a projector > running, or even a shockwave in the browser - my own, or anyone else's. > CPU averages 80% utilization when the projector is in the background > looping on a frame with no scripts (other than go to the frame.) > > If this doesn't qualify as an "issue" to be reported, does anyone see > similar results, or have found a way to eliminate the CPU hogging? [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
