Enabling Environment pass corrupts view layer in 2.93.1 (regression) #90047

Closed
opened 2021-07-22 16:02:20 +02:00 by sentharn · 12 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11

Blender Version
Broken: version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash: 1b8d33b18c
Worked: 2.92

Short description of error
Enabling Environment pass corrupts view layer

Exact steps for others to reproduce the error
I enabled the Environment pass on a cloned view layer in this file. All of the tiles with geometry in them look corrupted now in that view layer. It goes away if I uncheck Environment. This only happens in 2.93.1; older versions render this file fine.

BROKEN.blend

Additional information, to repro from scratch:

  • Create two view layers (OK if they bot have the same content/settings)
  • Enable Environment for the 2nd layer (other passes may work too)
  • Enable compositing and set up Alpha Overlay so that 1st layer is overlaid on top of 2nd layer
  • Enable Persistent Data

2nd layer should now be corrupted on render.

Disabling Persistent Data stops the corruption, so there is something wrong with that.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11 **Blender Version** Broken: version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash: `1b8d33b18c` Worked: 2.92 **Short description of error** Enabling Environment pass corrupts view layer **Exact steps for others to reproduce the error** I enabled the Environment pass on a cloned view layer in this file. All of the tiles with geometry in them look corrupted now in that view layer. It goes away if I uncheck Environment. This only happens in 2.93.1; older versions render this file fine. [BROKEN.blend](https://archive.blender.org/developer/F10233778/BROKEN.blend) Additional information, to repro from scratch: - Create two view layers (OK if they bot have the same content/settings) - Enable Environment for the 2nd layer (other passes may work too) - Enable compositing and set up Alpha Overlay so that 1st layer is overlaid on top of 2nd layer - Enable **Persistent Data** ``` ``` 2nd layer should now be corrupted on render. Disabling Persistent Data stops the corruption, so there is something wrong with that.
Author

Added subscriber: @sentharn

Added subscriber: @sentharn
Author

Error occurs on Blender 2.93.1 on Ubuntu 20.04 as well.

Error occurs on Blender 2.93.1 on Ubuntu 20.04 as well.
Author

Example of corruption:

corruption.PNG

Example of corruption: ![corruption.PNG](https://archive.blender.org/developer/F10233789/corruption.PNG)
Author

Additional information, to repro from scratch:

  • Create two view layers (OK if they bot have the same content/settings)
  • Enable Environment for the 2nd layer (other passes may work too)
  • Enable compositing and set up Alpha Overlay so that 1st layer is overlaid on top of 2nd layer
  • Enable Persistent Data

2nd layer should now be corrupted on render.

Disabling Persistent Data stops the corruption, so there is something wrong with that.

Additional information, to repro from scratch: - Create two view layers (OK if they bot have the same content/settings) - Enable Environment for the 2nd layer (other passes may work too) - Enable compositing and set up Alpha Overlay so that 1st layer is overlaid on top of 2nd layer - Enable **Persistent Data** ``` ``` 2nd layer should now be corrupted on render. Disabling Persistent Data stops the corruption, so there is something wrong with that.

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

Do you render with GPU? I can't reproduce issue with CPU rendering.

Do you render with GPU? I can't reproduce issue with CPU rendering.
Author

In #90047#1195118, @iss wrote:
Do you render with GPU? I can't reproduce issue with CPU rendering.

Yes, sorry. CUDA rendering on a GTX 1080.

The broken file has the same issue on CPU only for me. I can repro it from scratch. Is there geometry in the scene? Only the areas with any geometry will be corrupted.

EDIT: You might need to flip the order of alpha over to see the final result in Composite, but if you check the view layer independently in the image viewer it'll be corrupted regardless of it it was composited or not, so the compositor might be a red herring.

> In #90047#1195118, @iss wrote: > Do you render with GPU? I can't reproduce issue with CPU rendering. Yes, sorry. CUDA rendering on a GTX 1080. The broken file has the same issue on CPU only for me. I can repro it from scratch. Is there geometry in the scene? Only the areas with any geometry will be corrupted. EDIT: You might need to flip the order of alpha over to see the final result in Composite, but if you check the view layer independently in the image viewer it'll be corrupted regardless of it it was composited or not, so the compositor might be a red herring.

Closed as duplicate of #89396

Closed as duplicate of #89396

Added subscriber: @brecht

Added subscriber: @brecht

This was fixed already in master / 3.0, it's a matter of time before the fix makes it into the next 2.93 LTS release,

This was fixed already in master / 3.0, it's a matter of time before the fix makes it into the next 2.93 LTS release,
Author

In #90047#1195552, @brecht wrote:
This was fixed already in master / 3.0, it's a matter of time before the fix makes it into the next 2.93 LTS release,

Thanks brecht. Sorry to have taken up y'all's time. I have been chasing another bug and searching all over the bug tracker for it, but it slipped my mind to search for this one. I'm glad to see that it has been patched and look forward to the next 2.93 LTS release.

> In #90047#1195552, @brecht wrote: > This was fixed already in master / 3.0, it's a matter of time before the fix makes it into the next 2.93 LTS release, Thanks brecht. Sorry to have taken up y'all's time. I have been chasing another bug and searching all over the bug tracker for it, but it slipped my mind to search for this one. I'm glad to see that it has been patched and look forward to the next 2.93 LTS release.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#90047
No description provided.