link render layer with visible bug #42016

New Issue

Alexey · 2014-09-29T21:22:14+02:00

Alexey commented

2014-09-29 21:22:14 +02:00

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.blend
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

System Information windows7 64 ASUS ATI Radeon HD6870 Blender Version Broken: (All) Worked: (2.72 is special case) ![lock_on1.png](https://archive.blender.org/developer/F113631/lock_on1.png) ![lock_on2.png](https://archive.blender.org/developer/F113633/lock_on2.png) ![lock_on3.png](https://archive.blender.org/developer/F113637/lock_on3.png) ![lock_on4.png](https://archive.blender.org/developer/F113639/lock_on4.png) ![lock_on5.png](https://archive.blender.org/developer/F113641/lock_on5.png) ![lock_on6.png](https://archive.blender.org/developer/F113643/lock_on6.png) **Exact steps for others to reproduce the error** [lock_on_scene.blend](https://archive.blender.org/developer/F113646/lock_on_scene.blend) 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

Alexey commented

2014-09-29 21:22:14 +02:00

Changed status to: 'Open'

Alexey commented

2014-09-29 21:22:14 +02:00

Added subscriber: @Inwader77

Bastien Montagne commented

2014-09-30 11:58:01 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2014-09-30 11:58:01 +02:00

Bastien Montagne self-assigned this 2014-09-30 11:58:01 +02:00

Bastien Montagne commented

2014-09-30 11:58:01 +02:00

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.

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 commented

2014-09-30 12:04:04 +02:00

Changed status from 'Archived' to: 'Archived'

Sergey Sharybin commented

2014-09-30 12:04:04 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2014-09-30 12:04:04 +02:00

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.

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.

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

link render layer with visible bug #42016