Page MenuHome

Importing multilayer EXRs into compositor with animated view layers creates unexpected results.
Open, Needs Triage by DeveloperPublic


System Information
Operating system: Linux-4.4.0-161-generic-x86_64-with-debian-stretch-sid 64 Bits
Graphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 384.130

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: rBf6cb5f54494e
Worked: (optional)

Short description of error
All passes connected to my main View layer disappear when what was a View layer with an animated "Use for rendering" attribute, appears.

Exact steps for others to reproduce the error
Basically I in my original scene I created a "main" view layer, with several passes attached, and a "secondary" view layer, also with several passes attached. This "secondary" layer had its "use for rendering" attribute so that it would appear on frame 41 of 210.

The render went fine and opening these files in Nuke, with a layercontactsheet node attached, I see the "main" layer, with all its associated passes, and after frame 41, I see the additional "secondary" layer and all it's passes as well.

However, with a new scene in Blender the following happens;
In the compositor, add an image input and select the multilayer EXRs.
Attach a viewer to the main image output and select the "main" layer on the image node.
All the passes sockets are visible on the image node, until I scrub to frame 41, where the "main" layer enumerator changes to the "secondary" one and all sockets are visible still for all passes. But, if I change back to the "main" layer, I see it, but with only an image and alpha socket. All additional pass sockets have disappeared.

Without speculating, it feels like Blender, is having a trouble when an additional layer with passes suddenly appears in a sequence.



Event Timeline