Regression: Compositor Split node with only colors does not work (in 3DView, compositor backdrop is fine) #115780
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#115780
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: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.17
Blender Version
Broken: version: 4.1.0 Alpha, branch: main, commit date: 2023-12-04 01:28, hash:
92e8b7e85027
Worked: version: 4.1.0 Alpha, branch: main, commit date: 2023-12-02 19:08, hash:
8933284518a2
Likely caused by
153f14be2b
Short description of error
Compositor Split node with only colors no longer work.
Compositor Split node with only colors does not workto Regression: Compositor Split node with only colors does not workIt works as the Compositor Backdrop, but not in 3D View, so will confirm
Regression: Compositor Split node with only colors does not workto Regression: Compositor Split node with only colors does not work (in 3DView, compositor ackdrop is fine)Regression: Compositor Split node with only colors does not work (in 3DView, compositor ackdrop is fine)to Regression: Compositor Split node with only colors does not work (in 3DView, compositor backdrop is fine)@zazizizou ^
Thanks for the report. This was intentional. The Fullframe compositor also behaves the same way. But this seems to be perceived as a bug / non desired behavior, so I will change it to match the Tiled compositor.
@zazizizou I don't think we should change it for now. The node is no longer a viewer and should not depend on global information like the render size.
@OmarEmaraDev but the expectation seems to be that unconnected input behaves the same way as connected input with an image of same color.
For example, would you expect those two setups to behave the same?
Linked:
Unlinked
I wouldn't expect them to behave the same, since the unlinked one is doing size inference, which is the opposite of what we are trying to do in #115733.
The only issue here is that versioning will not work for unliked sockets, which can try to fix, but it doesn't seem worth it.
@persun Do you have a practical use case in mind where the behavior you describe is useful? Otherwise I'd suggest to close this report...
@zazizizou I just felt that it works differently with the expectation. I think most use cases people can think with this can be done with some math or the texture node (or upcoming texture nodes support).
But I think this at least warrants a note in the manual.
Thanks for taking a look!
@persun ok, thanks for testing!