Page MenuHome
Create Task
Maniphest T42016

link render layer with visible bug
Closed, ArchivedPublic
Actions

Description

System Information
windows7 64
ASUS ATI Radeon HD6870

Blender Version
Broken: (All)
Worked: (2.72 is special case)







Exact steps for others to reproduce the error
lock_on_scene.blend1 MBDownload

open this with 2.71(9337574)
select Cycles:
cursor position is not important press f12 - working normal
select Blender render:
don't set cursor to 3d view, f12 - working normal
set cursor to 3d view, f12 - working with bug
open with 84dfec7
(Cycles or BI is not important)
set cursor to 3d view f12 - working with bug
set cursor to any other window, f12 - working properly

Related Objects

Event Timeline

Alexey (Inwader77) created this task.Sep 29 2014, 9:22 PM
Alexey (Inwader77) raised the priority of this task from to 90.
Alexey (Inwader77) updated the task description. (Show Details)
Alexey (Inwader77) added projects: BF Blender, Cycles, Render Pipeline.
Alexey (Inwader77) edited a custom field.
Alexey (Inwader77) added a subscriber: Alexey (Inwader77).
Bastien Montagne (mont29) changed the task status from Unknown Status to Archived.Sep 30 2014, 11:58 AM
Bastien Montagne (mont29) claimed this task.

Thanks for the report, but there is no bug here, it’s feature. This behavior is intended, and it was a bug in Cycles in 2.71 and previous, that was fixed for 2.72.

The idea is that, when you call render op from the 3DView, you use layers from that 3DView. Else, you use layers from the scene.

Sergey Sharybin (sergey) changed the task status from Archived to Unknown Status.Sep 30 2014, 12:04 PM
Sergey Sharybin (sergey) added a subscriber: Sergey Sharybin (sergey).

In fact it was a bug in Cycles for quite a while. The thing is -- when viewport has local layers enabled (and not locked with the scene's one) viewport layers are to be used by the render engine when rendering is invoked from this viewport. This is by design. And it was made consistent in Cycles for 2.72.

Thanks for the report, but it's not a bug at all with BI.