Well, peachy. Got home, got it out of the box, did its mumbo jumbo, downloaded Unity, registered it, crashes every time I try to start it, so then I tried to do the good old fassion 10.4.9 Update Combined (Intel), and guess what, "You cannot install Mac OS X Update Combined (Intel) on this volume. This volume does not meet the requirements for this update.
Second guess, Unity won’t run on the machine.
MayDay! 
I feel your pain. Here’s hoping for a quick fix from OTEE – my Santa Rosa MPB will arrive next week and I was really hoping to move over to it right away.
Good luck!
Not a single 10.4.9 update from apple works on it, what ever version of 10.4.9 that comes on the beast is all we get. I have told the crash reporter to send in the report to OTEE, this is the primary and only reason why I got the machine
I’ll take the machine in with me to work tomorrow in hopes that maybe they need more info and can do a fast patch or something for me to try.
Cest La Vie
This is a new build of 10.4.9 to work on the new Santa Rosa hardware, etc., so it’s no surprise that older updaters won’t work. Given some of the issues we’ve been having with Unity, there’s a good chance this is a video driver issue related to the new video card, but of course that is speculation. I’m sure OTEE will be all over it as soon as they can.
Hang in there!
Yea, one thing OTEE crew is good at, is there job, oh and there great at everything else also! I leave for vacation the in 2 weeks and I want to take Unity on the road. I am praying that they get a hot fix done before then. I was “half” way tempted to install 10.4.8 then remembered the new hardware and decided against this dire dellusional thought of mine. I think you are right though, probably video since I see the sample FPS tutorial flash up on the screen then crash, which is odd, I don’t remember that a fresh install had any map loaded at first.
Well, I am downloading all my other cool software to it now to see what else is broke.
Try this:
This doesn’t help at the moment, but 10.4.10 will probably be released in the near future, so by then hopefully any problems can be sorted out, if it’s on the OS X end. Ideally something can be sorted out right now of course. 
–Eric
Ooof… We’ll see what we can sort out on our end, stay tuned.
I was asked to try 2 projects, since I am at work and don’t have my iMac here with a working copy of Unity, can comeone please post 2 projects for me compiled for mac. One as a basic application, don’t care what it does, spinning cube for all I care, make sure its made from the prefabs that come with Unity, second using an empty project and slap in a cube or something. This way I can give them the results of running these two. Thanks!
Edit: I just tried Unity Invaders by Eric and it worked without issue as a game.
Eric, did you create an empty project for that or did you start a new project with the built in assets?
If a standalone with graphics and gameplay works an empty one will work too.
Zum,
Here’s a Unity 1.6.2 Project folder with Standard and Pro assets, one scene, and a Unity cube in the scene facing the camera (not an external model).
It also includes the Intel standalone build.
Hope this is what you were looking for.
Thanks will try these both.
Working with support to get through this.
Starting to look like a folder/file permission issue with 10.4.9
Problem is, I create all my stuff in my user folder, so I have 100% rights to do everything in there, but for some reason, only with Unity and nothing else, the folder permissions keep getting changed when I exit Unity.
What we have done so far, is they had me hold down ALT and load unity, which bypassed the last loaded project (in a new install, that I think is the FPS example), so creating a new project empty or with assets, they get created. But I get an error on load about its ability to create some temp file or move some temp file. Where Unity is creating them, maybe Unity binary doesn’t have access to those folders or something, I don’t know.
I have no issues though downloading files into any folder unless its a locked system folder that I have to type in a password for. Still working through the possible cause, but good news is, so far I have atleast got the editor to load now with extra key presses on load.
EDIT:
OK bizzar, your test loads fine for the build, when I open a new project and load in your test with assets, the old scene from my last project doesn’t close like it is supposed to. The scene is still visible on the scene view, but, None of its assets are loaded any more, nor is the scene file in the list. So its not blanking the scene… I don’t think that can be blamed on my file permissions.
Ok, I “think” I have found a possible solution.
MacBook Pro (and possible regular iMac’s and other Macs) by default set the permissions up as follows:
On hour “HOME” folder:
Owner Permissions
You can: Read Write
Owner “You”
Access: Read Write
Group “You” (same as owner here, which appears to be the problem)
Access: Read Only
Others:
Read Only
To get rid of the constant harrassment of my machine about the security, I changed Group access to Read Write for the group with the same name as my login name which is the same as the locked owner name.
Although this does absolutely nothing for anything else, I get no more errors. On top of that, the last error I got about the Temp/temp copy goes away also. So to recap, before you launch Unity for the first time, FIX this permission for group since it is overriding the owner for Unity folders for some strange reason. Other than this, I am still doing testing, but that one Default permission is kiling everything.
I am still skeptical about this though.
Spoke to soon. Although the editor opens and I can do “some” work, its randomly crashing on me. Send in report from last crash, this time it bombed when I clicked on quit and the save box came up. Before I could click on save, it popped up the crash report box. Looks like its not stable. I’ll keep sending in reports as that crash box popps up.
Not sure if it matters, but I’m pretty sure I started that with the standard assets, though I ended up removing most or all of them by the end.
–Eric
3 more crash reports submitted as follows:
After save, clicked on Build, Build Settings, selected web player, clicked Build, Crash
After Load, clicked on a scene file and tried to open an existing scene, crash.
After Save, clicked on Build, Build Settings, crash.
I just installed Unity on my new Santa Rosa MacBook Pro 2.2. I updated the system by migrating my personal files, but no applications or files outside the user folder.
I reistalled Unity from scratch, including entering my serial number.
The FPS tutorial works fine both in the IDE and as a standalone Intel only build.
The frame rates are very high, even when playing back at the highest quality with a large window.
Sorry Zumwalt, but I wonder since you were having permission problems whether something about the way you migrated or configured your system is goofing you up.
I’ve forgotten whether you tried running Unity from a pristine new user account or not?
So Unity does not appear to be broken across the board on the new “Rosa” machines.
I experience the same crash on startup with a fresh new MacBook Pro and a fresh download of Unity. I hadn’t entered in a serial number or anything yet.
-Jon
Fresh new account, no migration.
Fresh install of Unity and then keyed it.
Crash.
I’ve gotten past the security problems, did that a while back.
I got 5 more crashes today while playing with it in different scenarios.
I click on a script to open it in textmate, soon as textmate loads and I have the script open, Unity dies, but no crash report, just closes.
Second attempt, Unity stayed open while I worked on a project for about 10 minutes then just up and crashed.
Keep working with it and see if it dies at all.