Node info python path always uses bpy.data.node_groups collection #35720
Closed
opened 10 years ago by givingsights
·
12 comments
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#35720
Loading…
Reference in new issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
%%%--- Operating System, Graphics card ---
Testet on Win7 64bit
All recent builds produce that error
Error massage in console: (See attachement)
Traceback (most recent call last):
KeyError: 'bpy_prop_collection[key]: key "Compositing Nodetree" not found'
Change any node value of any node (of any nodetree).
Copy the last line from the command history into the console
Run the line. Now the error happens.
%%%
Changed status to: 'Open'
#48628 was marked as duplicate of this issue
blender/blender#37733 was marked as duplicate of this issue
%%%Looks like you are referring to the standard compositing node tree? This tree is not in bpy.data.node_groups, but is stored locally in Scene, i.e. you need to access it as
bpy.data.scenes["Scene"].node_tree.nodes["Value"].outputs- [x].default_value = 0.5
Only actual node groups are currently stored in bpy.data.node_groups. This is a legacy "feature" which is frequently causing trouble, but is not likely to be replaced any time soon. Using scene.node_tree works fine however for any scripting purpose. Closing this report.%%%
%%%Ah, after IRC discussion turns out the actual problem here is the data path generation in the info space, this produces bpy.data.node_groups for all node trees, even the integrated compo trees. Will look into that.%%%
%%%Unfortunately this is not nicely solvable. The RNA function responsible for constructing the ID path assumes a consistent behavior of ID data blocks, which material/scene/texture node trees break. In order to handle this we would have to pass a lot of extra arguments to RNA functions which would be very messy. Since it's not actually a critical bug (only used for report strings) i would rather accept it for now and keep as a ToDo. Eventually i'd like to get rid of nested ID data blocks, then this issue would disappear as well.%%%
Changed status from 'Open' to: 'Archived'
Changing Node Values not workingto Node info python path always uses bpy.data.node_groups collection 9 years agoAdded subscriber: @artfunkel
◀ Merged tasks: blender/blender#37733.
Added subscriber: @IsaacWeaver
Added subscriber: @p2or
Added subscriber: @Peter-Jackson