Curve Hook modifier broken due to selection changes #116402

Open
opened 2023-12-21 00:06:50 +01:00 by Jerry Miller · 13 comments

System Information
Operating system: Windows 10
Graphics card: 2x Nvidia GeForce RTX 2080 Supers

Blender Version
Broken: 4.0 onwards
Worked: 3.6
Caused by 618f39fca2

Short description of error
When adding a hook object to a curve object it behaves in an unpredictable manner.
This is due the changes in curve selection. Now handles are not selected along with the control point, hence the difference

Exact steps for others to reproduce the error

  • Open default scene -> add bezier curve
  • In edit mode, subdivide once
  • Select the middle control point (notice it's handles are not selected)
  • Hook to new object.

Possible solutions to implement: #116402 (comment)

  • Have additional menu items to add hooks to the vertex and it's handles, so there would be 3x menu items to add hooks with the knot, another 3x to add with knot & handles. (an awkward solution but lets to user access the previous default behavior without having to manually select the handles).
  • Add an operator option to include handles when adding a hook and enable it by default (users are likely to overlook this, making adding a hook to a single vertex more obscure).
  • Revert the change to selection behavior, so handles are always selected again (listing for completeness, I don't think it's a practical option).
**System Information** Operating system: Windows 10 Graphics card: 2x Nvidia GeForce RTX 2080 Supers **Blender Version** Broken: 4.0 onwards Worked: 3.6 Caused by 618f39fca2 **Short description of error** When adding a hook object to a curve object it behaves in an unpredictable manner. This is due the changes in curve selection. Now handles are not selected along with the control point, hence the difference **Exact steps for others to reproduce the error** - Open default scene -> add bezier curve - In edit mode, subdivide once - Select the middle control point (notice it's handles are not selected) - Hook to new object. - - - Possible solutions to implement: https://projects.blender.org/blender/blender/issues/116402#issuecomment-1097628 - Have additional menu items to add hooks to the vertex and it's handles, so there would be 3x menu items to add hooks with the knot, another 3x to add with knot & handles. _(an awkward solution but lets to user access the previous default behavior without having to manually select the handles)._ - Add an operator option to include handles when adding a hook and enable it by default _(users are likely to overlook this, making adding a hook to a single vertex more obscure)._ - Revert the change to selection behavior, so handles are always selected again _(listing for completeness, I don't think it's a practical option)._
Jerry Miller added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-12-21 00:06:51 +01:00
Member

Hi, thanks for the report. I'm not able to confirm as described. Hook object seems to affect the curve when moved in 4.0.x and 4.1
Could you verify with factory reset?: File > Defaults > Load Factory Settings

Hi, thanks for the report. I'm not able to confirm as described. Hook object seems to affect the curve when moved in 4.0.x and 4.1 Could you verify with factory reset?: `File > Defaults > Load Factory Settings`
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-12-21 06:12:33 +01:00
Author

Hi, thanks for the report. I'm not able to confirm as described. Hook object seems to affect the curve when moved in 4.0.x and 4.1
Could you verify with factory reset?: File > Defaults > Load Factory Settings

It's the movement of the curve specifically. In older blender files it would move and have smooth falloff. In 4.0+ its been doing a sharp movement. Plus the falloff on the hook modifier isn't changing anything.

I will do a Factory load and verify it is not just something on my end.... but it happens on my computer, my friends computer next to me and my friend in Brazil that confirmed its being strange.

> Hi, thanks for the report. I'm not able to confirm as described. Hook object seems to affect the curve when moved in 4.0.x and 4.1 > Could you verify with factory reset?: `File > Defaults > Load Factory Settings` It's the movement of the curve specifically. In older blender files it would move and have smooth falloff. In 4.0+ its been doing a sharp movement. Plus the falloff on the hook modifier isn't changing anything. I will do a Factory load and verify it is not just something on my end.... but it happens on my computer, my friends computer next to me and my friend in Brazil that confirmed its being strange.
Author

Hi, thanks for the report. I'm not able to confirm as described. Hook object seems to affect the curve when moved in 4.0.x and 4.1
Could you verify with factory reset?: File > Defaults > Load Factory Settings

I confirmed the problem is still there even after I loaded factory settings. My video in my last comment shows the same behavior that I see with 4.0 being different than the same process in 3.5 or any earlier versions.

confirmed the same issue in 4.0.3 release candidate from yesterday's daily build as well...

> Hi, thanks for the report. I'm not able to confirm as described. Hook object seems to affect the curve when moved in 4.0.x and 4.1 > Could you verify with factory reset?: `File > Defaults > Load Factory Settings` I confirmed the problem is still there even after I loaded factory settings. My video in my last comment shows the same behavior that I see with 4.0 being different than the same process in 3.5 or any earlier versions. confirmed the same issue in 4.0.3 release candidate from yesterday's daily build as well...
Member

I see, can confirm actually (but loading older file in 4.0 with hook did not trigger the issue, hence the confusion)

I see, can confirm actually (but loading older file in 4.0 with hook did not trigger the issue, hence the confusion)
Member

Strange, git bisect points to 618f39fca2
@ideasman42 ^

Strange, git bisect points to 618f39fca23ca7734a09a8f08efced8379efd2b3 @ideasman42 ^
Contributor

Sadly after some time of debugging it appeared there is nothing to fix.
@sage2014 in old version when you are assigning modifier control point and both handles are selected.
In 4.0 only control point is selected, thus moving Empty handles stay in old position giving sharp corner.
It can be observed in provided video.

Tried 3.6 version. Handles are selected automatically if control point is selected.
And it seems that it's not possible to select control point without selecting both handles.
I suspect that selection behavior in 4.0 is intentional.

Sadly after some time of debugging it appeared there is nothing to fix. @sage2014 in old version when you are assigning modifier control point and both handles are selected. In 4.0 only control point is selected, thus moving Empty handles stay in old position giving sharp corner. It can be observed in provided video. Tried 3.6 version. Handles are selected automatically if control point is selected. And it seems that it's not possible to select control point without selecting both handles. I suspect that selection behavior in 4.0 is intentional.
Contributor

@PratikPB2123 is it really a bug?

@PratikPB2123 is it really a bug? <video src="/attachments/b5496129-b81d-43a7-851e-4e837040cc92" title="hook.mov" controls></video>
5.8 MiB
Member

Thanks @laurynas . Indeed this is due to selection differences. :)
Curve selection in 4.0 is intentional as specified in the commit message: 90864d3fb8

Not sure whether to consider it a bug but it affects the previous workflow to some extent. I'll pass it to Campbell for the decision :)

Meanwhile, I'll check if this can be improved.

Thanks @laurynas . Indeed this is due to selection differences. :) Curve selection in 4.0 is intentional as specified in the commit message: 90864d3fb80ebebef0f90cc6d60e9eb01e665ba5 Not sure whether to consider it a bug but it affects the previous workflow to some extent. I'll pass it to Campbell for the decision :) Meanwhile, I'll check if this can be improved.
Author

@PratikPB2123 is it really a bug?

This video helps to show how to fix the issue I was having, however... I selected the control points the same way in both versions. Is it that in the new version, it simply doesn't select all the controls on the control points the same way?

Before, you'd just select the control point and it would automatically select both handles. now its as if you only select the control point but not the two handles.

Either way, the video helps to show how to move forward. I just wonder if this was intended change in blender 4.0 or if there might have been something that causes the two handles to not be selected? or if I just straight up did something wrong lol.

Thank you for the video and responses <3

> @PratikPB2123 is it really a bug? > <video src="/attachments/b5496129-b81d-43a7-851e-4e837040cc92" title="hook.mov" controls></video> This video helps to show how to fix the issue I was having, however... I selected the control points the same way in both versions. Is it that in the new version, it simply doesn't select all the controls on the control points the same way? Before, you'd just select the control point and it would automatically select both handles. now its as if you only select the control point but not the two handles. Either way, the video helps to show how to move forward. I just wonder if this was intended change in blender 4.0 or if there might have been something that causes the two handles to not be selected? or if I just straight up did something wrong lol. Thank you for the video and responses <3
Hans Goudey added
Status
Needs Info from Developers
and removed
Status
Confirmed
labels 2024-01-08 21:42:30 +01:00

It's understandable that the change in selection behavior causes the change when adding new hooks, I don't think there are especially good ways to resolve this.

Changing the default behavior (treating the handles as if they're selected for e.g.) makes it impossible to add the hook to a single handle - which users may want to do too.

Possible Solutions

Listing potential solutions, although I'm not keen on any of them.

  • Have additional menu items to add hooks to the vertex and it's handles, so there would be 3x menu items to add hooks with the knot, another 3x to add with knot & handles. (an awkward solution but lets to user access the previous default behavior without having to manually select the handles).
  • Add an operator option to include handles when adding a hook and enable it by default (users are likely to overlook this, making adding a hook to a single vertex more obscure).
  • Revert the change to selection behavior, so handles are always selected again (listing for completeness, I don't think it's a practical option).

More generally, we could have a shortcut for selecting a point and it's handles - since it can be useful at times. If this is supported, ideally all bezier curve editors (f-curve, mask... etc) would support this too.


Setting as a lower priority design task as it's possible to select 3 points before adding the hook.

It's understandable that the change in selection behavior causes the change when adding new hooks, I don't think there are especially good ways to resolve this. Changing the default behavior (treating the handles as if they're selected for e.g.) makes it impossible to add the hook to a single handle - which users may want to do too. ## Possible Solutions Listing potential solutions, although I'm not keen on any of them. - Have additional menu items to add hooks to the vertex and it's handles, so there would be 3x menu items to add hooks with the knot, another 3x to add with knot & handles. _(an awkward solution but lets to user access the previous default behavior without having to manually select the handles)._ - Add an operator option to include handles when adding a hook and enable it by default _(users are likely to overlook this, making adding a hook to a single vertex more obscure)._ - Revert the change to selection behavior, so handles are always selected again _(listing for completeness, I don't think it's a practical option)._ More generally, we could have a shortcut for selecting a point and it's handles - since it can be useful at times. If this is supported, ideally all bezier curve editors (f-curve, mask... etc) would support this too. ---- Setting as a lower priority design task as it's possible to select 3 points before adding the hook.
Campbell Barton added
Priority
Low
and removed
Priority
High
labels 2024-01-09 05:36:03 +01:00
Campbell Barton added
Type
Design
and removed
Type
Report
Status
Needs Info from Developers
labels 2024-01-09 05:37:45 +01:00
Campbell Barton pinned this 2024-01-09 05:37:45 +01:00
Campbell Barton added the
Status
Needs Information from User
label 2024-01-09 05:37:45 +01:00
Campbell Barton unpinned this 2024-01-09 05:37:52 +01:00
Member

Add an operator option to include handles when adding a hook and enable it by default

Maybe the second option ^
But answer from core users would help here (people in this thread or someone from the studio)

> Add an operator option to include handles when adding a hook and enable it by default Maybe the second option ^ But answer from core users would help here (people in this thread or someone from the studio)
Author

Add an operator option to include handles when adding a hook and enable it by default

Maybe the second option ^
But answer from core users would help here (people in this thread or someone from the studio)

Honestly if whatever was added to make it an optional toggle, that'd be great. I personally would like for it to be the same as how it has been before. This way guides or tutorials are still valid. Or at a bare minimum have something listed in the release notes or somewhere that states this functionality was changed somehow.

I know in the blender discord, we had our own custom bot that had user submitted guides for random things and this would cause a tiny bit of confusion.

> > Add an operator option to include handles when adding a hook and enable it by default > > Maybe the second option ^ > But answer from core users would help here (people in this thread or someone from the studio) Honestly if whatever was added to make it an optional toggle, that'd be great. I personally would like for it to be the same as how it has been before. This way guides or tutorials are still valid. Or at a bare minimum have something listed in the release notes or somewhere that states this functionality was changed somehow. I know in the blender discord, we had our own custom bot that had user submitted guides for random things and this would cause a tiny bit of confusion.
Pratik Borhade changed title from Curve Hook modifier broken? to Curve Hook modifier broken due to selection changes 2024-03-01 10:45:52 +01:00
Member

Made few tweaks in description, confirming again.

Made few tweaks in description, confirming again.
Pratik Borhade added
Status
Confirmed
and removed
Status
Needs Information from User
labels 2024-03-01 10:51:53 +01:00
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#116402
No description provided.