[BUG?] Stat Collision/collision performance on mobile device (Jan 2012 SDK)
I've been looking into the perfomance of my app & there seems to be some odd results being returned via the "stat collision" command.
When comparing the Call Counts displayed on my device, the numbers for "BSP point check", "BSP extent check" (all the stats) are 2 to 3 times higher than when running the exact same test on the mobile previewer.
I was expecting the "ms" column readings to be completely different, but not the call count. This would seem to indicate a fairly significant (& broken?) set of logic beng applied when running on the device (or a problem with the stat recording). I'm guessing it's something to do with not being able to hit the min framerate/tick required for correct operation? I've tried setting the MaxSmoothedFrameRate to 35 to see if that helps, but it wasn't any different.
Is there something I should be setting somewhere? Should the numbers be interpreted in a non-obvious way? Anyone else experienced this problem? It seems to be responsible for massive slow-downs.
Any info greatly appreciated.