Append NodeTree also Appends Object #69508

Closed
opened 2019-09-04 22:42:39 +02:00 by Craig Jones · 9 comments

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: AMD Radeon R7 450 ATI Technologies Inc. 4.5.13521 Core Profile Context 24.20.11020.3002

Blender Version
Broken: version: 2.81 (sub 5), branch: master, commit date: 2019-09-03 12:35, hash: 51d8facbc3
Worked: (optional)

Short description of error
I tried appending a complex node tree into my new build to play with, and noticed that along with the group node, I got the original object from the file as well - the whole mesh object came into my 3d view. I'm used to it only bringing in the material or node tree.

Exact steps for others to reproduce the error

  1. Create a node group in a single file, make it fake user and save.
  2. Open new file, Append and navigate to the previous file - search for the node tree and append.
  3. If the node tree is still attached to an object, I am getting the mesh object in view.
    [Based on the default startup or an attached .blend file (as simple as possible)]
**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: AMD Radeon R7 450 ATI Technologies Inc. 4.5.13521 Core Profile Context 24.20.11020.3002 **Blender Version** Broken: version: 2.81 (sub 5), branch: master, commit date: 2019-09-03 12:35, hash: `51d8facbc3` Worked: (optional) **Short description of error** I tried appending a complex node tree into my new build to play with, and noticed that along with the group node, I got the original object from the file as well - the whole mesh object came into my 3d view. I'm used to it only bringing in the material or node tree. **Exact steps for others to reproduce the error** 1. Create a node group in a single file, make it fake user and save. 2. Open new file, Append and navigate to the previous file - search for the node tree and append. 3. If the node tree is still attached to an object, I am getting the mesh object in view. [Based on the default startup or an attached .blend file (as simple as possible)]
Author

Added subscriber: @CraigJones

Added subscriber: @CraigJones
Member

Added subscriber: @BrendonMurphy

Added subscriber: @BrendonMurphy
Member

hi @CraigJones could you check the node tree for Texture Coordinate
texture_grab_object.jpg
If there's an Object listed in the Object field, I found that it seems to get stored with the node data somehow and the object can seem to tag along with appends. Possibly this is the cause. It seems to be an expected although unusual behavior I think.

hi @CraigJones could you check the node tree for Texture Coordinate ![texture_grab_object.jpg](https://archive.blender.org/developer/F7717798/texture_grab_object.jpg) If there's an Object listed in the Object field, I found that it seems to get stored with the node data somehow and the object can seem to tag along with appends. Possibly this is the cause. It seems to be an expected although unusual behavior I think.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

I also cannot reproduce (other than the situation @BrendonMurphy described).
If it is not the object sticking in the Texture Coordinate Node [which is not a bug], please post the .blend containing the NodeTree in question...

I also cannot reproduce (other than the situation @BrendonMurphy described). If it is not the object sticking in the Texture Coordinate Node [which is not a bug], please post the .blend containing the NodeTree in question...
Author

Yes, this is the case - the object that owns the node tree is also referenced as the object there in the texture coordinate.

Yes, this is the case - the object that owns the node tree is also referenced as the object there in the texture coordinate.

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2019-09-16 22:00:08 +02:00

This is perfectly sane and expected behavior, since the nodetree uses/depends on the object, that one is also linked/appended. Thanks for the report, but no bug here.

This is perfectly sane and expected behavior, since the nodetree uses/depends on the object, that one is also linked/appended. Thanks for the report, but no bug here.
Sign in to join this conversation.
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
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#69508
No description provided.