The GI cache is used by the Global Illumination (GI) system to store intermediate files when precomputing real-time GI, and when baking Static LightmapsA pre-rendered texture that contains the effects of light sources on static objects in the scene. Lightmaps are overlaid on top of scene geometry to create the effect of lighting. More info
See in Glossary, Light ProbesLight probes store information about how light passes through space in your scene. A collection of light probes arranged within a given space can improve lighting on moving objects and static LOD scenery within that space. More info
See in Glossary and Reflection ProbesA rendering component that captures a spherical view of its surroundings in all directions, rather like a camera. The captured image is then stored as a Cubemap that can be used by objects with reflective materials. More info
See in Glossary. The cache is shared between all Unity projects on the computer, so projects with the same content and same version of the lighting system (Enlighten) can share the files and speed up subsequent builds.
Find the settings for the GI cache in Edit > Preferences > GI Cache on Windows, or Unity > Preferences > GI Cache on macOS.
|Maximum Cache Size (GB)||Use the slider to define the maximum size of the GI cache, in gigabytes. When the GI cache’s size grows larger than the size specified in Preferences > GI Cache, Unity spawns a job to trim the cache. The trim job removes some files so the GI cache does not exceed the size specified. It removes files based on when they were last accessed; it removes those which were last accessed the longest time ago, and keeps those that were most recently used.
Note: If all the files in the GI cache are currently being used by the current Scene (perhaps because the Scene is very large or the cache size is set too low), increase your cache size. Otherwise, resource-intensive recomputation occurs when baking.
|Custom cache location||By default, the GI cache is stored in the Caches folder. Tick Custom cache location to override the default location and set your own.
Note: Storing the GI Cache on an SSD drive can speed up baking in cases where the baking process is I/O bound.
|Cache compression||Tick this checkbox to allow Unity to compress files in the GI cache. The files are LZ4 compressed by default, and the naming scheme is a hash and a file extension. The hashes are computed based on the inputs to the lighting system, so changing any of the following can lead to recomputation of lighting:
- Materials (Textures, Albedo, Emission)
- Static flags
- Light Probe groups
- Reflection probes
- Lightmap Parameters
|Clean Cache||Use the Clean Cache button to delete the GI Cache directory.
It is not safe to delete the GI Cache directory manually while the Editor is running. This is because the GiCache folder is created on Editor startup, and the Editor maintains a collection of hashes that are used to look up the files in the GiCache folder. If a file or directory suddenly disappears, the system can’t always recover from the failure, and prints an error in the Console. The Clean Cache button ensures that the Editor releases all references to the files on disk before they are deleted.
To ensure that the the lighting data loads from the GI cache in a very short amount of time when you reload your Scene, open the Lighting window (menu: Window > Lighting) and tick the Auto checkbox next to the build button. This makes lightmap baking automatic, meaning that the lightmap data is stored in the GI cache.
In the Lighting window, you can clear the baked data in a SceneA Scene contains the environments and menus of your game. Think of each unique Scene file as a unique level. In each Scene, you place your environments, obstacles, and decorations, essentially designing and building your game in pieces. More info
See in Glossary (untick the Auto checkbox, click the BuildThe process of compiling your project into a format that is ready to run on a specific platform or platforms. More info
See in Glossary button drop-down and select Clear Baked Data). This does not clear the GI Cache, because this would increase bake time afterwards.
You can share the GiCache folder among different machines. This can make your lighting build faster, because the files are downloaded from the GiCache folder instead of computed locally. Note that the build process isn’t optimized for slow network-attached storage (NAS), so test if your bake times are severely affected before moving the cache to NAS.
Did you find this page useful? Please give it a rating: