Render layers not rendered correctly with Blender Render (2.78) #49236

Closed
opened 2016-09-03 11:55:06 +02:00 by soulfire · 6 comments

blender-2.78-ad40000-win64

renderlayer.blend
If I render the scene in Blender Render with 2 separate layers, result is
rl1.jpg

If I switch to Cycles with Film set totransparent, result is rendered normally
rl1cycles.jpg

As if material and light info is not rendered correctly when merging 2 layers in Blender Render.

EDIT:
https://blenderartists.org/forum/showthread.php?406044-Render-layers-not-combined-properly

blender-2.78-ad40000-win64 [renderlayer.blend](https://archive.blender.org/developer/F351235/renderlayer.blend) If I render the scene in Blender Render with 2 separate layers, result is ![rl1.jpg](https://archive.blender.org/developer/F351231/rl1.jpg) If I switch to Cycles with **Film** set to**transparent**, result is rendered normally ![rl1cycles.jpg](https://archive.blender.org/developer/F351233/rl1cycles.jpg) As if material and light info is not rendered correctly when merging 2 layers in Blender Render. EDIT: https://blenderartists.org/forum/showthread.php?406044-Render-layers-not-combined-properly
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @TomG

Added subscriber: @TomG

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2016-09-04 12:40:45 +02:00

Blender Internal and Cycles indeed behave differently here. I made Cycles behave different because I think it makes more sense this way, if you want consistent behavior between lights and meshes emitting or bouncing light.

Changing Blender Internal would break backwards compatibility, and many existing .blend files would stop working. It is possible to do such changes for example in Blender 2.8x, but what will happen with Blender Internal in that version is still to be decided. In any case it's not strictly a bug, but a design that could be improved or modified.

Blender Internal and Cycles indeed behave differently here. I made Cycles behave different because I think it makes more sense this way, if you want consistent behavior between lights and meshes emitting or bouncing light. Changing Blender Internal would break backwards compatibility, and many existing .blend files would stop working. It is possible to do such changes for example in Blender 2.8x, but what will happen with Blender Internal in that version is still to be decided. In any case it's not strictly a bug, but a design that could be improved or modified.
Author

In #49236#389548, @brecht wrote:
Blender Internal and Cycles indeed behave differently here. I made Cycles behave different because I think it makes more sense this way, if you want consistent behavior between lights and meshes emitting or bouncing light.

Changing Blender Internal would break backwards compatibility, and many existing .blend files would stop working. It is possible to do such changes for example in Blender 2.8x, but what will happen with Blender Internal in that version is still to be decided. In any case it's not strictly a bug, but a design that could be improved or modified.

Yes, please, could you modify/improve this render layers feature for BR in future releases?

Could you explain how render layers work differently in BR versus Cycles?
How come lights and materials on render layer 1 do not affect render layer 2 (Blender Internal)?

Please keep/improve Blender Render (Internal) in 2.8x for it's unique raster engine.

> In #49236#389548, @brecht wrote: > Blender Internal and Cycles indeed behave differently here. I made Cycles behave different because I think it makes more sense this way, if you want consistent behavior between lights and meshes emitting or bouncing light. > > Changing Blender Internal would break backwards compatibility, and many existing .blend files would stop working. It is possible to do such changes for example in Blender 2.8x, but what will happen with Blender Internal in that version is still to be decided. In any case it's not strictly a bug, but a design that could be improved or modified. Yes, please, could you modify/improve this render layers feature for BR in future releases? Could you explain how render layers work differently in BR versus Cycles? How come lights and materials on render layer 1 do not affect render layer 2 (Blender Internal)? Please keep/improve Blender Render (Internal) in 2.8x for it's unique raster engine.
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
2 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#49236
No description provided.