Snap vertices with "Closest" is not acting as expected #79556

Open
opened 2020-08-05 16:31:56 +02:00 by Georges Dahdouh · 21 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00

Blender Version
Broken: version: 2.83.3, branch: master, commit date: 2020-07-22 06:01, hash: 353e5bd749
Worked: 2.82a at least. Didn't check any 2.83 releases.

Short description of error
Snapping to vertex when moving with "Closest" works as if "Center" is chosen when moving several vertices at once.cubicle.blend

Exact steps for others to reproduce the error

  • In the attached file, go to edit mode with the selected cubic shape.
  • 3 vertices already selected, try to move them down on Z axis with snap to vertices, "Closest".
  • The expected behavior is that the vertex at the bottom among the 3 selected vertices, should be at the same position of the vertex I'm snapping to.

#46892 (Snapping closest vertex with Pivot point set to Individual Origins)

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00 **Blender Version** Broken: version: 2.83.3, branch: master, commit date: 2020-07-22 06:01, hash: `353e5bd749` Worked: 2.82a at least. Didn't check any 2.83 releases. **Short description of error** Snapping to vertex when moving with "Closest" works as if "Center" is chosen when moving several vertices at once.[cubicle.blend](https://archive.blender.org/developer/F8748594/cubicle.blend) **Exact steps for others to reproduce the error** - In the attached file, go to edit mode with the selected cubic shape. - 3 vertices already selected, try to move them down on Z axis with snap to vertices, "Closest". - The expected behavior is that the vertex at the bottom among the 3 selected vertices, should be at the same position of the vertex I'm snapping to. #46892 (Snapping closest vertex with Pivot point set to Individual Origins)

Added subscriber: @GeorgesDahdouh

Added subscriber: @GeorgesDahdouh
Georges Dahdouh changed title from Snap vertices with "Closes" is not acting as expected to Snap vertices with "Closest" is not acting as expected 2020-08-05 16:32:33 +02:00
Contributor

Added subscriber: @Gilberto.R

Added subscriber: @Gilberto.R
Contributor

Changing the Pivot Point from "individual origins" to any other option makes it behave as expected. Also I can reproduce this issue in 2.90 beta.

Changing the Pivot Point from "individual origins" to any other option makes it behave as expected. Also I can reproduce this issue in 2.90 beta.

Added subscriber: @Pasang

Added subscriber: @Pasang

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

Changed status from 'Needs Triage' to: 'Archived'
Pasang Bomjan self-assigned this 2020-08-06 09:51:21 +02:00

This is not a bug. When you choose the pivot point as "Individual Origin", the transformation acts on individual pieces of elements. Then when you Snap with the 'Closest', the polygon which is closest will be snapped
It has always worked this way. If you're still confused, I can show you the practical cases.

This is not a bug. When you choose the pivot point as "Individual Origin", the transformation acts on individual pieces of elements. Then when you Snap with the 'Closest', the polygon which is closest will be snapped It has always worked this way. If you're still confused, I can show you the practical cases.
Contributor

Added subscriber: @mano-wii

Added subscriber: @mano-wii
Contributor

No, to me it isn't working as expected. @mano-wii can you please have a look?

No, to me it isn't working as expected. @mano-wii can you please have a look?
Contributor

@Pasang you should let a developer triage this.

@Pasang you should let a developer triage this.

Can you show me the video where it worked before? I'd like to see it. 😃

Can you show me the video where it worked before? I'd like to see it. 😃
Contributor

Seems like it's broken since 2.79. This behavior is not documented. Documentation says it snaps the closest vertex, it doesn't say "it snaps the closest object center instead depending on pivot point"... If this was to be a feature, it would be added as a snapping option, not a pivot point dependent thing. So please reopen the task @Pasang let the developer have his opinion if this is really a bug or something that needs documentation.

Seems like it's broken since 2.79. This behavior is not documented. Documentation says it snaps the closest vertex, it doesn't say "it snaps the closest object center instead depending on pivot point"... If this was to be a feature, it would be added as a snapping option, not a pivot point dependent thing. So please reopen the task @Pasang let the developer have his opinion if this is really a bug or something that needs documentation.

Now the task is closed already, only a developer can reopen it. If you think I may have made a mistake then you can create a new task showing how it used to work. :)

Now the task is closed already, only a developer can reopen it. If you think I may have made a mistake then you can create a new task showing how it used to work. :)
Pasang Bomjan was unassigned by Ankit Meel 2020-08-07 23:13:03 +02:00
Member

Changed status from 'Archived' to: 'Confirmed'

Changed status from 'Archived' to: 'Confirmed'

The target is calculated based on the center of the elements involved.
With the Individual Origin option enabled, the center of the transformed elements is the center of the island to which it belongs.
It has always worked that way, but maybe it is time to change that behavior.
I will analyze it a little more to see if there is any disadvantage in changing this behavior.

The target is calculated based on the center of the elements involved. With the `Individual Origin` option enabled, the center of the transformed elements is the center of the island to which it belongs. It has always worked that way, but maybe it is time to change that behavior. I will analyze it a little more to see if there is any disadvantage in changing this behavior.
Germano Cavalcante self-assigned this 2020-08-08 01:37:44 +02:00

I will analyze it a little more to see if there is any disadvantage in changing this behavior.

Here's the use case.
20200808_124736.mp4

> I will analyze it a little more to see if there is any disadvantage in changing this behavior. Here's the use case. [20200808_124736.mp4](https://archive.blender.org/developer/F8758174/20200808_124736.mp4)
Contributor

@Pasang , for consistency sake of course. Changing the number of selected islands or changing the pivot point shouldn't alter the snapping option behavior. Snapping with "Closest" has a defined meaning, which is snapping the closest vertex, not "the closest island's center sometimes". The way it is, with the snapping being different depending on pivot point, makes users very stressed and confused, it feels like snap is broken. If snapping closest island center behavior is to be a feature, it should be a snapping option, not a pivot point dependent thing. Having the user's suffer until they learn behavior exceptions in features is not good design. Features should be consistent and intuitive. Behavior inconsistencies will only make people more reliant on the manual or come bug report. To me snap with closest should always mean snapping with closest vertex and something else should be something else.

@Pasang , for consistency sake of course. Changing the number of selected islands or changing the pivot point shouldn't alter the snapping option behavior. Snapping with "Closest" has a defined meaning, which is snapping the closest vertex, not "the closest island's center sometimes". The way it is, with the snapping being different depending on pivot point, makes users very stressed and confused, it feels like snap is broken. If snapping closest island center behavior is to be a feature, it should be a snapping option, not a pivot point dependent thing. Having the user's suffer until they learn behavior exceptions in features is not good design. Features should be consistent and intuitive. Behavior inconsistencies will only make people more reliant on the manual or come bug report. To me snap with closest should always mean snapping with closest vertex and something else should be something else.

@Gilberto.R, sorry for being a jerk earlier 😀.
I agree that there should be more options like closest edge, closest face, closest island and that the closest point should snap the closest vert no matter the pivot point.

@Gilberto.R, sorry for being a jerk earlier 😀. I agree that there should be more options like **closest edge, closest face, closest island** and that the **closest point** should snap the closest vert no matter the pivot point.

Added subscriber: @georgK

Added subscriber: @georgK
Contributor

@mano-wii Though it doesn't work in 2.79, I just found that this worked fine in much earlier versions.
Open blender 2.49b.
Tab to edit mode.
Duplicate cube and move it
Turn on Snapping
Change pivot point to "Individual Centers"
Snapping will still snap with closest. So no Bug there. The bug is that in current versions when you change the pivot to "Individual Origins", snap uses the nearest island center for snapping instead of using the closest point.

also no bug on version 2.59.

@mano-wii Though it doesn't work in 2.79, I just found that this worked fine in much earlier versions. Open blender 2.49b. Tab to edit mode. Duplicate cube and move it Turn on Snapping Change pivot point to "Individual Centers" Snapping will still snap with closest. So no Bug there. The bug is that in current versions when you change the pivot to "Individual Origins", snap uses the nearest island center for snapping instead of using the closest point. also no bug on version 2.59.

@Gilberto.R, thank you for the info, but we still need to look for the reason that these changes were made.
I feel like changing this now is a long shot.

@Gilberto.R, thank you for the info, but we still need to look for the reason that these changes were made. I feel like changing this now is a long shot.

Added subscriber: @sgariepy.3d

Added subscriber: @sgariepy.3d
Philipp Oeser removed the
Interest
Modeling
label 2023-02-09 15:29:03 +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
7 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#79556
No description provided.