Visibility Lines dont show up for Occlusion Culling

Ok, thanks for checking into it. , at least now I have warmer feeling the issues have been addressed and will be resolved in 5.3. If worse comes to worse I could hold off until 5.3, it's not a huge deal, but I can't speak for anyone else having similar struggles on this thread, though.

 

Happy to hear that this is being worked on. This is currently a blocker for our game, Among the Sleep, as reverting to a pre 5.2.1p2 version is not do-able beacuse it fixed an audio issue we've been having.
We're closing in on the certification soft deadline on Xbox/PS4 and if this could be released as a quick patch we would be really happy.

What we are having problems with is that realtime lights stop working when hard shadows are enabled and occlusion data has been baked. We don't need a full fix on the whole occlusion system, just that.

 

733005

From this issue where someone is experiencing the same bug.
https://fogbugz.unity3d.com/default.asp?733005_htl3297keb4tf3m4

 

Thanks, Karl. There is a thread full of people experiencing that exact issue, with no feedback yet:

http://forum.unity3d.com/threads/un...orking-occlusion-problem.358661/#post-2339290

We too have a project that is supposed to be entering cert next month on multiple platforms, and that issue is currently a major blocker for us. We shouldn't even be taking more updates at this point, but we have no choice...please poke someone to get the fix in asap-- it was working fine up through 5.2.1p1, but broke in 5.2.1p2.

 

Add us to the list of teams that really needs this fix. We aren't about to enter cert, but we've been stuck on 5.2.0f3 because all of the builds after that made the editor unusable with P4 integration. Now that's finally fixed in 5.2.1p4, but our game is almost entirely based on shadowcasting realtime lights, so it's pitch black now. And clearing occlusion data makes it unusably slow.

So we might have to roll back to 5.2.0f3 again, and miss out on all the fixes that've been done since then, if there isn't a resolution to this issue.

I'd definitely recommend adding data from the thread LeonH posted to the FogBugz report, as the official bug doesn't include the info that turning shadows off on lights allows them to be drawn again (though this of course has other bad side effects).

 

Sweet, thanks @karl.jones!

 

@karl.jones sounds great. Thank you for the continued updates, hopefully we can finally move on with some optimization.

 

Would it be possible to push for getting it into this weeks patch release? Deadline is really close for us.

 

Looks like the server is getting slammed by people downloading 5.2.2p2; I guess I was the only one waiting for urgent fixes. But I don't see anything about a fix for the occlusion helpers, only the fix for realtime light being ignored by occlusion. Has anyone checked yet? My download will take another 45 minutes.

 

I just finished eval'ing 5.2.2p2 with a fresh reimport of the entire project. No, the visualization helpers are not fixed. Incidentally, the issue with realtime lights is not fixed either, despite the release notes saying otherwise.

 

Several comments in this thread have other bug IDs, but mine is case 730410. It's been over a month so I don't remember for sure, but I probably did not include a repro project for that one because the bug exhibits in any project.

 

Yeah, I'm aware of that system. Unfortuntely, the time constraints I am working within are not loosened by Unity's self-defeating decisions about how to prioritize bug reports.

 

Morning folks,

Looking at the release notes for UNITY 5.2.3 it looks like there's a fix for the occlusion culling pre-visualisation tools in the editor. I'm just downloading the update.

Has anyone tested this and has the occlusion results improved?

EDIT: Where are my manners, thanks @karl.jones !

 

For me the bug mentionned in this thread is fixed by 5.2.3f1.
But after testing occlusion culling it seems its efficiency is quite strange: in a test scene (a 1st person player enclosed in a corridor, with big rooms behing corners) I get a lot of objects being culled by umbra, I can check this with the visualize mode.
However it seems I still get a high batches count that does not reflect the few objects that still visible with the visualization mode... I still not get it.

EDIT: Ok, I refined my umbra settings and now the efficiency is way much better. However I still think the visualization mode does not reflect exactly what is currently being drawn.

 

Sorry to bring up this old thread, but I found an odd problem with the occlusion culling that will make a lot of people confused as to what it's doing. I submitted a bug for this back in October, but had no response (bug 739220).

https://fogbugz.unity3d.com/default.asp?739220_ab19fd86u63njok3

When you bake the culling and run the game in the editor, everything looks fine. But if you load another scene and then come back to the original baked level and hit play, the culling is not working as well (and subsequently the number of batches has gone up from before, even with the camera in exactly the same place on both tries).

Parts of rooms next door that were completely culled are now for the most part fully displayed. Also occlusion portals now do not work when the scene is reloaded, but worked great right after the bake before switching scenes. I have tested this in game on the Gear VR and the results when loading these levels in one after each other is the same as the poor result from reloading the scene into the editor that I got.

This is killing progress on my Gear VR game (that needs all the performance it can get) and is now the only reason I cannot release the game. I really need someone to look into this.

Thanks,
Scott