You can reduce the time taken to bake data and the size of the generated data if you bake your data into multiple scenes.
To predetermine the brightness of surfaces in your scenes, you can bake lightmaps. There are two ways to bake lightmaps for multiple scenes at once:
Shadows and GI light bounces work across all scenes, but the lightmaps and Realtime GI data loads and unloads separately for each scene. This means scenes don’t share and you can unload scenes with lightmaps safely. Scenes do share Light Probe data so all Light Probes for scenes baked together load at the same time.
There are two ways to bake your NavMesh data for multiple scenes at once, which shows an approximation of the walkable surface on your scenes:
This bakes the NavMesh data into a single asset that’s shared by your loaded scenes. The data saves in the folder that matches the name of the current active scene.
You can bake occlusion culling data for multiple scenes at once to determine which GameObjects render: 1. Open the scenes that you want to bake. 2. Go to the Occlusion Culling window (Window > Rendering > Occlusion Culling). 3. Select the Bake button. 4. Save the baked scenes to make the scene-to-occlusion-data reference persistent.
This saves the occlusion culling data into a single asset called OcclusionCullingData.asset
in a folder matching the name of the current active scene.
If you load a scene additively and it has the same occlusion data reference as the active scene, then the static renderers and portals that cull information for that scene initialize from the occlusion data. This means the occlusion system performs as if static renderers and portals are baked into a single scene.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.