Occlusion Culling in Unity 5.1

Yesterday I tried to update my project from Unity 5.0.2 to 5.1 but I faced a crash when trying to bake Occlusion Culling at the end of the bake process.

I tried to manually delete the Library folder from my project, rebaked Occlusion Culling but it didn't changed anything: Unity crashes.
With Unity 5.0.1 and 5.0.2 it's fine (there's just a bug with showing visibility lines and occlusion portals in the scene view).

Does anyone have the same problem with Unity 5.1 ?

 

If it's reproducible file a bug report.

 

Same here, tried to bake it 4 times without success(a few pixels remains, it's thinking for another 10-15 minutes then bamm, crash). It worked with 5.0.2.

 

Ok, I'm not sure if it makes a difference or not but on my side I'm on Win7 64bit and using 64bit edition of Unity.

 

5.1 crash here when i try to access the Occlusion Panel. Win7/Unity 64bit.

 

I could track it down to the usage of SpeedTrees, #705299.

Edit:
To nail it down further, this only happens when there is baked data.

 

Have the same problem, it crashes when I click the occlusion tab. But then I disable my unity terrain with SpeedTrees on it does not crash.

 

Same problem here.
Filing bug report.

 

Same issue. Disabling terrain, clearing occlusion, enabling terrain, re-baking ends in editor crash as well. Running latest patch 5.1.1p2

 

Still the same with 5.1.1p4... Unfortunately.
This is an issue clearly related to SpeedTree in the terrain itself. If they are placed as GameObject there's no crash.

EDIT: As a temp fix to avoid crash I uncheck "Tree & Detail Objects" Draw checkbox in terrain settings, bake my Occlusion, then I recheck it after that.

But however Occlusion Culling is not working anymore efficiently (like in 5.0.2)...
Before I had larger Occlusion data, now it bakes occlusion blazingly fast with the same settings but occlusion data is only 48KB (versus more than 1MB in 5.0.2) and it's totally inefficient.
Tried to play with settings, but didn't found good values.

Unity 5.1 onwards is definitely a no go for me.

 

Yea ... i still have a lot of trouble on 5.1

 

Thanks. That worked for me.

Going back to the occlusion culling window when the trees are on causes a crash again, but I'll take what I can get.

 

And what about Occlusion Culling efficiency ?
Is it working as intended for you ?

 

Unity 5.1.2 released, and Unity still crashes miserably when computing occlusion for a scene with SpeedTrees.

Sometimes I really, really don't understand Unity's priorities. This is a very serious regression error. Projects have been submitted which provide repeatability of the error as soon as 5.1 appeared. Still Unity does nothing about it, despite several patch updates and despite the release of both 5.1.1 and 5.1.2?

I really don't get it. Fix your regression errors. Get your act together, Unity.

 

Agreed, Occlusion Culling is a must have for some games.

On my side I'd like to know a bit more what they have changed so that it became inefficient up to that point. At least in my case...

Did anyone else noticed inefficiency with the new Occlusion Culling ?

EDIT: There's also that bug that make visibility lines to not show up, which makes kind of hard to refine the settings.

 

The SpeedTree issue will be fixed in 5.2

 

Cool

Would be great to get someone from UT talking about the changes in Occlusion Culling algorithm.
As I mentionned several times I'm unable to get it work properly till 5.1 (with the workaround to prevent the crash of course).

That's mainly the reason I stick with 5.0.2 for now.

 

Had no answer...
It's not documented anywhere, please someone answer my question above.

 

Well I was totally wrong: occlusion culling behaves exactly as before (except the crash with speedtrees enabled in terrain of course).
In fact to do the workaround (disabling trees in terrain) I duplicated my terrain but I forgot to set it as static... Hence it was not taken in account by Umbra.

So I'm moving my project to 5.1.2 tonight!

 

I don't know if it's relevant but in a scene with Speedtrees when I use occlusion portals I run out of memory and have to cut the power to my machine.

It doesn't crash unless I have an occulusion portal over the Speedtree.