As always on Friday I was looking forward to the new beta. I got my coffee and started to read through the release notes. But they are broken. They only contained 20 lines. Oh. They are not broken I suddenly realized. It looks like Unity is prepping for a final 5.2 release and only puts in very few things now.
I am a bit in wonder: Are you really in that state already? Every beta after b3 crashes constantly. b5 is still unusable. I reported several different crash bugs and none have been addressed so far. Maybe they will in the next betas to make it in time but if it stays like this I am kinda worried.
It crashes when I put the mouse near the toolbar near the top (as is listed as a known issue). Builds on my Mac crash immediately on start-up. My meshes aren’t displaying at all, using the same code that displayed meshes fine on 5.1.
And who knows what else causes Unity to crash, seems to crash randomly if I type things in input fields for example. And randomly just about any other time.
Not to mention half the time my inspector window gets replaced with the Connect window and I can’t change it without restarting Unity…
Can you please share your bug numbers? We’re trying to be regular on shipping builds during beta to get changes out regularly. We aren’t aiming to wait for fixes until we start finalizing.
Um… what about the other bugs like Image fill (714926) and sprite removal when gameobject toggled active (don’t have that # handy)? Those are not mentioned in the B5 release notes but someone confirmed it was going to be fixed but not when. Does that mean they will not be in 5.2 final?
Every time I download a new beta I find at and report a few bugs, seems way too early to be pushing final.
And, of course: once 5.2 is out, we will be shipping weekly patches for it, just as we’ve done for 4.6, 5.0, and 5.1 before it. So if something doesn’t make the very first 5.2 release, you may still see it appear the week after.
You’re looking at it too deeply. The reason for reduced number of changesets compared to other betas is because it’s end of July/start of August - many many people are on vacation.
Backwards compatibility related to how geometry is submitted to the Canvas system is still not functional in Beta 5.
Here is a simple Repro Case 716597 showing one of the issues I am running into.
Ideally, my users should be able to use TextMesh Pro in Unity 5.2 and have everything work.
Obviously I am planning on switching over to using the Mesh Class instead of UiVertex and .SetVertices. The previous API implementation should work as it did in 5.1.
I’m having the same issue (716761) of the editor crashing when going into play mode. Unfortunately my bug report probably won’t be that useful because I couldn’t attach my project.
One small note: I can enter play mode if the initial scene is very simple. If that scene loads a more complicated scene, the game plays correctly. The editor crashes if I just try to play the complicated scene directly.
I am not aware currently that one of the 4 I posted is ProBuilder related. There was one (709829, 709832, 709844) which I solved by a ProBuilder update. Since tons of users use ProBuilder I am not sure it’s a good strategy to let it slip through with that explanation but it’s your call.
715005 can be mitigated by using less dialog options in adventure creator (must be looked into though, but not a ship-stopper)
713630 happens still, workaround is to change quality settings, save scene, restart Unity, otherwise it crashes
714983 is a duplicate to 713630 and can be closed
715050 is still happening in b5, I just attached new crash reports, for me there is no mitigation so far and therefore would be a stopper for me
I actually intended to list this one that also still happens in b5 but since it also happens in b3 so it is probably no stopper for Unity, just for me and I really really hope you do find a solution:
713310 (Open) Switch scene while in playmode crashed editor, mitigation is to not switch scenes in playmode, so much for testing the game
Thanks for all your efforts Unity. Really appreciated. Hope you find our reports helpful and can get some of these resolved after vacation period and have an awesome 5.2 release! Looking forward to an early 5.3 Beta cycle
I was making the call based on crash stacks I saw in the reported bugs. They still resembled the previous stacks from Probuilder, so I was making the connection that they were. We’re still looking into it though.
I went through all the bug reports mentioned in this post and I can tell you more than half of them are already fixed and will be available in the next build or the build after that. The rest of them we have reproduced and are still in the process of being fixed.
The only two cases we still have to get a repro on are 713310 and 715005, which are from the same user on the same project, but potentially different issues. We’re working on those and I will update this as soon as we have more to say.
Thanks to all that contributed to this post so far, and if there are any other crashes we might not be aware of, keep posting them. We want to ensure that Unity 5.2 is as stable as it can possibly get.
