I’ve submitted a bug for this with case ID 374219, but I wanted to put it out here in the public to see if anyone else had ideas because I am at a complete loss.
When I was working on my project in Unity iPhone 1.7, any Unity GUI elements I had displayed and function just fine. Upon switching to Unity 3, all Unity GUI elements are hidden when running on an iPhone or iPad.
I have a simple scrolling text box with a custom skin. The text displays just fine inside the editor, but when dropped to a device it never shows up. I’ve not seen any other reports of this behavior on the forums, which seems odd to me, but I don’t think I’m doing anything incorrectly. The code is exceedingly simple, and all of it worked just fine in v1.7 on both iPad and iPhone.
I even created a completely new scene with only the script in it and using the default skins. Nothing displayed on the device, and nothing crashed. If my implementation were incorrect, it shouldn’t work in the editor or standalone player either. Are there some lesser known limitations to using UnityGUI on an iOS device?
I’m not sure I understand. These aren’t GUI elements I’m laying out in the scene. These are components generated in the onGUI handler of a controller script. One of the components is simply a label displaying text. It also seems like it shouldn’t work in the editor if the problem were a setting and not a bug with the iOS player.
I just recently finished a near purely ongui driven interface so I know that this aspect definitely isn’t the problem …
but I also know that textures might required to have their import settings fixed and that especially own fonts will need it cause the u3 font system is different (and unpleasently uses a functionality when dropping a new one in thats not even supported on the iphone)
all that being said: sure you don’t have an error that prevents it from running at all? that the go is still around and that the script is not cut on build for whatever reason?
Unfortunately, I’m not sure of anything at this point. Later today I will create a brand new project from scratch (rather than using the one that came over from 1.7) and see if I still run into these issues when using all the defaults. I suppose it’s possible that it’s a problem with the custom skin textures, but that seems like it should have gone away when I reverted to the defaults.
I don’t think there’s anything wonky with my code - like I said it runs just fine in standalone mode, just not on the device. I’ll post back after I’ve created a brand new U3 project and tested it.