Partial scene baking - Revision history

Mr F at 16:29, 14 November 2024

2024-11-14T16:29:48Z

Mr F: /* Light probes and volumes */

2024-01-10T12:57:31Z

‎Light probes and volumes

Mr F: /* Material compatibility */

2023-05-18T16:52:14Z

‎Material compatibility

Mr F: /* The sector system */

2022-11-16T15:42:50Z

‎The sector system

Mr F: /* Material compatibility */

2021-05-31T19:14:20Z

‎Material compatibility

Mr F: /* Material compatibility */

2021-05-31T19:13:53Z

‎Material compatibility

Mr F: /* Material compatibility */

2021-05-31T19:12:20Z

‎Material compatibility

Mr F: /* Light probes and volumes */

2021-05-31T19:12:11Z

‎Light probes and volumes

Mr F: /* The sector system */

2021-05-31T16:11:30Z

‎The sector system

Mr F: /* The sector system */

2021-05-31T16:11:12Z

‎The sector system

← Older revision		Revision as of 16:29, 14 November 2024
Line 1:		Line 1:
−	In the level design process, especially when working on very large maps, it is often desirable to only rebake a small chunk of the world and iterate on it. Originally Bakery's [[Manual#Bakery_Lightmap_Group_Selector\|Lightmap Groups]] were meant to achieve it (apart from their other benefits). In practice, however, it didn't work well, as they are limited to a single lightmap atlas, and "Render Selected" functionality had too many constraints due to lightmapper's core architecture. "Render Selected" also didn't reduce the memory footprint of world geometry; all vertices and triangles of all loaded scenes had to be ready in VRAM.	+	In the level design process, especially when working on very large maps, it is often desirable to only rebake a small chunk of the world and iterate on it. Originally Bakery's [[Manual#Bakery_Lightmap_Group_Selector\|Lightmap Groups]] were meant to achieve it (apart from their other benefits). In practice, however, it didn't work well, as they are limited to a single lightmap atlas, and "Render Selected Groups" functionality had too many constraints due to lightmapper's core architecture. "Render Selected Groups" also didn't reduce the memory footprint of world geometry; all vertices and triangles of all loaded scenes had to be ready in VRAM.

	Large scenes could be also split into multiple smaller scenes, but this approach required more setup and, most importantly, such scenes couldn't light/shadow each other.		Large scenes could be also split into multiple smaller scenes, but this approach required more setup and, most importantly, such scenes couldn't light/shadow each other.

@@ Line 104: / Line 104: @@
 === Light probes and volumes ===
-* Light probes are not baked if any sector is chosen. They only update in regular full bakes or with "Render Light Probes".
+* Since v1.96, light probes can be partially baked inside sectors, if "Bake Light Probes" checkbox is set on the Sector. Light Probe Groups must be in the hierarchy of the root Sector object.
 * Volumes from the hierarchy of the chosen sector are baked; other volumes are left unchanged.

← Older revision		Revision as of 16:52, 18 May 2023
Line 113:		Line 113:

	Internally, capture points render the scene in 6 directions using special shaders that output albedo, normal and depth.		Internally, capture points render the scene in 6 directions using special shaders that output albedo, normal and depth.
−	As these shaders don't have original shaders' logic, procedural albedos may be lost. Currently every rendered object will draw _MainTex/_BaseMap/_BaseColorMap of the material (whichever is present). As capture points draw objects directly as seen (with perspective projection), they can't, unlike the lightmapper or the RTPreview, use [https://docs.unity3d.com/Manual/MetaPass.html Meta Pass].	+	As these shaders don't have original shaders' logic, procedural albedos may be lost. Currently every rendered object will draw _MainTex/_BaseMap/_BaseColorMap of the material (whichever is present). As capture points draw objects directly as seen (with perspective projection), they can't, unlike the lightmapper or the RTPreview, use the [https://docs.unity3d.com/Manual/MetaPass.html Meta Pass].

@@ Line 5: / Line 5: @@
 == The sector system ==
 [[File:Bsector.jpg|thumb|BakerySector component UI]]
-The new sector system (added in v1.9) attempts to solve this problem.
+The sector system (added in v1.9) attempts to solve this problem.
 '''BakerySector''' is a collection of objects that can be baked separately. Similar to Lightmap Groups, adding BakerySector component to a root object of a hierarchy, marks all objects in this hierarchy as belonging to this sector.

← Older revision		Revision as of 19:14, 31 May 2021
Line 113:		Line 113:

	Internally, capture points render the scene in 6 directions using special shaders that output albedo, normal and depth.		Internally, capture points render the scene in 6 directions using special shaders that output albedo, normal and depth.
−	As these shaders don't have original shaders' logic, procedural albedos may be lost. Currently every rendered object will draw _MainTex/_BaseMap/_BaseColorMap of the material (whichever is present). As capture points draw objects directly as seen (with perspective projection), they can't, unlike the lightmapper or the RTPreview, use [https://docs.unity3d.com/Manual/MetaPass.html\|Meta Pass].	+	As these shaders don't have original shaders' logic, procedural albedos may be lost. Currently every rendered object will draw _MainTex/_BaseMap/_BaseColorMap of the material (whichever is present). As capture points draw objects directly as seen (with perspective projection), they can't, unlike the lightmapper or the RTPreview, use [https://docs.unity3d.com/Manual/MetaPass.html Meta Pass].

← Older revision		Revision as of 19:13, 31 May 2021
Line 113:		Line 113:

	Internally, capture points render the scene in 6 directions using special shaders that output albedo, normal and depth.		Internally, capture points render the scene in 6 directions using special shaders that output albedo, normal and depth.
−	As these shaders don't have original shaders' logic, procedural albedos may be lost. Currently every rendered object will draw _MainTex/_BaseMap/_BaseColorMap of the material (whichever is present).	+	As these shaders don't have original shaders' logic, procedural albedos may be lost. Currently every rendered object will draw _MainTex/_BaseMap/_BaseColorMap of the material (whichever is present). As capture points draw objects directly as seen (with perspective projection), they can't, unlike the lightmapper or the RTPreview, use [https://docs.unity3d.com/Manual/MetaPass.html\|Meta Pass].

← Older revision		Revision as of 19:12, 31 May 2021
Line 107:		Line 107:

	* Volumes from the hierarchy of the chosen sector are baked; other volumes are left unchanged.		* Volumes from the hierarchy of the chosen sector are baked; other volumes are left unchanged.
		+
		+	<hr>

	=== Material compatibility ===		=== Material compatibility ===