Just downloaded and authorised the Unity Pro Beta. It wrote over my 2.6 install, then proceeded to compile scripts and bring in all the texture and gui image assets just fine. It got to the meshes and I had C4D open. It opened a dialog window asking me to shut Cinema 4D to install a plugin when it reopened. However the C4D icon just bounced and bounced in the dock for minutes without the telltale triangle indicating it opened. Right click revealed the Application was not responding and gave me the option to Force Quit. Checking Unity it also was not responding. I force quit both and tried again. Same thing, compiled scripts, had already precompiled the graphic assets and got stuck at meshes. Restarted the machine and again same sequence. If C4D is open it tries to open a second copy of it which it too dances in the dock forever. The process never completes.
As well I opened the MonoDevelop.dmg.bz with Zipeg and then I get a MonoDevelop.dmg which when double clicked or checked with Disk Utility says there is no mountable file system. I thought maybe it needed MonoDevelop to properly install the plugin but did not know where to exactly place it so the final decision was to place with the Unity folder in Applications. Should it be elsewhere? How is the original download properly unzipped, mounted and installed?
Looking forward to a rapid resolution of this that hopefully does not involve reinstalling everything :?
I resolved the apps opening issue with a fresh install of both programs…
I still have an issue with where to and how to unzip the file. Do I just discard the .dmg?? As stated, when I unzip it it is a .dmg that will not mount as the dialog window states there is no file system to mount.
The system knows how to unpack and use .dmg files, so if the file is not corrupt, it should work with just a double click. It behaves as though it were a read only disk drive, which is the reason for the strange error message. You can copy the Unity app to any convenient place, although Applications is the most obvious. If you want to avoid writing over your existing Unity, simply rename the existing folder before you install the beta.
I…ummm…oops already wrote over 2.6 Pro thinking the beta would just toss a new app in the Unity folder. I would like to have the two installs, 2.6 and 3.0 beta as I found alot of physics settings which worked perfect require tweaking in 3.0. That is for a game already completed. It opens fine in 3.0…but the other game in development that can use all the new widgetry in 3.0 will not open. It cycles through all assets and scripts and then on recheck for unimported assets crashes. What steps do I proceed through to get back the 2.6 app? Reinstall to a different folder than the 3.0 version and authorize the same way as always?
I also get a console error on each import telling me C4D could not export and to manually export as fbx. The files seem alright but now it seems that I cannot have C4D open and have it use that. It opens a second copy of the app, does some voodoo and closes the app without ever opening it all the way. Then reports a console error on failing to import and use manual fbx export.
It would be handy to have a progress bar or something to ;let you know how long the Umbra is going to need to finish its processes. I waited and hour or more last nite for a preview on an arena of a couple thousand polys with five or six other static objects of a couple hundred polys each.
Followed instructions for the MonoDervelop install and debug routines…as far as I could…heh… However the MonoDevelop.dmg would not open and it has no mountable file system. OS X Disk Utility states “Verify volume failed: Unrecognised File System”.
To get a working 2.6 back, you should download the installer again and select an install location other than the Applications folder. Then, rename the Unity folder and drag it into Applications. The issue with the .dmg file sounds as though the file is corrupt. It might be worth downloading the file again.