Didn’t think it would be this big a deal, but it turns out the upgrade will need us to put in a week or so in getting things back to normal. In 1.0.3 our title compiled w/ 0 errors or warnings.
1,) Since static batching was removed from the basic license anything animated needed to be set w/o the basic box checked. Seems to work in 80% of the cases. No idea what to do with the rest,
2.) GUI textures are now completely out of whack. We are not yet sure why.
3.) The Xcode project is a complete mess. Looks like a monkey went to work and tore stuff from the appropriate dirs - i.e. frameworks all over the place.
4.) animations of scaled objects will now return to location 0, 0, 0 and render without animation ignoring the scale factor. For example a cog wheel animation will now ignore the assigned transform and just render the image in full scale sans animation in the middle of the screen.
I have read the comments of RTFM and so on and how this is all the programmer’s fault. OK. Still any help would be good ; )
Can you share some more information about this? For issue 1, you say that your approach works in 80% of cases - what goes wrong in the 20% where it doesn’t work? Are the GUITextures misaligned, rendering in the wrong colours, invisible… ? As for the animations, do the settings appear to be correct, but still work incorrectly? Is the animation problem fixed if you reconstruct the object or is it occurring regardless of what you do?
I think it’s probably worth trying iphonefreak’s suggestion about Xcode first, although I don’t really know if it could be causing any of the other problems.
The Xcode installation is fine. It seems the 1.5 release was put together somewhat hastily as far as the trampoline project is concerned and the frameworks were not put in the correct location (i.e. the frameworks directory). Apparently they were pulled out when testing under Snow Leopard where all these frameworks display in red (i.e. missing) and then someone forgot to put them back.
One layer of issues stems from an incompatibility with Snow Leopard. We hadn’t really thought this would be a problem, since developers have had access to Snow Leopard for over a year now. Under Snow Leopard the xcode project does not compile - frameworks cannot be found. This is also the cause for 80% of GUI texture issues.
Under Leopard these things are out of whack:
font material
Due to the removal of the static designation in the indie version, prefabs that still have this checked are invisible
imported animations and scaling/positioning of the latter are all broken
coded animations (i.e. rotations) are broken
compiles are now about 5% larger in size
Again - this is a partial list. We only had 2 days to go through level by level and test everything for a list of these newly introduced defects. Can’t say that I am thrilled with the quality control here. Pulling features, etc. At the very least when introducing this many problems, a checklist should have been provided listing everything that will break and some suggested workarounds. Had we had such a list before, we probably wouldn’t have bothered with the upgrade. Having such a list now would help addressing these problems in a systematic way.
I understand the documentation has improved, but this is a high price to pay.
For best experience with Unity iPhone 1.5 I can advise to use OS 10.5 and SDK 3.0.
We’re aware of some unexpected behavior under OS 10.6 and will improve user experience and compatibility with Snow Leopard with the next Unity iPhone release.
If you absolutely need to use OS 10.6, please install complete package of latest Apple’s dev tools to a separate directory (and use those for development) as this is the most reliable way to make things work. Also users with clean (not upgrade) OS 10.6 installs report far less issues with Unity iPhone 1.5.
If you have noticed any bugs, please use bugreporter to log them. That would be the most reliable approach to have them fixed for you.