Compositor: Unexpected behaviour? #97385
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#97385
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
Operating system: Linux-5.13.0-39-generic-x86_64-with-glibc2.31 64 Bits, Ubuntu 20.04.4 LTS
Graphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01
Blender Version
Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-04-15 21:55, hash:
dc5ae10692Short description of error
It's hard to really explain what happens, because I'm not sure how to reproduce this behaviour reliably.
In the attached .blend file are some nodes in the compositor to create a rendered image with a gradient outline.
Unfortunately it worked just once in Blender 3.1.0, but then the viewer updated and it never showed this "gradient outline" again.
After this problem I switched to the latest Blender version. I experimented a bit and I am really confused. If the "Set Alpha" and "Viewer" are connected while rendering the result is (sometimes...) correct, but only in the rendered image. If I connect another node with "Viewer" or delete it, the rendered image shows just the cube. Here are a few screenshots I took while testing:
Screenshot 1 and 2: Viewer does not update when certain nodes are connected.
Here is also a node setup and the result where the rendering worked at least twice. On the third attempt, unfortunately, only the cube was visible again.:
And with this node setup, unfortunately, only the cube was rendered:
Exact steps for others to reproduce the error
Open the attached .blend file. Try to get viewer outputs from the different nodes. Try to render the file. Unfortunately, the errors do not really occur in a reliable way.
compositor_problem2.blend
So... I really hope, that this will help in some way.
Added subscriber: @SayDev
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Archived'
The compositor tries to guess the size of each of the outputs of your nodes, this may not be what you want in some cases, so you have to define that manually. In your case, adding a scale to render size node should fix the issue. But this is a consequence of the design of the compositor, not a bug.