Axis-constrained snapping to an object with Shrinkwrap modifier is broken #99051

Closed
opened 2022-06-21 13:52:00 +02:00 by slowburn · 8 comments

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79

Blender Version
Broken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: e05e1e3691
Worked: ?

Short description of error
Using axis-constrained edge or face snapping onto an object affected by Shrinkwrap modifier is really buggy and will often transform to a wrong location. The object has to be actually deformed by the Shrinkwrap. Edge snapping is broken with 1or 2 axis constrained, while face snapping only with one axis.

snapping_bug.mp4
Exact steps for others to reproduce the error

Use the provided file
Snap to shrinkwrap.blend1

  • Enable edge or face snapping
  • Move the cube on 1 or 2 axes
  • Try snapping onto the subdivided plane
**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79 **Blender Version** Broken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: `e05e1e3691` Worked: ? **Short description of error** Using axis-constrained edge or face snapping onto an object affected by Shrinkwrap modifier is really buggy and will often transform to a wrong location. The object has to be actually deformed by the Shrinkwrap. Edge snapping is broken with 1or 2 axis constrained, while face snapping only with one axis. [snapping_bug.mp4](https://archive.blender.org/developer/F13212049/snapping_bug.mp4) **Exact steps for others to reproduce the error** Use the provided file [Snap to shrinkwrap.blend1](https://archive.blender.org/developer/F13212045/Snap_to_shrinkwrap.blend1) - Enable edge or face snapping - Move the cube on 1 or 2 axes - Try snapping onto the subdivided plane
Author

Added subscriber: @slowburn

Added subscriber: @slowburn
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

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

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

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'

This is not a bug.
Snapping with constraint is done to the intersection with the extent of geometry. See D5608: Transform: Snap to the intersection between the constraint and the geometry
There is a threshold angle for this intersection to be made. In the attached file this threshold has been reached.

If you don't want this behavior, it's best not to snap, as there's not much use snapping to an undefined point of an edge or face.

This is not a bug. Snapping with constraint is done to the intersection with the extent of geometry. See [D5608: Transform: Snap to the intersection between the constraint and the geometry](https://archive.blender.org/developer/D5608) There is a threshold angle for this intersection to be made. In the attached file this threshold has been reached. If you don't want this behavior, it's best not to snap, as there's not much use snapping to an undefined point of an edge or face.
Author

In that case, could you add a toggle to disable intersection snapping, because it ruins snapping in certain situations that are quite common.

In that case, could you add a toggle to disable intersection snapping, because it ruins snapping in certain situations that are quite common.

Polluted interface with too many options is something to avoid.
It was decided that for this feature it is better to always keep it active.

For many different cases, this feature has proved more useful than inconvenient.

It is actually more appropriate to disable snapping altogether than snapping to the region closest to an undefined point of a face or edge.

Polluted interface with too many options is something to avoid. It was decided that for this feature it is better to always keep it active. For many different cases, this feature has proved more useful than inconvenient. It is actually more appropriate to disable snapping altogether than snapping to the region closest to an undefined point of a face or edge.
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
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#99051
No description provided.