Well… my device is a bit of an obscure one. (It was one provided by our ISP)
It is… A Pendo Pad 4.0
The hardware specs: (as far as I know, I might have missed something!)
CPU: AllWinner A10
GPU: ARM Mali-400 MP (This GPU might be the culprit!)
RAM: 1GB (As far as I know… )
Anything else I might have missed? Also asking; I also had issues with a stencil-based effect I made, so could all of this be traced to a license error? (i.e. on the android device, it’s locking out the stencil buffer because I have Unity free, causing the objects not to show?)
depends, could be a depth buffer, could be some sort of limit you hit on device with your main project and not a basic one. I’d check the playerSetting between the two and see
Actually, I found the issue: (2961) at UnityEngine.UI.CanvasUpdateRegistry.PerformUpdate () [0x00149] in C:\BuildAgent\work\d63dfc6385190b60\Extensions\guisystem\guisystem\UI\Core\CanvasUpdateRegistry.cs:107 (2961) at UnityEngine.UI.Canvas.SendWillRenderCanvases () [0x00000] in :0 (2961) (Filename: C Line: 0) (2961) ArgumentOutOfRangeException: Argument is out of range. (2961) Parameter name: index (2961) at System.Collections.Generic.List`1 [UnityEngine.UI.ICanvas.Element].get_Item (Int32 index) [0x0000c] in /Users/builduser/buildslave/mono-runtime-and-classlibs/ build/mcs/class/corlib/System.Collections.Generic/List.cs:633
This was what showed up in logcat when I enabled the new GUI in my main menu. have NO IDEA what is causing this. Oh, and of course, the GUI didn’t show…
Well, from looking at this thread (Of which I somehow couldn’t find on my first search… ):
It appears to be caused by not including the default UI shaders…
…and after doing so, my GUI rendered!
So maybe a patch should be put in to detect if the shaders are missing, and add them in at build-time… so if some doofus (like me… ) went and blanked the list, it won’t cause issues.
I will also point out another issue I was having: for some odd reason, ReadPixels no longer works in Unity 4.6 on my android device, whereas before in a previous version, it worked correctly. What could be the problem? unlike my GUI slip-up, this weird bug shows nothing in logcat!