Render Optimization - Revision history

Standingpad: /* Texture Cache */ Remove period in reference

2026-05-16T22:11:24Z

Texture Cache: Remove period in reference

← Older revision		Revision as of 22:11, 16 May 2026
Line 130:		Line 130:
	{{Note\|Note: The following information is about a feature that, as of writing, is not in the stable releases of Blender. While this feature is mostly complete, it is subject to changes before entering stable}}		{{Note\|Note: The following information is about a feature that, as of writing, is not in the stable releases of Blender. While this feature is mostly complete, it is subject to changes before entering stable}}

	In scenes with a large amount of textures, the texture cache feature may be used. At its core, texture cache works by taking every texture in the scene and creating various versions with reduced resolutions; it then loads textures that are visible to the camera, using the distance of objects in the scene to decide the resolution loaded<ref>https://developer.blender.org/docs/release_notes/5.2/cycles/</ref><ref>[https://projects.blender.org/blender/blender/pulls/154913 Blender Pull Request 154913: Cycles: Add image texture cache and mipmaps]</ref><ref>[https://youtu.be/-JVROzcTElM Christopher 3D: Blender 5.2: The New Texture Caching System Explained]</ref>. In addition, when using tiles, Cycles will also unload previously loaded textures that are not visible to the current tile being rendered, through a feature known as cache eviction<ref>[https://projects.blender.org/blender/blender/pulls/157244 Blender Pull Request 157244: Cycles: Texture cache eviction and widen ray differentials]</ref><ref>[https://youtu.be/8PIoc8IJLzk Christopher 3D: Blender 5.2. More memory efficiency gains with Cache Eviction.]</ref>.		In scenes with a large amount of textures, the texture cache feature may be used. At its core, texture cache works by taking every texture in the scene and creating various versions with reduced resolutions; it then loads textures that are visible to the camera, using the distance of objects in the scene to decide the resolution loaded<ref>https://developer.blender.org/docs/release_notes/5.2/cycles/</ref><ref>[https://projects.blender.org/blender/blender/pulls/154913 Blender Pull Request 154913: Cycles: Add image texture cache and mipmaps]</ref><ref>[https://youtu.be/-JVROzcTElM Christopher 3D: Blender 5.2: The New Texture Caching System Explained]</ref>. In addition, when using tiles, Cycles will also unload previously loaded textures that are not visible to the current tile being rendered, through a feature known as cache eviction<ref>[https://projects.blender.org/blender/blender/pulls/157244 Blender Pull Request 157244: Cycles: Texture cache eviction and widen ray differentials]</ref><ref>[https://youtu.be/8PIoc8IJLzk Christopher 3D: Blender 5.2. More memory efficiency gains with Cache Eviction]</ref>.

	However, the significant reductions in memory usage stemming from texture cache come from scenes with many large textures (e.g. 4K textures). Thus, for Minecraft animation specifically, texture cache may only benefit scenes using higher resolution textures, with standard Minecraft animation scenes setting little to no improvement in memory usage. Further testing would be needed to make definite conclusions.		However, the significant reductions in memory usage stemming from texture cache come from scenes with many large textures (e.g. 4K textures). Thus, for Minecraft animation specifically, texture cache may only benefit scenes using higher resolution textures, with standard Minecraft animation scenes setting little to no improvement in memory usage. Further testing would be needed to make definite conclusions.

Standingpad: /* Texture Cache */ Adjust pull request references to make them more clear at a glance

2026-05-16T22:10:52Z

Texture Cache: Adjust pull request references to make them more clear at a glance

← Older revision		Revision as of 22:10, 16 May 2026
Line 130:		Line 130:
	{{Note\|Note: The following information is about a feature that, as of writing, is not in the stable releases of Blender. While this feature is mostly complete, it is subject to changes before entering stable}}		{{Note\|Note: The following information is about a feature that, as of writing, is not in the stable releases of Blender. While this feature is mostly complete, it is subject to changes before entering stable}}

	In scenes with a large amount of textures, the texture cache feature may be used. At its core, texture cache works by taking every texture in the scene and creating various versions with reduced resolutions; it then loads textures that are visible to the camera, using the distance of objects in the scene to decide the resolution loaded<ref>https://developer.blender.org/docs/release_notes/5.2/cycles/</ref><ref>https://projects.blender.org/blender/blender/pulls/154913</ref><ref>[https://youtu.be/-JVROzcTElM Christopher 3D: Blender 5.2: The New Texture Caching System Explained]</ref>. In addition, when using tiles, Cycles will also unload previously loaded textures that are not visible to the current tile being rendered, through a feature known as cache eviction<ref>https://projects.blender.org/blender/blender/pulls/157244</ref><ref>[https://youtu.be/8PIoc8IJLzk Christopher 3D: Blender 5.2. More memory efficiency gains with Cache Eviction.]</ref>.		In scenes with a large amount of textures, the texture cache feature may be used. At its core, texture cache works by taking every texture in the scene and creating various versions with reduced resolutions; it then loads textures that are visible to the camera, using the distance of objects in the scene to decide the resolution loaded<ref>https://developer.blender.org/docs/release_notes/5.2/cycles/</ref><ref>[https://projects.blender.org/blender/blender/pulls/154913 Blender Pull Request 154913: Cycles: Add image texture cache and mipmaps]</ref><ref>[https://youtu.be/-JVROzcTElM Christopher 3D: Blender 5.2: The New Texture Caching System Explained]</ref>. In addition, when using tiles, Cycles will also unload previously loaded textures that are not visible to the current tile being rendered, through a feature known as cache eviction<ref>[https://projects.blender.org/blender/blender/pulls/157244 Blender Pull Request 157244: Cycles: Texture cache eviction and widen ray differentials]</ref><ref>[https://youtu.be/8PIoc8IJLzk Christopher 3D: Blender 5.2. More memory efficiency gains with Cache Eviction.]</ref>.

	However, the significant reductions in memory usage stemming from texture cache come from scenes with many large textures (e.g. 4K textures). Thus, for Minecraft animation specifically, texture cache may only benefit scenes using higher resolution textures, with standard Minecraft animation scenes setting little to no improvement in memory usage. Further testing would be needed to make definite conclusions.		However, the significant reductions in memory usage stemming from texture cache come from scenes with many large textures (e.g. 4K textures). Thus, for Minecraft animation specifically, texture cache may only benefit scenes using higher resolution textures, with standard Minecraft animation scenes setting little to no improvement in memory usage. Further testing would be needed to make definite conclusions.

Standingpad: Adjust references to include video title

2026-05-16T04:46:31Z

Adjust references to include video title

← Older revision		Revision as of 04:46, 16 May 2026
Line 130:		Line 130:
	{{Note\|Note: The following information is about a feature that, as of writing, is not in the stable releases of Blender. While this feature is mostly complete, it is subject to changes before entering stable}}		{{Note\|Note: The following information is about a feature that, as of writing, is not in the stable releases of Blender. While this feature is mostly complete, it is subject to changes before entering stable}}

	In scenes with a large amount of textures, the texture cache feature may be used. At its core, texture cache works by taking every texture in the scene and creating various versions with reduced resolutions; it then loads textures that are visible to the camera, using the distance of objects in the scene to decide the resolution loaded<ref>https://developer.blender.org/docs/release_notes/5.2/cycles/</ref><ref>https://projects.blender.org/blender/blender/pulls/154913</ref><ref>https://youtu.be/-JVROzcTElM</ref>. In addition, when using tiles, Cycles will also unload previously loaded textures that are not visible to the current tile being rendered, through a feature known as cache eviction<ref>https://projects.blender.org/blender/blender/pulls/157244</ref><ref>https://youtu.be/8PIoc8IJLzk</ref>.		In scenes with a large amount of textures, the texture cache feature may be used. At its core, texture cache works by taking every texture in the scene and creating various versions with reduced resolutions; it then loads textures that are visible to the camera, using the distance of objects in the scene to decide the resolution loaded<ref>https://developer.blender.org/docs/release_notes/5.2/cycles/</ref><ref>https://projects.blender.org/blender/blender/pulls/154913</ref><ref>[https://youtu.be/-JVROzcTElM Christopher 3D: Blender 5.2: The New Texture Caching System Explained]</ref>. In addition, when using tiles, Cycles will also unload previously loaded textures that are not visible to the current tile being rendered, through a feature known as cache eviction<ref>https://projects.blender.org/blender/blender/pulls/157244</ref><ref>[https://youtu.be/8PIoc8IJLzk Christopher 3D: Blender 5.2. More memory efficiency gains with Cache Eviction.]</ref>.

	However, the significant reductions in memory usage stemming from texture cache come from scenes with many large textures (e.g. 4K textures). Thus, for Minecraft animation specifically, texture cache may only benefit scenes using higher resolution textures, with standard Minecraft animation scenes setting little to no improvement in memory usage. Further testing would be needed to make definite conclusions.		However, the significant reductions in memory usage stemming from texture cache come from scenes with many large textures (e.g. 4K textures). Thus, for Minecraft animation specifically, texture cache may only benefit scenes using higher resolution textures, with standard Minecraft animation scenes setting little to no improvement in memory usage. Further testing would be needed to make definite conclusions.

Standingpad: Add texture cache information, with warning that it's not yet in stable

2026-05-15T21:49:45Z

Add texture cache information, with warning that it's not yet in stable

← Older revision		Revision as of 21:49, 15 May 2026
Line 125:		Line 125:

	Adaptive subdivision and/or [[Level of Detail\|LOD]] may also introduce memory savings for terrain.<ref>[https://youtu.be/8gSyEpt4-60?t=1670 Blender Guru: 18 Ways to Speed Up Cycles Rendering - Adaptive Subdivision]</ref>		Adaptive subdivision and/or [[Level of Detail\|LOD]] may also introduce memory savings for terrain.<ref>[https://youtu.be/8gSyEpt4-60?t=1670 Blender Guru: 18 Ways to Speed Up Cycles Rendering - Adaptive Subdivision]</ref>

			===== Texture Cache =====

			{{Note\|Note: The following information is about a feature that, as of writing, is not in the stable releases of Blender. While this feature is mostly complete, it is subject to changes before entering stable}}

			In scenes with a large amount of textures, the texture cache feature may be used. At its core, texture cache works by taking every texture in the scene and creating various versions with reduced resolutions; it then loads textures that are visible to the camera, using the distance of objects in the scene to decide the resolution loaded<ref>https://developer.blender.org/docs/release_notes/5.2/cycles/</ref><ref>https://projects.blender.org/blender/blender/pulls/154913</ref><ref>https://youtu.be/-JVROzcTElM</ref>. In addition, when using tiles, Cycles will also unload previously loaded textures that are not visible to the current tile being rendered, through a feature known as cache eviction<ref>https://projects.blender.org/blender/blender/pulls/157244</ref><ref>https://youtu.be/8PIoc8IJLzk</ref>.

			However, the significant reductions in memory usage stemming from texture cache come from scenes with many large textures (e.g. 4K textures). Thus, for Minecraft animation specifically, texture cache may only benefit scenes using higher resolution textures, with standard Minecraft animation scenes setting little to no improvement in memory usage. Further testing would be needed to make definite conclusions.

Standingpad: Add details related to unbiased volumetric rendering

2026-05-15T21:14:59Z

Add details related to unbiased volumetric rendering

← Older revision		Revision as of 21:14, 15 May 2026
Line 63:		Line 63:
	</tabber>		</tabber>

	In addition to max light bounces, there is also stepping rate and max steps. Stepping rate defines how many "steps" is performed in a volumetric object, where lower values allow for more detail, at the cost of render time, and max steps defines how many steps Cycles will perform for volumes before giving up<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/volumes.html</ref>. Depending on the scene, the default value of <math>1</math> may be excessively low, and increasing the rate may allow for performance improvements. In addition, decreasing max steps may also improve render times, at the cost of detail.		In addition to max light bounces, there is also volume rendering, which can be set to either the biased ray marching algorithm, or unbiased null scattering algorithm. By default, Cycles uses the unbiased null scattering algorithm to avoid artifacts, at the cost of potentially more noise<ref>https://projects.blender.org/blender/blender/pulls/134460</ref><ref>https://docs.blender.org/manual/en/latest/render/cycles/render_settings/volumes.html</ref>. However, in certain scenarios, null scattering can incur a performance penalty compared to biased rendering with comparable output; this usually occurs in objects where the stepping rate and/or max steps options in biased rendering can be adjusted for performance gains, with little loss in the quality of the rendered volume, such as with clouds<ref>https://www.youtube.com/watch?v=NpKwVgTwAFg</ref>.

			Biased volume rendering in Cycles is based on two settings: stepping rate, and max steps. Stepping rate defines how many "steps" is performed in a volumetric object, where lower values allow for more detail, at the cost of render time, and max steps defines how many steps Cycles will perform for volumes before giving up<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/volumes.html</ref>. Depending on the scene, the default value of <math>1</math> may be excessively low, and increasing the rate may allow for performance improvements. In addition, decreasing max steps may also improve render times, at the cost of detail.

	Like many path tracers, Cycles includes options to clamp the brightness of pixels caused by both direct and indirect bounces. When set to <math>0</math>, no clamping is done<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/light_paths.html#clamping</ref>. While clamping direct lighting is usually not necessary, clamping indirect lighting may reduce the amount of [[Firefly\|fireflies]] created when rendering. However, clamping indirect can often reduce the brightness of highlights on reflective objects.		Like many path tracers, Cycles includes options to clamp the brightness of pixels caused by both direct and indirect bounces. When set to <math>0</math>, no clamping is done<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/light_paths.html#clamping</ref>. While clamping direct lighting is usually not necessary, clamping indirect lighting may reduce the amount of [[Firefly\|fireflies]] created when rendering. However, clamping indirect can often reduce the brightness of highlights on reflective objects.
Line 94:		Line 96:
	Alpha transparency may introduce slow down when rendering as Cycles has to execute an object's shader trace a ray when hitting a transparent portion.<ref>https://docs.blender.org/manual/en/latest/render/cycles/render_settings/light_paths.html#transparency</ref> In cases where many objects with alpha transparency overlap, such as leaves or grass, it may be beneficial to remove the transparent portions. <ref>[https://youtu.be/8gSyEpt4-60?si=yKZp6k1iYtFfiVPH Blender Guru: 18 Ways to Speed Up Cycles Rendering - Remove Alpha Transparency]</ref> However, it's possible that any performance improvement is negated by the cost any additional geometry needed to remove alpha transparent faces.		Alpha transparency may introduce slow down when rendering as Cycles has to execute an object's shader trace a ray when hitting a transparent portion.<ref>https://docs.blender.org/manual/en/latest/render/cycles/render_settings/light_paths.html#transparency</ref> In cases where many objects with alpha transparency overlap, such as leaves or grass, it may be beneficial to remove the transparent portions. <ref>[https://youtu.be/8gSyEpt4-60?si=yKZp6k1iYtFfiVPH Blender Guru: 18 Ways to Speed Up Cycles Rendering - Remove Alpha Transparency]</ref> However, it's possible that any performance improvement is negated by the cost any additional geometry needed to remove alpha transparent faces.

	Volumetric shaders may introduce additional noise and render time.<ref>[https://youtu.be/8gSyEpt4-60?t=1931 Blender Guru: 18 Ways to Speed Up Cycles Rendering - Remove Volumetrics]</ref> In cases where volumetric shaders are used for god-rays, 2D emissive ~~plans~~ can make a suitable substitute.		Volumetric shaders may introduce additional noise and render time.<ref>[https://youtu.be/8gSyEpt4-60?t=1931 Blender Guru: 18 Ways to Speed Up Cycles Rendering - Remove Volumetrics]</ref> In cases where volumetric shaders are used for god-rays, 2D emissive planes can make a suitable substitute.

	==== Lights ====		==== Lights ====

Standingpad: Clarified sentence regarding cost of removing alpha faces

2025-07-09T05:05:16Z

Clarified sentence regarding cost of removing alpha faces

← Older revision		Revision as of 05:05, 9 July 2025
Line 92:		Line 92:
	Like glass, the emission shader is often linked to increased noise.		Like glass, the emission shader is often linked to increased noise.

	Alpha transparency may introduce slow down when rendering as Cycles has to execute an object's shader trace a ray when hitting a transparent portion.<ref>https://docs.blender.org/manual/en/latest/render/cycles/render_settings/light_paths.html#transparency</ref> In cases where many objects with alpha transparency overlap, such as leaves or grass, it may be beneficial to remove the transparent portions. <ref>[https://youtu.be/8gSyEpt4-60?si=yKZp6k1iYtFfiVPH Blender Guru: 18 Ways to Speed Up Cycles Rendering - Remove Alpha Transparency]</ref> However, ~~this may also be~~ negated by the cost any additional geometry needed to remove alpha transparent faces.		Alpha transparency may introduce slow down when rendering as Cycles has to execute an object's shader trace a ray when hitting a transparent portion.<ref>https://docs.blender.org/manual/en/latest/render/cycles/render_settings/light_paths.html#transparency</ref> In cases where many objects with alpha transparency overlap, such as leaves or grass, it may be beneficial to remove the transparent portions. <ref>[https://youtu.be/8gSyEpt4-60?si=yKZp6k1iYtFfiVPH Blender Guru: 18 Ways to Speed Up Cycles Rendering - Remove Alpha Transparency]</ref> However, it's possible that any performance improvement is negated by the cost any additional geometry needed to remove alpha transparent faces.

	Volumetric shaders may introduce additional noise and render time.<ref>[https://youtu.be/8gSyEpt4-60?t=1931 Blender Guru: 18 Ways to Speed Up Cycles Rendering - Remove Volumetrics]</ref> In cases where volumetric shaders are used for god-rays, 2D emissive plans can make a suitable substitute.		Volumetric shaders may introduce additional noise and render time.<ref>[https://youtu.be/8gSyEpt4-60?t=1931 Blender Guru: 18 Ways to Speed Up Cycles Rendering - Remove Volumetrics]</ref> In cases where volumetric shaders are used for god-rays, 2D emissive plans can make a suitable substitute.

Standingpad: Add mention of light tree bug

2025-07-07T20:19:02Z

Add mention of light tree bug

← Older revision		Revision as of 20:19, 7 July 2025
Line 31:		Line 31:
	Beyond adjusting the sample count, there are alternate settings in Cycles specifically related to sampling. In particular, adjusting [[Adaptive Sampling\|adaptive sampling]] settings to kick in earlier on can reduce render times, at the cost of more noise.<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/sampling.html#adaptive-sampling</ref> Setting the noise threshold to <math>0.03</math> instead of <math>0.01</math> may be a good compromise of quality and render times.		Beyond adjusting the sample count, there are alternate settings in Cycles specifically related to sampling. In particular, adjusting [[Adaptive Sampling\|adaptive sampling]] settings to kick in earlier on can reduce render times, at the cost of more noise.<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/sampling.html#adaptive-sampling</ref> Setting the noise threshold to <math>0.03</math> instead of <math>0.01</math> may be a good compromise of quality and render times.

	Another sampling related setting in Cycles is [[Light Tree\|light tree]], which reduces noise in scenes with a large amount of lights<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/sampling.html#lights</ref>.		Another sampling related setting in Cycles is [[Light Tree\|light tree]], which reduces noise in scenes with a large amount of lights<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/sampling.html#lights</ref>. Note that issues may result from overlapping area lights, though this may be a bug.<ref>https://projects.blender.org/blender/blender/issues/141576</ref>

	==== Light Paths ====		==== Light Paths ====

Standingpad: Fixed light tree link

2025-07-07T18:51:43Z

Fixed light tree link

← Older revision		Revision as of 18:51, 7 July 2025
Line 31:		Line 31:
	Beyond adjusting the sample count, there are alternate settings in Cycles specifically related to sampling. In particular, adjusting [[Adaptive Sampling\|adaptive sampling]] settings to kick in earlier on can reduce render times, at the cost of more noise.<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/sampling.html#adaptive-sampling</ref> Setting the noise threshold to <math>0.03</math> instead of <math>0.01</math> may be a good compromise of quality and render times.		Beyond adjusting the sample count, there are alternate settings in Cycles specifically related to sampling. In particular, adjusting [[Adaptive Sampling\|adaptive sampling]] settings to kick in earlier on can reduce render times, at the cost of more noise.<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/sampling.html#adaptive-sampling</ref> Setting the noise threshold to <math>0.03</math> instead of <math>0.01</math> may be a good compromise of quality and render times.

	Another sampling related setting in Cycles is [[Light ~~Trees~~\|light tree]], which reduces noise in scenes with a large amount of lights<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/sampling.html#lights</ref>.		Another sampling related setting in Cycles is [[Light Tree\|light tree]], which reduces noise in scenes with a large amount of lights<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/sampling.html#lights</ref>.

	==== Light Paths ====		==== Light Paths ====

Standingpad: Remove cost from light tree since it's not relevant

2025-07-07T18:46:56Z

Remove cost from light tree since it's not relevant

← Older revision		Revision as of 18:46, 7 July 2025
Line 31:		Line 31:
	Beyond adjusting the sample count, there are alternate settings in Cycles specifically related to sampling. In particular, adjusting [[Adaptive Sampling\|adaptive sampling]] settings to kick in earlier on can reduce render times, at the cost of more noise.<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/sampling.html#adaptive-sampling</ref> Setting the noise threshold to <math>0.03</math> instead of <math>0.01</math> may be a good compromise of quality and render times.		Beyond adjusting the sample count, there are alternate settings in Cycles specifically related to sampling. In particular, adjusting [[Adaptive Sampling\|adaptive sampling]] settings to kick in earlier on can reduce render times, at the cost of more noise.<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/sampling.html#adaptive-sampling</ref> Setting the noise threshold to <math>0.03</math> instead of <math>0.01</math> may be a good compromise of quality and render times.

	Another sampling related setting in Cycles is [[Light Trees\|light tree]], which reduces noise in scenes with a ~~heavy~~ amount of lights<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/sampling.html#lights</ref>~~, but may cause more noise in scenes with fewer lights~~.		Another sampling related setting in Cycles is [[Light Trees\|light tree]], which reduces noise in scenes with a large amount of lights<ref>https://docs.blender.org/manual/en/4.4/render/cycles/render_settings/sampling.html#lights</ref>.

	==== Light Paths ====		==== Light Paths ====

Standingpad: Make portal examples use tabber

2025-07-07T16:42:07Z

Make portal examples use tabber

← Older revision		Revision as of 16:42, 7 July 2025
Line 102:		Line 102:
	For a long time, light portals were a suggested method of decreasing noise in interior scenes.<ref>https://docs.blender.org/manual/en/latest/render/cycles/light_settings.html#render-cycles-lights-area-portals</ref><ref>[https://youtu.be/8gSyEpt4-60?t=458 Blender Guru: 18 Ways to Speed Up Cycles Rendering - Use Portals]</ref> However, in practice, light portals do not seem to make any difference in noise quality, both with large exterior gaps and small exterior gaps, while also slightly increasing render times. For this reason, light portals '''are not recommended''' as of Blender 3.0+. Cycles Legacy (Blender 2.61 to 2.93) may see benefits from portals, but more tests are needed.		For a long time, light portals were a suggested method of decreasing noise in interior scenes.<ref>https://docs.blender.org/manual/en/latest/render/cycles/light_settings.html#render-cycles-lights-area-portals</ref><ref>[https://youtu.be/8gSyEpt4-60?t=458 Blender Guru: 18 Ways to Speed Up Cycles Rendering - Use Portals]</ref> However, in practice, light portals do not seem to make any difference in noise quality, both with large exterior gaps and small exterior gaps, while also slightly increasing render times. For this reason, light portals '''are not recommended''' as of Blender 3.0+. Cycles Legacy (Blender 2.61 to 2.93) may see benefits from portals, but more tests are needed.

	<gallery mode="packed" heights="400px" caption="4096 samples, 0.03 noise threshold~~, large gap~~">		<tabber>
			\|-\|Large Gap=
			<gallery mode="packed" heights="400px" caption="4096 samples, 0.03 noise threshold">
	File:Portals Test- Nishita - No Portals.jpg\|alt=Heatmap of sample count in a scene without portals\|Heatmap of sample count in a scene without portals		File:Portals Test- Nishita - No Portals.jpg\|alt=Heatmap of sample count in a scene without portals\|Heatmap of sample count in a scene without portals
	File:Portals Test- Nishita - With Portals.jpg\|alt=Heatmap of sample count in a scene with portals\|Heatmap of sample count in a scene with portals. Note the lack of any major difference to the heatmap without portals		File:Portals Test- Nishita - With Portals.jpg\|alt=Heatmap of sample count in a scene with portals\|Heatmap of sample count in a scene with portals. Note the lack of any major difference to the heatmap without portals
	</gallery>		</gallery>

	<gallery mode="packed" heights="400px" caption="4096 samples, 0.03 noise threshold~~, small gap~~">		\|-\|Small Gap=
	File:Portals Test- Nishita - No Portals Small Gap.jpg\|alt=Heatmap of sample count in a scene without portals and small gap\|Heatmap of sample count in a scene without portals ~~and small gap~~		<gallery mode="packed" heights="400px" caption="4096 samples, 0.03 noise threshold">
	File:Portals Test- Nishita - With Portals Small Gap.jpg\|alt=Heatmap of sample count in a scene with portals and small gap\|Heatmap of sample count in a scene with portals ~~and small gap~~. Note the lack of any major difference to the heatmap without portals		File:Portals Test- Nishita - No Portals Small Gap.jpg\|alt=Heatmap of sample count in a scene without portals and small gap\|Heatmap of sample count in a scene without portals
			File:Portals Test- Nishita - With Portals Small Gap.jpg\|alt=Heatmap of sample count in a scene with portals and small gap\|Heatmap of sample count in a scene with portals. Note the lack of any major difference to the heatmap without portals
	</gallery>		</gallery>
			</tabber>

	In theory, path guiding is a more viable alternative, though only CPU rendering is supported.<ref>https://docs.blender.org/manual/en/latest/render/cycles/render_settings/sampling.html#path-guiding</ref>		In theory, path guiding is a more viable alternative, though only CPU rendering is supported.<ref>https://docs.blender.org/manual/en/latest/render/cycles/render_settings/sampling.html#path-guiding</ref>