Hi Joel, Check the location of the Footprint trait as per an earlier email. From memory, Footprint creates a bounding box to include the entire movement history and should be specified outside of any rotation trait,
Cheers, Brent. *********** REPLY SEPARATOR *********** On 11/11/2007 at 10:21 PM Joel Uckelman wrote: Thus spake "Kevin Coombs": > Hi, Joel, > I hate to be a pest, but have you been able to make any progress towards tack > ling this issue? > Thanks. > Kevin I've made some progress on this now: If you load the Glory III module and try to rotate a token, you can *see* the dramatic increase in memory usage in a profiler. The superficial cause is that the bounding boxes of your tokens are completely bogus---which is causing huge images to be created to receive the rotation result---but I haven't been able to determine why yet. (For comparison, I haven't been able to get this to happen with any other module.) -- J. ____________________________________________________________ Brent Easton Analyst/Programmer University of Western Sydney Email: [EMAIL PROTECTED] [Non-text portions of this message have been removed]
