As the title implies, I’m curious as to what the exact nature of this folder and its contents is. I’ve recently been transferring a few of my Unity project folders to my new iMac using an external hard drive, and the file copying process to the iMac from the external hard drive kept getting stuck when ‘preparing files to be copied’. I ended up tracking the issue to the ‘/Library/Occlusion’ folder by copying each individual file from one of the projects to a new folder on the iMac, and when it came to copying the ‘/Library/Occlusion’ folder across it became stuck while preparing to copy the file, forcing me to cancel the transfer and force quit/relaunch the finder.
I know there’s generally a ‘Don’t ever touch the Library folder or the very fabric of reality will collapse in upon itself’ rule, but I launched the copied project in Unity on the iMac without the Occlusion folder present and everything seems to run fine, which leads me to wonder what Umbra is doing with a folder filled with several million .umbracache files?
So if someone can provide a definitive answer explaining the folder’s purpose and what Umbra is planning to do with all of those .umbracache files, it’d do a great deal to satiate my curiosity and quell my concerns that I may have just been forced to remove something important from the project.
Umbra stores temporary data generated during a bake in that folder. You can safely delete it.
BTW, if you have .meta files enabled (and since Unity 4.<don’t remember> we enable them automatically but hide them by default), you can always delete the Library/ folder without any ill-effects. Basically, your source assets in combination with the .meta files are all the data Unity needs to recreate the data in the Library folder.
It claims: “All metadata for assets is stored in the Library folder. As as user, you should never have to alter the Library folder manually and attempting to do so may corrupt the project.”
Which I think is somewhat misleading these days since it’s perfectly safe (and sometimes recommended) to delete the Library folder if you have .meta files enabled.
Should this be qualified with ‘since version X.X where we introduced forced .meta files’ or similar? (just thinking that some poor 3.x user may read this and cause themselves some severe pain )
This is such a pain in the @$$… Not only is occlusion not working properly, but its now made it near impossible for me to make backup copies of my project folder without having to go through minutes upon minutes of deleting files…
I just ran into this devil of a problem. What a pain! This could definitely be managed better then it’s current design. 90k files regardless of file size take an enormous amount of time to do anything with.
Is there any fix for this? It is litteraly faster for me to wipe my hard drive and reinstall windows than deleting my Unity Project. what is this madness?
Cache server is a “nerve-saver” in that case