Bones Snapping #115456

Closed
opened 2023-11-27 01:12:14 +01:00 by Adam Earle · 5 comments

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.42

Blender Version
Broken: version: 4.0.1, branch: blender-v4.0-release, commit date: 2023-11-16 16:40, hash: d0dd92834a08
Worked: (newest version of Blender that worked as expected)

Short description of error
Bone is not snapping to a vertex point in space when the control key is held down and when the snap button is enabled.

Exact steps for others to reproduce the error
Create an armature.
make a bunch of bones.
Snap them along and curve and other bones any which way you can.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.42 **Blender Version** Broken: version: 4.0.1, branch: blender-v4.0-release, commit date: 2023-11-16 16:40, hash: `d0dd92834a08` Worked: (newest version of Blender that worked as expected) **Short description of error** Bone is not snapping to a vertex point in space when the control key is held down and when the snap button is enabled. **Exact steps for others to reproduce the error** Create an armature. make a bunch of bones. Snap them along and curve and other bones any which way you can.
Adam Earle added the
Type
Report
Severity
Normal
Status
Needs Triage
labels 2023-11-27 01:12:15 +01:00
Member

Hi, thanks for the report. Can confirm if pivot point is active element and snap target is set to center
cc @mano-wii

Hi, thanks for the report. Can confirm if pivot point is `active element` and snap target is set to `center` cc @mano-wii
Pratik Borhade added
Module
Modeling
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-11-27 05:08:09 +01:00
Author

This is working in 4.1 I just checked.

This is working in 4.1 I just checked.

Hi @AdamEarle,

According to the video, in 4.1 you are using the Median Point as the Center, while in 4.0 it is the Active Element.

There is no bug here, the Snap With Center option uses the Transform Pivot Point as the Snap Base Point.

In other words, you are moving this point that I marked yellow to the snapping point.
image

Hi @AdamEarle, According to the video, in 4.1 you are using the Median Point as the Center, while in 4.0 it is the Active Element. There is no bug here, the `Snap With` Center option uses the Transform Pivot Point as the Snap Base Point. In other words, you are moving this point that I marked yellow to the snapping point. ![image](/attachments/ceb1b5d3-2070-4e12-b8cf-71653704f6f4)
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2023-11-27 12:37:40 +01:00

However, the question remains: why is the active point not the selected point.
In fact, there may be a bug.

However, the question remains: why is the active point not the selected point. In fact, there may be a bug.
Blender Bot added
Status
Needs Triage
and removed
Status
Archived
labels 2023-11-27 12:39:00 +01:00
Germano Cavalcante added
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-11-27 12:39:20 +01:00

The code that sets the Transform Pivot Point Active Element as being the "Head" of the Bone is explicit and has always worked like this:
https://projects.blender.org/blender/blender/src/branch/main/source/blender/editors/object/object_utils.cc#L65
https://projects.blender.org/blender/blender/src/branch/main/source/blender/editors/object/object_utils.cc#L110

This happens because a bone does not have an "Active element".
From the code we cannot know which "Element" was selected last (Head or Tail).
We can only know which bone is active:
https://projects.blender.org/blender/blender/src/branch/main/source/blender/editors/armature/armature_select.cc#L1121

I imagine this could be improved, but I don't think it is considered a bug given how long it's been working like this.
Cc. @dr.sybren

The code that sets the Transform Pivot Point `Active Element` as being the "Head" of the Bone is explicit and has always worked like this: https://projects.blender.org/blender/blender/src/branch/main/source/blender/editors/object/object_utils.cc#L65 https://projects.blender.org/blender/blender/src/branch/main/source/blender/editors/object/object_utils.cc#L110 This happens because a bone does not have an "Active element". From the code we **cannot** know which "Element" was selected last (Head or Tail). We can only know which bone is active: https://projects.blender.org/blender/blender/src/branch/main/source/blender/editors/armature/armature_select.cc#L1121 I imagine this could be improved, but I don't think it is considered a bug given how long it's been working like this. Cc. @dr.sybren
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2023-11-27 12:57:58 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
3 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#115456
No description provided.