I wanted to take a minute and pass out some praise for Unity 5.5. It is my favorite version of Unity so far. The new Graphics.DrawMeshInstanced method is awesome.
In my game, I am getting massive reductions in draw calls and massive framerate gains using Graphics.DrawMeshInstanced. This is a fantastic leap forward compared to the automatic instancing in Untiy 5.4 that often failed to instance effectively enough. With Unity 5.5, I am able to force it to group 500 items into a single draw call. This is fantastic. It opens the door to massively scaling the number of objects on screen while maintaining high frame rates.
I also really like the object highlighting in design view in the editor. It is a subtle yet very welcomed improvement.
Anyway, I just wanted to heap some praise on Unity 5.5 today. It is a fantastic release. Thank you Unity team!
I’ve read this a few times in the 5.5 beta forum. For whatever reason, this seems to be a rather common 5.5 issue and it seems it often can be fixed by deleting/renaming the “Library” folder.
Close Unity, rename the “Library” folder in your project to “Library_DeleteMe” and start Unity again. The next start might take a while, because Unity re-imports all assets and re-creates the Library folder.
Doing this fixed several issues in my project (HoloLens GUID issues (never used HoloLens though), broken shaders and pink materials).
Aside from finding out it’s now essential to have a reflection probe in the scene or I get garbage noise on everything, I haven’t had any new issues crop up. Played with the look dev tool a bit since I spent all of monday making a model viewer. It probably needs another pass on usability, but otherwise it’s pretty interesting.
I’ve found and reported a bug in the particle system sub emitter functionality, but otherwise it’s been great so far. I love the new post effects stack! And I haven’t even touched the new features on the particle system yet, which was my main reason to upgrade. So far I’m really happy with 5.5 as well! Great job everyone who worked on getting this into our hands, thanks a lot!
I haven’t touched the things that convinced me upgrade to 5.4…
I feel pretty spoiled these last few updates, since stuff that happens to be specifically relevant to me is getting added faster than I’m getting to try it out.
The only thing I’m really interested in is the new splash screen since it’s just less… gaudy than the old one, but I’m mid-development right now so makes farting noises with armpit
By the way, less than 24 hours later I’ve heard the bug has been fixed, but it might take a bit for the fix to go through QA and make it into a patch release. I’m still very impressed how quickly it got sorted out!
I jumped from Unity 4 to the 5.5 beta as I am nearing completing a mobile game, so will need to be on 5 at some point for iOS compatibility, so best to do it before launch, and might as well go to the newest possible.
It is a mixed bag for me, and still prefer Unity 4. However, I really do like the new splash screen. That is a massive improvement. Perhaps even a little too generous, but welcome.
For balance (well, not really balance), the things I don’t like include:
Can no longer set Default texture format. Makes for more work and increase chances of errors on multiple mobile formats.
My GLSL shaders do not work at all.
Legacy particle system is due to be depreciated. The new system does not have the Systematic option, and I dislike the interface (I dislike all the non-standard interfaces that have appeared in Unity, but this one replaces something that worked well and was standard).
Scene management changing but not being documented clearly (was stuck for ages because didn’t find anywhere that said “using UnityEngine.SceneManagement;” was required).
Documentation out of date for things that have changed slightly for no apparent reason, but don’t work without changing. This was the worst for updating projects compared to Unity 2 to Unity 3 and Unity 3 to Unity 4. It was days rather than minutes.
EDIT: Some more features I forgot
Unity Remote 3 no longer supported, so no connecting by wifi, which is often more convenient.
Reduced options. One that I noticed missing was the Mipmap Linear Space setting.
That was more about Unity 5 rather than 5.5 as I jumped. I’d tried updating to 5 a few times before and returned to 4 as soon as possible. Unity 5 is a very nice piece of software, it just isn’t as good as Unity 4. Unity 5 is about what I have lost, not what I have gained.
I have been searching. I can find something for setting the default texture format. I want something for me to set each texture individually. I use a variety of formats in each project. Some can be compressed, some can be 16 bit, some need more. Some need transparency, some do not.
Even if I find a solution, it will not be as easy as using an option on the texture. Just as it used to be and Unity decided to take away. Apparently it is to stop people selecting formats that could be incompatible with a platform, or too big for that platform. So they took away control for those who know what they are doing.
Unity are chasing AAA at one end, and beginners at the other end. They seem to be forgetting the competent indie who are their core customers.
I have also been impressed with a bug I reported ages ago, not in that it was fixed quickly (I’m not sure) but in that they followed it up with me twice when unable to reproduce it. I’d have expected them to drop it when they couldn’t reproduce it from the description or from the repro case I sent. They got in contact and I had another look, and my own repro case didn’t work any more so I said I’d make another. When I hadn’t got back on that in a few weeks they got in contact again to ask how it was going. (And now I feel a little bad, actually, since I’ve a sneaky feeling that’s sitting in my growing pile of to-be-responded emails…)
Point being, though, the people on the other end definitely get my thumbs up!
I reported a bug when Unity 5.0 was early beta (alpha really). The bug was fixed in another beta update… and Unity just sent me an email yesterday saying the bug was fixed. Guess they’re finally making their way through the list.
