Hi - I’m trying to profile the OSX build of a simple game I’ve written. I build the game with ‘development’ checked but whenever I open the Profiler window I get constant beachballs and end up having to force quit Unity. Is there something simple I’m doing wrong or is the profiler a bit barfed ?
Thanks.
I have a similar problem. With Unity 4.0 and 4.1.
However I’m not seeing any spinning pinwheels. CPU and memory load are far less than 100%. Unity app itself is unresponsive when profiler window is open and set to “Record”. I’m using mid 2010 MacBook Pro with 10.8.3 installed. I haven’t noticed any problems before updating to 10.8.3 from 10.8.2. On a newer MacBooks this problem doesn’t occur, so I blame Apple and their graphics card drivers.
Unfortunately downgrading OS is not an option for me.
Does anyone from Unity have any input to this problem ? Not being able to profile is not good 8(