I had thought I’d read that 1.7 and 2.6 projects are compatible, and did a bunch of work in 2.6 that I’m trying to get into 1.7 to do a build.
When I open the 2.6 project with 1.7, it imports for quite a while, then crashes, every time. I suspected that the problem had to do with the player setting for mono 1.1/2.1, so I tried creating a new project in 1.7 and updating from the 2.6 project on my asset server. This sort of worked, but a bunch of clips ended up missing in my animations?
Am I trying to do something that isn’t supposed to work?
Try to select all your project stuff and make a package. Then import it onto your Unity iPhone 1.7.
See if that could help.
From my experience, they are VERY compatible with each other…
Although Unity 2.6 and Unity iPhone 1.7 projects might be compatible in some cases, they are not actively intended to be. Unity iPhone is currently based on an earlier version of Unity and generally, different major versions do not produce compatible projects. This will be addressed in Unity 3.0 when the desktop and iPhone versions will be aligned.
Ah ha! I found it:
“Unity 2.6.1
Unity 2.6.1 contains a new webplayer plugin that is compatible with Mac OSX 10.6 Safari when running in 64-bit mode. Additionally a number of improvements and bug fixes were implemented to smooth out some of the issues experienced by Unity (free) license holders. Additionally, Unity 2.6.1 projects are now compatible with Unity iPhone 1.5.1 projects.”
http://unity3d.com/unity/whats-new/unity-2.6
So what happened? Did it really work with 1.5? I’m a bit peeved, having found myself in a really awkward position because of this not working as advertised.
I’ll try the package export trick, though I think that ends up being the same as downloading from the server. Will report back.
This sucks.
Are you sure about that, because it seemed there was some work done specifically to make Unity and Unity iPhone be able to share projects. I’ve had no problem loading any projects from Unity 2.6 into Unity iPhone 1.6 (haven’t used 1.7 yet since it seemed like it was mostly for iPad support).
–Eric