Boolean modifier, snapping doesn't work #54241

New Issue

BlenderSpot · 2018-03-07T01:05:50+01:00

BlenderSpot commented

2018-03-07 01:05:50 +01:00

Windows 10

Blender 2.79a 8928d99270

If an object has a boolean modifier with a chosen mesh, that chosen mesh cannot be snapped onto the object with the said boolean modifier. You can snap the object with the boolean modifier onto anything, works fine; you can snap any other object onto a mesh with boolean on, also works fine. But if it's the mesh that was chosen to be used as a boolean object, you can't snap it onto any element of that object that has the boolean modifier.

Windows 10 Blender 2.79a 8928d99270f If an object has a boolean modifier with a chosen mesh, that chosen mesh cannot be snapped onto the object with the said boolean modifier. You can snap the object with the boolean modifier onto anything, works fine; you can snap any other object onto a mesh with boolean on, also works fine. But if it's the mesh that was chosen to be used as a boolean object, you can't snap it onto any element of that object that has the boolean modifier. ![boolean.png](https://archive.blender.org/developer/F2429139/boolean.png)

BlenderSpot commented

2018-03-07 01:05:50 +01:00

Added subscriber: @unimbox

Sergey Sharybin commented

2018-03-08 12:29:24 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2018-03-08 12:29:24 +01:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2018-03-08 12:29:24 +01:00

Sergey Sharybin self-assigned this 2018-03-08 12:29:24 +01:00

Sergey Sharybin commented

2018-03-08 12:29:24 +01:00

Thanks for the report, but this is not a bug, but rather how system is designed to work.

Snapping will not happen onto objects which have affect on the currently transforming object. This is to avoid feedback loops, which otherwise will cause undefined behavior of snapping.

It's all coming from the fact that snapping is happening onto "final" state of object, with modifiers applied. This way you can snap onto subdivided objects, or onto deformed by armature.

Thanks for the report, but this is not a bug, but rather how system is designed to work. Snapping will not happen onto objects which have affect on the currently transforming object. This is to avoid feedback loops, which otherwise will cause undefined behavior of snapping. It's all coming from the fact that snapping is happening onto "final" state of object, with modifiers applied. This way you can snap onto subdivided objects, or onto deformed by armature.

TJ Horner commented

2021-08-28 03:53:35 +02:00

Added subscriber: @tjhorner

TJ Horner commented

2021-08-28 03:53:35 +02:00

Apologies for bringing this issue back from the dead, but I recently ran into this. This behavior absolutely makes sense, but it occurs even when show_viewport/show_render is disabled on the modifier that references the object that's being transformed. I would expect, since the modifier is no longer active, that the object can safely be snapped onto the other object that's referencing it.

Unless there's another way to entirely disable a modifier (other than removal), then I would consider this a bug. Let me know if you agree and I can create a separate report for this.

Apologies for bringing this issue back from the dead, but I recently ran into this. This behavior absolutely makes sense, but it occurs even when `show_viewport`/`show_render` is disabled on the modifier that references the object that's being transformed. I would expect, since the modifier is no longer active, that the object can safely be snapped onto the other object that's referencing it. Unless there's another way to entirely disable a modifier (other than removal), then I would consider this a bug. Let me know if you agree and I can create a separate report for this.

Sergey Sharybin commented

2021-08-30 09:52:50 +02:00

Disabling visibility of modifier does not remove it from the dependency graph. That is another limitation of a system. The reason for this is due to possible animated/driven state of the modifier visibility.

Possible solution for this would be to implement a way to skip modifiers from the dependency graph if they are disabled and are not driven/animated.

From artist side I don't think there is a way to fully disable modifier, unfortunately.

Disabling visibility of modifier does not remove it from the dependency graph. That is another limitation of a system. The reason for this is due to possible animated/driven state of the modifier visibility. Possible solution for this would be to implement a way to skip modifiers from the dependency graph if they are disabled and are not driven/animated. From artist side I don't think there is a way to fully disable modifier, unfortunately.

Germano Cavalcante referenced this issue

2023-07-05 02:09:23 +02:00

Snap doesn't work when moving object associated with Boolean. #109711

Germano Cavalcante referenced this issue

2023-10-02 15:40:52 +02:00

Inactive geometry dependencies preventing snapping between objects #113087

Sign in to join this conversation.