today I updated from 5.1.x to 5.2.0f3 and it seems it’s horribly unstable, whereas 5.1.x ran very well.
For one, I get this error anytime I switch the project:
For two, Unity crashes. Often. Can happen entering Play mode. Exiting Play mode. Accessing the Asset Store. Doing nothing and just letting it run in the Background. This is insane.
For three, why is the Asset Store a Tab now? I am using the 2by3 view, so the Asset Store is only as large as the Scene, so relatively small. Too small to really use. When I maximize the tab it’s bigger, but from there I don’t see any way to get back to a productive window layout (i.e. not everything covered by the Asset Store). So the only way is to reset the layout to 2by3, but then I lose all my window setup. Am I missing something here?
CustoMac w/ Gf 760
Mac OS X.9.3
EDIT: Now it froze when trying to switch projects on the project list, didn’t even produce a bug reporter.
EDIT2: I’m pretty sure it’s crashing when loading AssetBundles and instantiating the content in the Scene. Maybe I will produce a repro project tomorrow.
Yeah, and unfortunately the DontDestroyOnload bug that crashes unity happens on builds as well, so it’s unusable to build a game.
I’m downloading 5.1 again.
Does anyone know if I’ll be able to open my 5.2 project on 5.1? I guess no =(
I can’t find where to download the 5.2 patch release, I guess it’s not available yet, we need it ASAP.
I get instability too, but reporting bugs is all any of us can do. At some point, Unity will get on top of it, ongoing job I suppose.
As always, back up when upgrading Unity so you can downgrade if it’s a pile of mouldy pants. You can try rolling back - it should sort of work, but do it on a copy to be safe, probably need to delete library and temp folder before opening in earlier version. Will take a while to rebuild but its cleaner.
Hm, I continued working today and the problems seem to be gone. I started a reproduction project to issue a bug report and I simply can’t reproduce the problem Even switching between projects is now error free.
The only thing I noticed: Using LoadLevelAdditive() the Scene indices are screwed. Is this a new thing or an old bug? In my test setup I use two scenes for testing. In the build menu I have three other scenes, index 0 to 2. The content scene that I use LoadLevelAddtive on is index 2. In both test scenes I load this scene additively.
Here’s the thing: One of the test scenes is not in the build menu list, and as a result you have to add one to load the correct scene. So, it’s not 0 to 2 anymore, but 1 to 3. Is this a known problem?
P.S. Yeah I always back up, I could roll back no problem.
EDIT: Ok, the project switching problem mentioned in the original post are back. But it doesn’t happen as often and no crashes yet.
It all depends on how you report, if it’s just a bit of text with no repro scene or its got swearing, it’ll likely just be used for accumulating stats about similar issues. Understandable with so much traffic…
I get some instability, crashes, etc [Win10] but so far its only when importing assetpackages. I haven’t lost any work because of it yet (but I save before importing stuff now, just in case it crashes).
Even switching between projects is now error free.