I’ve just release a game on Steam with Unity 4.6.2f1, drawcalls where acceptable.
I’m working on the mobile version of this game.
So I upgraded to the latest version of Unity 4.6 : Unity 4.6.4p2 and drawcalls exploded.
I show you a representative part of my problem :
I have 1 Camera, 1 Canvas
I Render only that :
My Hierarchy :
Cases contains only that :
Leds contains only that :
Unity 4.6.2f1 : 4 Drawcalls
Unity 4.6.4p2 : 40 Drawcalls
If I set led’s Source Image to None, drawcalls go down to 4 but I have glitch (which I don’t have in 4.6.2f1)
There are problems with overlapped images on the latest version.
With the new version, I have drawcall problem everywhere in the game now, but i need the new version for the iOS build (il2cpp).
On my example I have shown you, I’ll change the background image to avoid Case objects.
Do you have tips, advices or clear explanations why my drawcalls goes up in 2 months updates?
I’d log that as a bug using the Unity bug reporter in the editor. There weren’t any significant changes in the UI source for this, so it must be an editor regression issue. Thoughts @phil-Unity@Aras
Just one after thought. Might the above control not be easier to update to use a single image for the Cells/cases (tiled image maybe) with a background slider (set in to stepped mode) for the LED’s to achieve the same effect.
Just confirmed this myself on 4.6.4p4. UI batching completely broken. We were stuck using 4.6.3f1 for months because InputField was broken on Android ever since until 4.6.4p4, and now that we were finally able to update, there’s this blocker.
I guess it’s back to 4.6.3f1 again. I hope they’d fix this soon, but the way it’s been with UI fixes and 4.6 lately, I’m not expecting much. I reported a bug from 4.6.4, but since this doesn’t happen in Unity 5, I guess the reports are pretty much ignored.
Reported a bug too. Not fixed in 4.6.5f1, but I guess it’s basically the same as 4.6.4p4.
There’s now been a blocker level UI bug in every patch/release since 4.6.3 (InputField not working on Android, disabled UI items blocking raycasts, UI image draw calls not batching). I really hope they’re working on this, since I got a deadline coming up and I’m getting a bit worried with the way things have been going lately.
So the invisible UI objects will be fixed (at least for 5.x, hopefully 4.6.x too). How about the badly broken UI batching? Can you poke the relevant folks, @superpig ?
Has anyone confirmed whether the issue is or isn’t present in the latest 5.1 beta release? It’d help me to know whether this is a “already fixed but needs backporting” vs a “nobody has fixed it anywhere yet” situation.
Here’s some screenshots from 5.1.0b6. I just have a panel with gridlayout, containing panels with an image on top. I’ve duplicated the inner panel multiple times in these screenshots.
