—
I know your getting that reference from my post, but I think I need to clarify that. What I said was
adding any non needed behaviours will slow down your performance. As an example even PIN when NOT PINNED to anything will still takes it's toll on performance. In my test on an iPod Touch 4g; I could have 500+ objects render on the screen(no behaviours or code) and maintain 30fps, however when adding PIN even when not PINNED reduced the count to 70(with only PIN).
I did not say PIN was slow, what I meant to say was that ALL behaviours have a cost. So make sure the minimum number of objects use any behaviours at all that you can get away with.
delgado
You already posted in the thread. Just becareful. Get the lowest end device that you want to run on. Then make that your only test device for performance checking. Don't even really use a PC unless you need PC compatibility.
If you need to use angle() and or any trig functions. Try to do it as little as possible. calculating angle() and lerp(), unlerp() often will slow everything down.