I recently loaded up my 2D game on an iPad Mini and noticed that the framerate is reeeallly bad, like 17-20fps. This is throughout the application, on the title screen that only has a few UI buttons and also during gameplay.
I’ve been running the game on an iPhone 6S and it’s been locked at 60fps (using application.targetframerate). I realize that the Mini is much older than the iPhone 6, but I didn’t think it would perform this poorly.
Are there any settings that may need checked/unchecked that would be causing this? I’m pretty new to the profiler, but I loaded it up and I can see that the overhead is super high (screenshot attached) and may be the cause of the issue.
Tried disabling all of the UI in the scene, no change in FPS, still sitting at 17-20. Seems kind of odd that I can’t get the FPS above 20 even with an almost empty scene. I know the hardware is old, but I’ve tested other projects on this iPad and haven’t had any real performance issues until now.
Ok, wow, so after looking in Xcode more, I found out that the performance issues were being caused by a single shader. I have no idea why, not too experienced with creating shaders, but that just narrowed things down dramatically. Thanks for the suggestion, Mantas!
I’m going to look into it, but if anyone wants to take a look at the shader and help me figure out why it kills performance I wouldn’t be against it
Question is how many of the Shaders that come with Unity are optimized for mobile properly.
Since Unity 5 update there is issues with shaders in peoples projects and do not think they realise.
If you have a quick way of identifying shader performance issues, please share with us?
Not really a quick way and I’m not using a built in Unity shader. The way I found out was, the script that uses the shader is attached to the Main Camera. I disabled everything in the scene except for the Camera to see what was going on, still had performance issues… So that’s when I followed Mantas’ idea and connected it to Xcode and checked the performance. The shader that was attached to the camera appeared as a Warning in Xcode, so I disabled it and everything ran perfectly after that.
Not sure if this is the best way to go about it, but the shader did show up in Xcode so maybe that’ll help identifying the problem faster in the future.
