Regression: Compositor render layer node's outputs no longer update when modified from python #114234
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#114234
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 GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.58
Blender Version
Broken: version: 4.1.0 Alpha, branch: main, commit date: 2023-10-27 00:53, hash:
ce027579e02f
Worked: (previous 4.1.0 build and all builds before that)
Short description of error
Enabling passes of another scene via python no longer results in the current scene's render layers node for that scene getting the new output sockets.
It's strange, but it only appears to be an issue with the Vector pass, other passes that are updated via python get a socket on the render layer node without issue.
Exact steps for others to reproduce the error
Forcing region redraw with region.tag_redraw() does not resolve.
I've found that I can force the render layer node to update by assigning the same scene back to itself before trying to create links from the missing socket:
(URGENT) - Compositor render layer node's outputs no longer update when modified from pythonto Compositor render layer node's outputs no longer update when modified from pythonCompositor render layer node's outputs no longer update when modified from pythonto Regression: Compositor render layer node's outputs no longer update when modified from pythonRegression: Compositor render layer node's outputs no longer update when modified from pythonto (URGENT) Compositor render layer node's outputs no longer update when modified from python(URGENT) Compositor render layer node's outputs no longer update when modified from pythonto Regression: (URGENT) Compositor render layer node's outputs no longer update when modified from pythonRegression: (URGENT) Compositor render layer node's outputs no longer update when modified from pythonto Regression: Compositor render layer node's outputs no longer update when modified from pythonI can confirm the missing UI update, however (before diving deeper), I'd like to check on the following:
I cannot confirm that, I get the same (wrong) behavior in 3.6.5 even
@3di : Could you re-check?
Hi, thanks for looking. Yes I can confirm that the issue has never arisen prior to my first noticing it with 4.1.0. If it's now happening with 3.65 then that would indicate whatever code change has caused it, was also backported.
My addon was working without issue with all builds between 2.93 and 4.1 Alpha previously 👍 I was a bit stressed initially, because the addon is used by thousands of users, and is even in use by NASA and some major studios . I've managed to workaround it for now though, but would still be great if it could be fixed.
I get the behavior in 3.5.1 even...
I remade this file from scratch and i not able to reproduce this bug.
hmm, perhaps it previously was evident in the UI but python was still able to access the sockets. I'll do some further testing and create a new example file if necessary.
This is extremely strange.
I'm now not getting the issue with virtually identical code in the attached blend file, but I'm still getting the problem in the blend file I originally attached above.
bizarre!
Can you check if that is related with order of creating nodes/scene/something other?
I'm wondering if it might be an issue if the blend file was originally created in a different version of Blender. I can't remember if I had done that or not.
OK, I've been wracking my brain cell, and no matter what I do, I can't replicate the issue from script which is run from Blender's script editor.
So to demonstrate the problem, I've cut down my addon from 10,000 lines of code to around 200 (guessing).
Possibly caused by
e4ad58114b
?by the way, if you add a breakpoint prior to the line that throws the error, checking the render layer node for scene.001 will show you that according to python there is a socket present with name 'Vector' and also identifier 'Vector', so the commit above should find it via the identifier initially.