Render Result showing the wrong renderlayer in image editor #53971

New Issue

Mike Pan · 2018-02-01T08:09:25+01:00

Mike Pan commented

2018-02-01 08:09:25 +01:00

Blender Version
Broken: 2.79 official, also tested on latest master.

Short description of error
When rendering with 'Only render active layer' enabled in the renderlayer panel, the image editor switches to a seemingly random renderlayer when rendering is finished, instead of showing the active renderlayer.

Exact steps for others to reproduce the error

Open Blend file attached and hit F12
Select another render and render again.
Repeat #2 a few times and notice that the image editor starts to show you a random renderlayer in the stack, instead of the one you are rendering.

renderlayer.blend

**Blender Version** Broken: 2.79 official, also tested on latest master. **Short description of error** When rendering with 'Only render active layer' enabled in the renderlayer panel, the image editor switches to a seemingly random renderlayer when rendering is finished, instead of showing the active renderlayer. **Exact steps for others to reproduce the error** 1. Open Blend file attached and hit F12 2. Select another render and render again. 3. Repeat #2 a few times and notice that the image editor starts to show you a random renderlayer in the stack, instead of the one you are rendering. [renderlayer.blend](https://archive.blender.org/developer/F2068499/renderlayer.blend)

Mike Pan commented

2018-02-01 08:09:25 +01:00

Added subscriber: @MikePan

ronan ducluzeau commented

2018-02-01 17:43:53 +01:00

Added subscriber: @zeauro

ronan ducluzeau commented

2018-02-01 17:43:53 +01:00

confirmed on 2.79 and master under ubuntu 16.04

Problem seems to occur for both render engines BI and Cycles.

confirmed on 2.79 and master under ubuntu 16.04 Problem seems to occur for both render engines BI and Cycles.

Oliver Weissbarth commented

2018-02-22 19:35:04 +01:00

Added subscriber: @oweissbarth

Cheryl Chen commented

2018-03-06 23:02:39 +01:00

Added subscriber: @chnchryl

Cheryl Chen commented

2018-03-06 23:02:39 +01:00

Hi there, I'm new to this, but I've been poking around with this bug to find my way around. From what I gather, the displayed render-layer is affected by the value of ‘iuser->layer’ in ‘uiblock_layer_pass_buttons’, which displays the rendered layer corresponding to the index of ‘iuser->layer’. It's set to 1 initially, so when multiple layers are rendered consecutively, it keeps displaying the second layer in the rendered stack. (If there isn't a layer at that index, it'll just display the closest one.) If you select a different layer to be displayed in the image editor, ‘iuser->layer’ is properly updated to that layer's index, and then it'll keep displaying the render layer at that index until you set another layer.

I think the issue is that ‘iuser->layer’ is only directly affected by the selected layer in the image editor, but not the layer that is being rendered. A possible fix could be to update ‘iuser->layer’ to the selected render layer, particularly when ‘Only render active layer' is enabled? Or maybe have the displayed layer be directly affected by the layer that was last rendered…Anyway, I’ll poke around a bit more and see if I can find a work-around.

Hi there, I'm new to this, but I've been poking around with this bug to find my way around. From what I gather, the displayed render-layer is affected by the value of ‘iuser->layer’ in ‘uiblock_layer_pass_buttons’, which displays the rendered layer corresponding to the index of ‘iuser->layer’. It's set to 1 initially, so when multiple layers are rendered consecutively, it keeps displaying the second layer in the rendered stack. (If there isn't a layer at that index, it'll just display the closest one.) If you select a different layer to be displayed in the image editor, ‘iuser->layer’ is properly updated to that layer's index, and then it'll keep displaying the render layer at that index until you set another layer. I think the issue is that ‘iuser->layer’ is only directly affected by the selected layer in the image editor, but not the layer that is being rendered. A possible fix could be to update ‘iuser->layer’ to the selected render layer, particularly when ‘Only render active layer' is enabled? Or maybe have the displayed layer be directly affected by the layer that was last rendered…Anyway, I’ll poke around a bit more and see if I can find a work-around.

Brecht Van Lommel commented

2018-03-07 00:15:54 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2018-03-07 00:15:54 +01:00

A possible fix could be to update ‘iuser->layer’ to the selected render layer, particularly when ‘Only render active layer' is enabled?

Yes, I think iuser->layer should be automatically set to the active render layer when "Only render active layer" is enabled. This means changing render_image_restore_layer() behavior.

> A possible fix could be to update ‘iuser->layer’ to the selected render layer, particularly when ‘Only render active layer' is enabled? Yes, I think `iuser->layer` should be automatically set to the active render layer when "Only render active layer" is enabled. This means changing `render_image_restore_layer()` behavior.

Cheryl Chen commented

2018-03-08 11:41:42 +01:00

Yes, I think iuser->layer should be automatically set to the active render layer when "Only render active layer" is enabled. This means changing render_image_restore_layer() behavior.

Thanks for the tip! I've got a working implementation now, but I'm not sure if it's the most efficient. I couldn't use render_get_active_layer(), since it seemed to be using the layer index corresponding to the full layer list on the list of only the rendered layers, which seems a bit strange? So it sometimes returns the wrong layer if not all layers are rendered yet. Right now, I'm getting the layer name from the list of all render layers, and then using that to find the string index in the rendered layer list, but that requires looping through both lists...
I'm also not sure how to check whether "Only render active layer" is used or not. I'm looking at RenderSettings_use_single_layer_get(), but it takes in a PointerRNA. Is there anything in RenderJob that holds that pointer? Thanks!

>Yes, I think iuser->layer should be automatically set to the active render layer when "Only render active layer" is enabled. This means changing render_image_restore_layer() behavior. Thanks for the tip! I've got a working implementation now, but I'm not sure if it's the most efficient. I couldn't use render_get_active_layer(), since it seemed to be using the layer index corresponding to the full layer list on the list of only the rendered layers, which seems a bit strange? So it sometimes returns the wrong layer if not all layers are rendered yet. Right now, I'm getting the layer name from the list of all render layers, and then using that to find the string index in the rendered layer list, but that requires looping through both lists... I'm also not sure how to check whether "Only render active layer" is used or not. I'm looking at RenderSettings_use_single_layer_get(), but it takes in a PointerRNA. Is there anything in RenderJob that holds that pointer? Thanks!

blender-admin commented

2018-03-15 23:36:15 +01:00

This issue was referenced by 07b07e53ea

This issue was referenced by 07b07e53ea0831ffb0c2a3aff0a33b40aa935c5c

Brecht Van Lommel commented

2018-03-16 01:03:59 +01:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2018-03-16 01:03:59 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Render Result showing the wrong renderlayer in image editor #53971