Parenting object to a curve acts as if parenting to first curve point #98489

Closed
opened 2022-05-30 11:08:34 +02:00 by Demeter Dzadik · 14 comments
Member

Blender Version
Broken: version: 3.3.0 Alpha, branch: master, commit date: 2022-05-30 08:14, hash: fc3c589b18
Worked: Unknown

Short description of error
When parenting an object to a curve using very basic object parenting, it actually acts as if the object was parented to the first curve point, rather than the curve object itself.
So when moving the first curve point in edit mode, the object moves.

Exact steps for others to reproduce the error

  • Add a Bezier Curve
  • Parent default cube to the curve with Ctrl+P->Object
  • Enter edit mode in the curve
  • Any operations here shouldn't affect the child object (the default cube), but moving the first curve point moves the cube.
  • The relationship line between the cube and the curve also indicate that the cube is parented to the first curve point, rather than the curve object's origin.

curve_parenting-2022-05-30_11.02.44.mp4

**Blender Version** Broken: version: 3.3.0 Alpha, branch: master, commit date: 2022-05-30 08:14, hash: `fc3c589b18` Worked: Unknown **Short description of error** When parenting an object to a curve using very basic object parenting, it actually acts as if the object was parented to the first curve point, rather than the curve object itself. So when moving the first curve point in edit mode, the object moves. **Exact steps for others to reproduce the error** - Add a Bezier Curve - Parent default cube to the curve with Ctrl+P->Object - Enter edit mode in the curve - Any operations here shouldn't affect the child object (the default cube), but moving the first curve point moves the cube. - The relationship line between the cube and the curve also indicate that the cube is parented to the first curve point, rather than the curve object's origin. [curve_parenting-2022-05-30_11.02.44.mp4](https://archive.blender.org/developer/F13122648/curve_parenting-2022-05-30_11.02.44.mp4)
Author
Member

Added subscriber: @Mets

Added subscriber: @Mets
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

It is a bit weird, but this still uses Path Animation setting from the curve (check the curve data panel):

  • if this option is ON it follows the path (not the first point, not the last point, this depends on the Evaluation Time)
  • if this is OFF, you'll get "regular" object only parenting behavior

Not really a bug, might be worth checking if this is something that is in need of some rethinking?
Makes sense? If so, would vote for not keeping this in the tracker though

It is a bit weird, but this still uses `Path Animation` setting from the curve (check the curve data panel): - if this option is ON it follows the path (not the first point, not the last point, this depends on the `Evaluation Time`) - if this is OFF, you'll get "regular" object only parenting behavior Not really a bug, might be worth checking if this is something that is in need of some rethinking? Makes sense? If so, would vote for not keeping this in the tracker though
Member

Added subscriber: @SimonThommes

Added subscriber: @SimonThommes
Member

There is no good reason imo to have object parenting work differently for curves when there are such things as constraints to achieve the same thing. There is a series of other hidden functionalities baked into the curve object.

This behaviour will thankfully just go away with the new curves object type. So for the time being, I guess, as this is not a bug the report can be archived.

There is no good reason imo to have object parenting work differently for curves when there are such things as constraints to achieve the same thing. There is a series of other hidden functionalities baked into the curve object. This behaviour will thankfully just go away with the new curves object type. So for the time being, I guess, as this is not a bug the report can be archived.
Author
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Author
Member

While playing around with it a bit more, I also discovered something that looks more like a bug:

But this whole thing is such a mess that I wouldn't want anyone to waste time actually trying to fix it, as long as this is on the radar of the guys making the new Curves objects, all will be well. I also didn't even mention yet how the secret setting of the parent inverse matrix when using Ctrl+P is a massive and unnecessary pitfall.

"This is the dumbest thing."

This was the reaction when @SimonThommes (who originally discovered this) showed the original issue to Hans, so I'd leave it up to him if this should be closed as not-a-bug or converted/re-made as a design task on how Path Animation should work for the new Curves object type.

While playing around with it a bit more, I also discovered something that looks more like a bug: - Disable Path Animation - Parent object - Enable Path Animation - Child object doesn't update in real-time (missing dependency I guess) [curve_madness-2022-05-30_12.16.38.mp4](https://archive.blender.org/developer/F13122748/curve_madness-2022-05-30_12.16.38.mp4) But this whole thing is such a mess that I wouldn't want anyone to waste time actually trying to fix it, as long as this is on the radar of the guys making the new Curves objects, all will be well. I also didn't even mention yet how the secret setting of the parent inverse matrix when using Ctrl+P is a massive and unnecessary pitfall. > "This is the dumbest thing." > - @HooglyBoogly This was the reaction when @SimonThommes (who originally discovered this) showed the original issue to Hans, so I'd leave it up to him if this should be closed as not-a-bug or converted/re-made as a design task on how Path Animation should work for the new Curves object type.
Member

I made a design task about simplifying this area and updating it to use the new curves type: #98494

So I think I'll close this, since that task describes how to improve the issues here on a design level.

I made a design task about simplifying this area and updating it to use the new curves type: #98494 So I think I'll close this, since that task describes how to improve the issues here on a design level.
Member

Closed as duplicate of #98494

Closed as duplicate of #98494
Member

Changed status from 'Duplicate' to: 'Needs Developer To Reproduce'

Changed status from 'Duplicate' to: 'Needs Developer To Reproduce'
Member

In #98489#1366491, @Mets wrote:
While playing around with it a bit more, I also discovered something that looks more like a bug:

True. the following would update dependencies but not take care of correcting the parent matrix since for that the RNA callback would need to walk over objects to find all possible children I think... (but strictly speaking, this would need to be reported separately -- and then again there seems to be consensus to not spend time on this?)
P2982: T98489_snippet



diff --git a/source/blender/makesrna/intern/rna_curve.c b/source/blender/makesrna/intern/rna_curve.c
index 49b78e90024..ca87ba8b958 100644
--- a/source/blender/makesrna/intern/rna_curve.c
+++ b/source/blender/makesrna/intern/rna_curve.c
@@ -1007,7 +1007,7 @@ static void rna_def_path(BlenderRNA *UNUSED(brna), StructRNA *srna)
   prop = RNA_def_property(srna, "use_path", PROP_BOOLEAN, PROP_NONE);
   RNA_def_property_boolean_sdna(prop, NULL, "flag", CU_PATH);
   RNA_def_property_ui_text(prop, "Path", "Enable the curve to become a translation path");
-  RNA_def_property_update(prop, 0, "rna_Curve_update_data");
+  RNA_def_property_update(prop, 0, "rna_Curve_update_deps");
 
   prop = RNA_def_property(srna, "use_path_follow", PROP_BOOLEAN, PROP_NONE);
   RNA_def_property_boolean_sdna(prop, NULL, "flag", CU_FOLLOW);
> In #98489#1366491, @Mets wrote: > While playing around with it a bit more, I also discovered something that looks more like a bug: True. the following would update dependencies but not take care of correcting the parent matrix since for that the RNA callback would need to walk over objects to find all possible children I think... (but strictly speaking, this would need to be reported separately -- and then again there seems to be consensus to not spend time on this?) [P2982: T98489_snippet](https://archive.blender.org/developer/P2982.txt) ``` diff --git a/source/blender/makesrna/intern/rna_curve.c b/source/blender/makesrna/intern/rna_curve.c index 49b78e90024..ca87ba8b958 100644 --- a/source/blender/makesrna/intern/rna_curve.c +++ b/source/blender/makesrna/intern/rna_curve.c @@ -1007,7 +1007,7 @@ static void rna_def_path(BlenderRNA *UNUSED(brna), StructRNA *srna) prop = RNA_def_property(srna, "use_path", PROP_BOOLEAN, PROP_NONE); RNA_def_property_boolean_sdna(prop, NULL, "flag", CU_PATH); RNA_def_property_ui_text(prop, "Path", "Enable the curve to become a translation path"); - RNA_def_property_update(prop, 0, "rna_Curve_update_data"); + RNA_def_property_update(prop, 0, "rna_Curve_update_deps"); prop = RNA_def_property(srna, "use_path_follow", PROP_BOOLEAN, PROP_NONE); RNA_def_property_boolean_sdna(prop, NULL, "flag", CU_FOLLOW); ```
Member

Oops, was too slow

Oops, was too slow
Member

Closed as duplicate of #98494

Closed as duplicate of #98494
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#98489
No description provided.