In one of my previous posts I’ve explained this problem.
Today I would like to say that I had the same problem with Unity 2.5.1 and that I noticed that the real issue involves the Inspector: if I have the Inspector in Debug mode or if I don’t have any Inspector at all opened all seems to work properly.
Just to be more specific: if an Inspector is visible on my view, Unity freezes several times and when the execution of the application seems to be restored, each operation I do, each button I press, etc… the window freezes again.
If I have the Inspector on Debug view or I haven’t it at all, Unity seems to work properly.
The Inspector issue is better shown in the screenshot I attached.
At last I wnato to remember that I’m using:
() MacPro1,1
() Dual-Core Intel Xeon 2.66 GHz
() 4 GB RAM
() Mac OS X 10.4.11
(*) kernel: Darwin 8.11.1
I really hope that this won’t be a Tiger OS incompatibility with Unity 2.5-2.5.1.
I really would be albe to use the new Unity version but in this conditions I couldn’t.
Just to make you know, I tried to open my project on a Unity 2.5.1 demo version on a Mac Book Pro with Leopard installed on and NO FREEZES and NO CRASHES occurred.
At this time I think that there are some real big issue with Tiger and Unity 2.5 release.
Here’s the laptop specification:
MacBook Pro
Intel Core 2 Duo 2.2 GHz
RAM 4 GB
GeForce 8600M GT PCIe
VRAM 128 MB
Mac OS X 10.5.7 build 9j61
It runs with Tiger on my G5 nearly flawlessly…right-click popup menus are far too wide, but this is apparently a PPC-only bug. Other than that, no issues.
I’m also running 10.4.11 but haven’t had any freezes with 2.5 or 2.5.1. I have found that with some projects the playback in a stand alone is 2x slower than those built with 2.1. Consequently, I’m still using 2.1 for most things.
