Unity 4.1 won't start (OS X 10.8.3)

Unity Engine
1

I tried to start Unity up this morning and nothing happens. The icon just bops up and down on the dock and then stops. No error dialogue appears either. I’m not sure what’s happening; it was working fine last night. I’ve also tried restarting the my Mac and reinstalling Unity.

Here’s a print out from Console.app… don’t know if any of this information is relevant.

30/03/13 11:36:52.056 AM Unity[459]: NSDocumentController Info.plist warning: The values of CFBundleTypeRole entries must be ‘Editor’, ‘Viewer’, ‘None’, or ‘Shell’.
30/03/13 11:36:52.080 AM mDNSResponder[38]: Bad service type in Andrew’s Mac mini._unityiphoneremote._tcp.local. Application protocol name must be underscore plus 1-15 characters. See http://www.dns-sd.org/ServiceTypes.html
30/03/13 11:36:52.080 AM mDNSResponder[38]: Bad service type in ._unityiphoneremote._tcp.local. Application protocol name must be underscore plus 1-15 characters. See http://www.dns-sd.org/ServiceTypes.html
30/03/13 11:36:52.080 AM mDNSResponder[38]: Bad service type in Andrew’s Mac mini._unityiphoneremote._tcp.local. Application protocol name must be underscore plus 1-15 characters. See http://www.dns-sd.org/ServiceTypes.html
30/03/13 11:36:52.860 AM com.apple.launchd.peruser.501[140]: ([0x0-0x45045].com.unity3d.UnityEditor4.x[459]) Exited with code: 1

2

Might be a corrupt scene being autoloaded - Hold down option, then click the icon, see if that starts it

3

Okay, there’s definitely something wrong with my project. None of my scenes will open. So is it just as likely that it’s an asset being referenced in my scenes (or even in the library) which are breaking it? It would be nice if Unity gave some feedback as to the culprit rather than just failing to launch.

I’ve copied over a backup project from a couple of days ago which is loading fine. I guess I’ll drop my new assets into it until something breaks. The last thing I remember doing was updating my Prime[31] tools, so I think I’ll back it all up before trying that again.

4

It’s being caused by downloading latest Prime[31] Admob plugins and updating tools.

EDIT: Fixed by moving P31StoreKit.dll from Prime31 folder to Plugins folder.