Computing Occlusion takes forever

So I have a 1000x1000 Terrain scene, with trees and grass. And the Occlusion Culling baking is taking absolutely forever.

I started baking at around 6am this morning, and it is now 5pm, and the blue bar hasn't even reached 1/10 of the "Computing Occlusion". Not to mention, when I try to pan around the scene in the editor window, it's like almost completely frozen. It moves slightly and then freezes up, and repeats. This happens even if I disable "View Volumes".

Part of the problem may be the fact that every inch of it is a dense forest, on a really high and hilly landscape. But it still seems to take a way too big amount of time with baking the occlusion.

I will try doing this on a completely flat terrain, and removing some of the trees in areas that will never be seen by the player, but it if still takes a long while, then I'm all out of ideas.

 

What are your computer's specs? Specifically the CPU, and other info if you have it. Also, what settings are you using when baking?

 

I found out what it was. The bake settings had the same values I set for my test scene, which was only 100x100. And the values were something like "0.25" and "0.1" (not at home right now, and don't remember the settings' labels), so it was scanning very fine and small areas for the entire 1000x1000 landscape.

P.S. My CPU is an AMD FX(tm)-8350 Eight-Core (4.00GHz).

 

After you changed the values, it should bake faster. Your CPU should be fine for such tasks.

Typically, the default settings are OK for me, but since I do a lot of mobile stuff I like to keep them fine.

 

Yep, when I changed them to default, it did everything in just half a minute. I'll keep it at default for now, since I'm not making a final level at the moment, and just need more fps for testing purposes.

 

Just encountered the same issue with Unity 2020.3.26f1.
Processor is Ryzen 9 3900x, First half went with all cores, after 50%, It only uses 1 or 2 threads. Poor thread management?

 

Had this issue. Tearing hair out. Turned out to be had marked very distant "moon" static - so got included in the occlusion. Got stuck at about 1 hour. I should have noticed the blue cubes appearing around it tbh