Mesh Parenting a Collection? #81666

Closed
opened 2020-10-13 03:10:39 +02:00 by Paul Muns · 4 comments

{F8984422}Status: ? Single line or paragraph human readable text.


Team
Commissioner: ? Core developer or artist, sign off the project, works as client.
Project leader: ? Main developer responsible for the implementation, only in one project.
Project members: - Optional other developers, can be in multiple projects at once.

Description
Big picture: ? Short text explaining the vision of the project.

Use cases:

  • ? Which specific scenarios will be tackled by the milestones .

Design:

  • ? Mental model, end user usability, paradigms, mockups.

Engineer plan:

  • ? Abstract code samples - linked here, UML, API guidelines, library changes.

Work plan

{icon check-circle color=green} Milestone 1 - optional name
Optional description of milestone.
Time estimate: ?

All existent tasks edited out (removed) since the milestone is fully done.

Milestone 2 - optional name
Optional description of milestone.
Time estimate: ?

    • Task or feature.
    • Task or feature.
  • . . .

Branch: - Existing patches or branches.


Relevant links:

  • -
    +++++++++
    +++++++++
    Shown in the Screen Capture is the current state of version 2.9 Collections. I can't find any information that says that a Mesh can Parent a Collection, but that's what needs to happen in my situation below. Otherwise I need to Drag every single object in Saddle Append to Horse mesh for Parenting (in Green).
    In Yellow, the objects inside AppendEye Collection have individually been dragged to Horse Mesh and Parented. Now they do move with the mesh but the presentation in my Collections is confusing with the same objects showing in two places.with some that can be selected and some not. This is the way all of the Saddle Append Collection objects will appear if I do it correctly and will, with a rather small number of objects create a blizzard of duplication that will soon become difficult to comprehend.
    Version 2.7 had its limitations but Parenting was not one of them. Without a way to allow a Mesh to Parent a Collection with a special marker or (Indention under the Mesh as in 2.7), even simple projects are going to become too complex and make the use of Collections a burden rather than a simplification.
{[F8984422](https://archive.blender.org/developer/F8984422/Parenting_Mess.png)}**Status:** `?` *Single line or paragraph human readable text.* --- **Team** **Commissioner:** `?` *Core developer or artist, sign off the project, works as client.* **Project leader:** `?` *Main developer responsible for the implementation, only in one project.* **Project members:** `-` *Optional other developers, can be in multiple projects at once.* **Description** **Big picture:** `?` *Short text explaining the vision of the project.* **Use cases**: * `?` *Which specific scenarios will be tackled by the milestones .* **Design:** * `?` *Mental model, end user usability, paradigms, mockups.* **Engineer plan:** * `?` *Abstract code samples - linked here, UML, API guidelines, library changes.* **Work plan** **{icon check-circle color=green} Milestone 1 - optional name** *Optional description of milestone.* Time estimate: `?` *All existent tasks edited out (removed) since the milestone is fully done.* **Milestone 2 - optional name** *Optional description of milestone.* Time estimate: `?` * - [x]*Task or feature.* * - [ ]*Task or feature.* * . . . **Branch**: `-` *Existing patches or branches.* --- **Relevant links**: * `-` +++++++++ +++++++++ Shown in the Screen Capture is the current state of version 2.9 Collections. I can't find any information that says that a Mesh can Parent a Collection, but that's what needs to happen in my situation below. Otherwise I need to Drag every single object in Saddle Append to Horse mesh for Parenting (in Green). In Yellow, the objects inside AppendEye Collection have individually been dragged to Horse Mesh and Parented. Now they do move with the mesh but the presentation in my Collections is confusing with the same objects showing in two places.with some that can be selected and some not. This is the way all of the Saddle Append Collection objects will appear if I do it correctly and will, with a rather small number of objects create a blizzard of duplication that will soon become difficult to comprehend. Version 2.7 had its limitations but Parenting was not one of them. Without a way to allow a Mesh to Parent a Collection with a special marker or (Indention under the Mesh as in 2.7), even simple projects are going to become too complex and make the use of Collections a burden rather than a simplification.
Author

Added subscriber: @PaulM44

Added subscriber: @PaulM44
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Aaron Carlisle self-assigned this 2020-10-13 05:55:24 +02:00
Member

Thanks for the report, but please use other channels for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Thanks for the report, but please use other channels for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
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
2 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#81666
No description provided.