No snapping for objects referenced in modifiers (even if disabled) #81237

New Issue

Jesse Yurkovich · 2020-09-27T22:40:43+02:00

Jesse Yurkovich commented

2020-09-27 22:40:43 +02:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-25 20:54, hash: 83dc97ccc0
Worked: probably never; hopefully it's just an oversight. Even 2.79b is broken

Short description of error
I've experienced this a handful of times but finally sat down to investigate from the user perspective here today (sorry, haven't looked at the code). But apparently the object you use as Simple Deform's "origin" will not be snap-able to the object that has Simple Deform on it. It doesn't matter if the modifier is enabled or disabled or if the settings actually produces no deformation, it always breaks snapping for the origin object.

Exact steps for others to reproduce the error
snap-issue.blend

Open the attached .blend file OR follow next instructions to setup
- Start with default scene and add an Empty to the scene
- Add a Simple Deform modifier to the Cube
- Set the Simple Deform's "origin" object to the Empty, the mode to "Bend" and the "Angle" to 0deg (to prevent any deformation)
- Set the scene snapping mode to vertex
Grab the Empty and attempt to snap it to verts of the Cube -- it cannot snap (bug)
Disable the modifier and repeat the snap attempt -- it still cannot snap to the Cube (bug)
Create a new object and attempt to snap the empty to that new object -- it succeeds (the Sphere in the attached .blend file)
Delete the modifier and repeat the snap -- finally, it is able to snap to the Cube

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67 **Blender Version** Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-25 20:54, hash: `83dc97ccc0` Worked: probably never; hopefully it's just an oversight. Even 2.79b is broken **Short description of error** I've experienced this a handful of times but finally sat down to investigate from the user perspective here today (sorry, haven't looked at the code). But apparently the object you use as Simple Deform's "origin" will not be snap-able to the object that has Simple Deform on it. It doesn't matter if the modifier is enabled or disabled or if the settings actually produces no deformation, it always breaks snapping for the origin object. **Exact steps for others to reproduce the error** [snap-issue.blend](https://archive.blender.org/developer/F8929379/snap-issue.blend) - Open the attached .blend file OR follow next instructions to setup - Start with default scene and add an Empty to the scene - Add a Simple Deform modifier to the Cube - Set the Simple Deform's "origin" object to the Empty, the mode to "Bend" and the "Angle" to 0deg (to prevent any deformation) - Set the scene snapping mode to vertex - Grab the Empty and attempt to snap it to verts of the Cube -- it cannot snap (bug) - Disable the modifier and repeat the snap attempt -- it still cannot snap to the Cube (bug) - Create a new object and attempt to snap the empty to that new object -- it succeeds (the Sphere in the attached .blend file) - Delete the modifier and repeat the snap -- finally, it is able to snap to the Cube

Jesse Yurkovich commented

2020-09-27 22:40:43 +02:00

Added subscriber: @deadpin

blender-admin commented

2020-09-27 22:40:43 +02:00

#100785 was marked as duplicate of this issue

Jesse Yurkovich commented

2020-09-28 02:12:30 +02:00

Hmm, so ignoring the special case of no deformation or the modifier being disabled, I suppose the general case is that this would result in circular behavior. If I attempt to snap the empty to original vertex V, the act of moving that empty will potentially cause V to move to a new location... so where should it snap?

I'll let the bug triagers declare if this is supported or not.

Hmm, so ignoring the special case of no deformation or the modifier being disabled, I suppose the general case is that this would result in circular behavior. If I attempt to snap the empty to original vertex V, the act of moving that empty will potentially cause V to move to a new location... so where should it snap? I'll let the bug triagers declare if this is supported or not.

Germano Cavalcante commented

2020-10-05 17:35:00 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-10-05 17:35:00 +02:00

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

Germano Cavalcante commented

2020-10-05 17:35:00 +02:00

The "Cube" object has a dependency of type DEG_OB_COMP_GEOMETRY.
During the transformation, all objects with this dependency are ignored for snapping.

Perhaps the depsgraph could be smarter and not set this dependency if the modifier is disabled.
But this is a known issue and has already been mentioned in #73199 for example.

The "Cube" object has a dependency of type `DEG_OB_COMP_GEOMETRY`. During the transformation, all objects with this dependency are ignored for snapping. Perhaps the depsgraph could be smarter and not set this dependency if the modifier is disabled. But this is a known issue and has already been mentioned in #73199 for example.

Germano Cavalcante changed title from ~~Snapping broken for objects used as the "origin" in Simple Deform~~ to No snapping for objects referenced in modifiers (even if disabled)

2020-10-05 17:38:01 +02:00

Pratik Borhade commented

2022-09-03 06:26:12 +02:00

Added subscriber: @Vyach

Pratik Borhade commented

2022-09-03 06:26:20 +02:00

Added subscriber: @PratikPB2123

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

No snapping for objects referenced in modifiers (even if disabled) #81237