Occlusion culling baking causing crash!

I get this error when I start baking occlusion culling data, and the editor crashes upon bake completion. I have tried several times and each time is the same. I have tried making tiny areas to test that it is not the size of my scene and the same occurs.
error : (srcData.GetChannelMask() & copyChannels) == copyChannels
UnityEditor.DockArea:OnGUI()

 

I had the same problem, 100 percent reproducible. As soon as I disabled my terrain, I was able to bake without crashing. Not a permanent solution, but at least I can continue to work on my interiors.

 

I found a better workaround; it seems that it is the Visualization panel that is triggering the crash. I can now start the occlusion bake process, then switch to another panel (so that the Occlusion/Visualisation tab is not visible... mine shares the same docked window as my project explorer, so I just switch to that). As long as that Visualization panel is not open, the bake completes and does not crash. Even after the bake completes and I save though, if I open the Occlusion/Visualization tab, the editor crashes instantly.

 

Please can you make a Bug report with a small example project and a view words of how to reproduce it?
That give the bug a bigger chance to be be fixed.

 

I have to turn off Real Time GI, Baked GI and Auto under lighting to end the errors. It's all within those settings. Like a bad joke, but unfortunately true, when it does "crash" and when one tries to send the Crash/bug report, it also freezes up, fails, and crashes. Its like the old joke "What happened to the fail safe? It failed."

 

I don't know what others have but mine is the latest with the last patch 5.2.2p4. And i still get the errors, and cant send reports.

Patch 5.2.2p4

 

Yes, did all that, and it still occurs.

 

In fact I also get this one often;

NullReferenceException: Object reference not set to an instance of an object
UnityEditorInternal.AnimationRecording.Process (UnityEditorInternal.AnimationWindowState state, UnityEditor.UndoPropertyModification[] modifications) (at C:/buildslave/unity/build/Editor/Mono/Animation/AnimationWindow/AnimationRecording.cs:46)
UnityEditorInternal.AnimationWindowState.PostprocessAnimationRecordingModifications (UnityEditor.UndoPropertyModification[] modifications) (at C:/buildslave/unity/build/Editor/Mono/Animation/AnimationWindow/AnimationWindowState.cs:1255)
UnityEditor.Undo.InvokePostprocessModifications (UnityEditor.UndoPropertyModification[] modifications) (at C:/buildslave/unity/build/artifacts/generated/common/editor/UndoBindings.gen.cs:173)

 

Yep visualization tab crashes my project to but only if i switch to it while baking in in progress

 

@fffMalzbier @karl.jones I think I forgot to get back to you on this, but I had entered a bug on this some time ago... issue 720254. It has since been closed as fixed in 5.3. I still have the issue in 5.2.3.f1. Since it is a crash it would have been nice to get it patched in the latest versions though. Yes, I have a weak workaround (don't use the visualization tab more than once), but now that the occlusion debug tool are working, if I check the Visibility Lines, correct something in the Project View, then try to check the Visibility Lines again, I crash.

 

Ok, thanks again Karl. I think I can manage until December 8th

 

using 5.3.2f1 and this error still occurs and crashing before bake completion. Please help, my game could really benefit from occlusion culling and it isnt working!
(srcData.GetChannelMask() & copyChannels) == copyChannels
UnityEditor.DockArea:OnGUI()

 

Thanks for replying, I was able to get a successful bake now, but the error message still occurs, I guess that doesnt matter though as long as the bake was successful!

 

Unity has a lot of funny bugs
Like not having auto save.
Because if you look at your shoes today, they have autosave
But this one is really weird. I did the baking twenty times and it failed but by doing this trick it did without stopping the baking
After baking, you will completely lose access to the corresponding window. Even closing and opening Unity does not solve the problem