Rendering only takes into account the render border of the current scene when compositing #46166
Labels
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#46166
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Windows 7 64-bit, Nvidia gtx570
Blender Version
Broken: 2.76
36d6424
Worked: -
Short description of error
I have two scenes, one with a cube in the top left of the camera's view and another scene with a cube in the bottom right of the camera's view. Each scene has a separate render border around that scene's cube. In one of the scenes I have compositing set up to render both scenes and lay them over each other (transparent background is enabled in one of the scenes to allow this). When I render the frame I find that both scenes are rendered using the render border of the current scene instead of taking into account each scene's individual render border, which means the final render appears blank (as the empty area of one scene is overlaid on the other).
This can be fixed, but only by pressing the render button on the render layer node for the scene that rendered incorrectly. When I do that, it uses the correct render border for that scene.
Not sure whether this is a bug or intended, but not what I personally expect.
Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps
Render border compositing multiple scenes.blend
Changed status to: 'Open'
Added subscriber: @RayMairlot
Added subscriber: @AntonStotzer
Added subscriber: @Sergey
Changed status from 'Open' to: 'Archived'
This is workign as designed and expected and in fact it's the only wayt you can have usable border render for scenarios when your scene is split into several render layers/scenes for the performance reasons.. For example, you might want ot render volumes in BI, rest of geometry in Cycles and combine them together. With your suggestion you'll need to change render border in every scene every time you want ot preview different area of your frame.
Soe thanks for the report, but it's not considered a bug.