Do you know of a reason why Unity3D 3.0.0f5 would crash at startup on my user account but not in my admin account using OSX 10.6? I tried to press the ALT key at startup but the project manager did not display. Could this be a permissions issue?
When Unity3D did not start in my User account, I logged into my Admin account and executed Unity. Unity required me to click on the "Set Permissions" button to run unity3D, which I did and to my success, Unity3D is running (admin account). I tried to repair permissions using disk utility, but I still cannot execute Unity on my user account. I could just reinstall unity (not sure if that will help though), but if this comes up in the future, I would rather a workaround. Not sure if this is a factor, but I ran Maya 2008, created some work and then wanted to import that into unity, but that is when I found out that I could not start Unity3D. Perhaps Maya caused some sort of permissions problem at load? Not sure, just trying to figure out what might have been the cause and of course the workaround would be of benefit.
Here is the Editor.log msg:
"Initialize mono Mono path[0] = '/Applications/Unity/Unity.app/Contents/Frameworks/Mono/lib/mono/2.0' Mono path[1] = '/Applications/Unity/Unity.app/Contents/Frameworks/Managed' _wapi_shm_attach: shared file [/Users/haskellf/.wapi/shared_fileshare-s01060019e3f9854a.vc.shawcable.net-Darwin-i386-28-12-0] open error * Assertion at handles.c:254, condition `_wapi_fileshare_layout != NULL' not met
Stacktrace:"
Here is the error I received in my console window:
"com.apple.launchd.peruser.501[215] ([0x0-0x4c04c].com.unity3d.UNityEditor3.x[550]) Job appears to have crashed: Abort trap"