Change Details

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 950/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11 **Blender Version** Broken: version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: `rBf1cca3055776` Does not occur in version: 2.93.7 **Short description of error** When rendering scene with glossy materials and a volume object encompassing the whole scene, glossy indirect pass doesn't reflect world lighting or the volume material correctly. If volumetric objects are disabled from rendering, glossy indirect will correctly reflect world lighting. Only happens in Blender 3.0 and 3.1 as error does not exist in Blender 2.93.7. Occurs with: - "Principled Volume" and "Volume Scatter". - Objects with volume material covering whole scene and world volumes. - Does not occur with "Volume Absorption" node. {F12708156} {F12708158} **Exact steps for others to reproduce the error** To view rendered image and image created from render passes: - Open attached .blend and render image. - Change between "0 and 1" on the mix node to switch between the rendered image and the image reconstructed from render passes. To view glossy indirect differences: - Open attached .blend - Render image to slot 1 in "Image Editor" workspace and connect "GlossInd" in "Render Layers" node to "image" in "Composite" node. - In "Outliner" workspace, disable rendering of object labelled as "Volume". - Change to slot 2 and render image, connect "GlossInd" to "Composite" node and compare slot 1 to slot 2. - Note: Rendering images to separate slots does not create the error. Rendering to separate slots only helps to quickly switch between both images. Thanks! {F12708203}

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 950/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11 **Blender Version** Broken: version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: `rBf1cca3055776` Does not occur in version: 2.93.7 **Short description of error** When rendering scene with light render passes enabled (e.g. diffuse, glossy, transmission, volume) and with objects that possess a volumetric material, "Glossy Indirect" does not reflect any object that contains volumetric materials, this also includes world volumes. If an object contains both a BSDF material (e.g. Principled BSDF) and a volume material, the BSDF will be reflected while the volume remains not present in the 'Glossy Indirect' pass. Note that volumes are reflected in the render result and in the viewport, but are absent with the 'Glossy Indirect' pass. Occurs with Blender 3.0 and the newest build of Blender 3.1 (24 Jan, 2022). This issue is absent in Blender 2.93. Occurs with: - CPU and GPU Rendering - "Principled Volume" and "Volume Scatter". - Objects with volume materials and world volumes. - Does not occur with "Volume Absorption" node. {F12708156} {F12708158} **Exact steps for others to reproduce the error** To view rendered image and image created from render passes: - Open attached .blend and render image. - Change between "0 and 1" on the mix node to switch between the rendered image and the image reconstructed from render passes. To view glossy indirect differences: - Open attached .blend - Render image to slot 1 in "Image Editor" workspace and connect "GlossInd" in "Render Layers" node to "image" in "Composite" node. - In "Outliner" workspace, disable rendering of object labelled as "Volume". - Change to slot 2 and render image, connect "GlossInd" to "Composite" node and compare slot 1 to slot 2. - Note: Rendering images to separate slots does not create the error. Rendering to separate slots only helps to quickly switch between both images. Thanks! {F12708203} Update 1.0 ( 25 Jan, 2022): - Changed title. - Updated "Short description of error" to more accurately reflect the issue.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 950/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11 **Blender Version** Broken: version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: `rBf1cca3055776` Does not occur in version: 2.93.7 **Short description of error** When rendering scene with glossy materials and a volume object encompassing the whole scenelight render passes enabled (e.g. diffuse, glossy, transmission, volume) and with objects that possess a volumetric material, "Glossy Indirect" does not reflect any object that contains volumetric materials, this also includes world volumes. If an object contains both a BSDF material (e.g. Principled BSDF) and a volume material, glossy indirect pass doesn't reflect world lighting or the volume material correctly. If volumetric objects are disabled from renderingthe BSDF will be reflected while the volume remains not present in the 'Glossy Indirect' pass. Note that volumes are reflected in the render result and in the viewport, glossy indirecbut are absent will correctly reflect world lightingth the 'Glossy Indirect' pass. Only happens in Blender 3.0 andOccurs with Blender 3.0 and the newest build of Blender 3.1 as error does not exis(24 Jan, 2022). This issue is absent in Blender 2.93.7. Occurs with: - CPU and GPU Rendering - "Principled Volume" and "Volume Scatter". - Objects with volume material covering whole scenes and world volumes. - Does not occur with "Volume Absorption" node. {F12708156} {F12708158} **Exact steps for others to reproduce the error** To view rendered image and image created from render passes: - Open attached .blend and render image. - Change between "0 and 1" on the mix node to switch between the rendered image and the image reconstructed from render passes. To view glossy indirect differences: - Open attached .blend - Render image to slot 1 in "Image Editor" workspace and connect "GlossInd" in "Render Layers" node to "image" in "Composite" node. - In "Outliner" workspace, disable rendering of object labelled as "Volume". - Change to slot 2 and render image, connect "GlossInd" to "Composite" node and compare slot 1 to slot 2. - Note: Rendering images to separate slots does not create the error. Rendering to separate slots only helps to quickly switch between both images. Thanks! {F12708203} Update 1.0 ( 25 Jan, 2022): - Changed title. - Updated "Short description of error" to more accurately reflect the issue.