Extrude, Dissolve and Intersect. Some problems. #76039

New Issue

Alaska · 2020-04-24T03:43:34+02:00

Alaska commented

2020-04-24 03:43:34 +02:00

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

Blender Version
Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-04-23 16:26, hash: 7d98dfd6bb
Worked: (newest version of Blender that worked as expected)

Short description of error
I'm not sure, but, if you're interested, I found a few problems.
Watch gif pictures.
From Tools panel and from hotkey E, they work differently. From hotkey E, there remains excess geometry.:

Extra geometry in a difficult place:

Extrude, Dissolve and Intersect.blend

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19 **Blender Version** Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-04-23 16:26, hash: `7d98dfd6bb` Worked: (newest version of Blender that worked as expected) **Short description of error** I'm not sure, but, if you're interested, I found a few problems. Watch gif pictures. From Tools panel and from hotkey E, they work differently. From hotkey E, there remains excess geometry.: ![xhtfjhcfthxdr .gif](https://archive.blender.org/developer/F8491470/xhtfjhcfthxdr_.gif) Extra geometry in a difficult place: ![xthxthxrgxdrd.gif](https://archive.blender.org/developer/F8491472/xthxthxrgxdrd.gif) [Extrude, Dissolve and Intersect.blend](https://archive.blender.org/developer/F8491477/Extrude__Dissolve_and_Intersect.blend)

Alaska commented

2020-04-24 03:43:34 +02:00

Added subscriber: @Alaska

blender-admin commented

2020-04-24 03:43:34 +02:00

#76029 was marked as duplicate of this issue

Alaska commented

2020-04-24 03:44:18 +02:00

Added subscriber: @AxelMening-4

Alaska commented

2020-04-24 03:49:43 +02:00

Just to expand on the original post from @AxelMening-4 which I accidentally closed on the basis that I was reproducing the wrong issue.
Ticking "Dissolve Orthographic Edges" in the last operator panel of the extrude operation produces different results to the "Extrude, Dissolve, and intersect" tool. The development of the tool D7222 suggests that "Extrude, Dissolve, and intersect" and "Dissolve Orthographic Edges" are the same operation.

Just to expand on the original post from @AxelMening-4 which I accidentally closed on the basis that I was reproducing the wrong issue. Ticking "Dissolve Orthographic Edges" in the last operator panel of the extrude operation produces different results to the "Extrude, Dissolve, and intersect" tool. The development of the tool [D7222](https://archive.blender.org/developer/D7222) suggests that "Extrude, Dissolve, and intersect" and "Dissolve Orthographic Edges" are the same operation.

Alaska commented

2020-04-24 03:57:19 +02:00

It seems to be a issue with the extra vertices being "created" in the operation not being added to the faces connected to the edge that had the operator applied to it.

Key:
F=Face
V=Vertice
In this example (Extrude with "E" then enable "Dissolve Orthographic Edges"), F1 is a quad face with it's four original vertices (V1,V2,V3,V4) while with "Extrude, Dissolve, and intersect" F1 is a n-gon with five vertices (V1, V2, V3, V4, V5).

Or an alternative explaination. The edge V3, V4 stays as one when you extrude with E then enable "Dissolve Orthographic Edges" while with "Extrude, Dissolve, and intersect" that edge is split into two V4, V5 and V5, V3.

It seems to be a issue with the extra vertices being "created" in the operation not being added to the faces connected to the edge that had the operator applied to it. Key: F=Face V=Vertice In this example (Extrude with "E" then enable "Dissolve Orthographic Edges"), F1 is a quad face with it's four original vertices (V1,V2,V3,V4) while with "Extrude, Dissolve, and intersect" F1 is a n-gon with five vertices (V1, V2, V3, V4, V5). ![Screenshot from 2020-04-24 13-52-42.png](https://archive.blender.org/developer/F8491858/Screenshot_from_2020-04-24_13-52-42.png) Or an alternative explaination. The edge V3, V4 stays as one when you extrude with E then enable "Dissolve Orthographic Edges" while with "Extrude, Dissolve, and intersect" that edge is split into two V4, V5 and V5, V3.

Philipp Oeser commented

2020-04-24 10:48:26 +02:00

Added subscribers: @mano-wii, @lichtwerk

Philipp Oeser commented

2020-04-24 10:48:26 +02:00

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

Philipp Oeser commented

2020-04-24 10:48:26 +02:00

Would confirm on first sight.
Though I havent checked where the differences between the tool and the extrude option are...
@mano-wii: could you comment? (on first sight, seems like legit criticism?)

Would confirm on first sight. Though I havent checked where the differences between the tool and the extrude option are... @mano-wii: could you comment? (on first sight, seems like legit criticism?)

Alaska commented

2020-04-24 11:02:17 +02:00

@lichtwerk and @mano-wii

Extrude, Dissolve, and intersect

bpy.ops.mesh.extrude_region_dissolve_move_intersect(MESH_OT_extrude_region={"use_normal_flip":False, "use_dissolve_ortho_edges":True, "mirror":False}, TRANSFORM_OT_translate={"value":(0, 0, -0.649887), "orient_axis_ortho":'X', "orient_type":'NORMAL', "orient_matrix":((1, 0, -0), (0, 0, 1), (0, -1, 0)), "orient_matrix_type":'NORMAL', "constraint_axis":(False, False, True), "mirror":False, "use_proportional_edit":False, "proportional_edit_falloff":'SMOOTH', "proportional_size":1, "use_proportional_connected":False, "use_proportional_projected":False, "snap":False, "snap_target":'CLOSEST', "snap_point":(0, 0, 0), "snap_align":False, "snap_normal":(0, 0, 0), "gpencil_strokes":False, "cursor_transform":False, "texture_space":False, "remove_on_cancel":False, "release_confirm":True, "use_accurate":False, "use_automerge_and_split":True})

Dissolve Orthographic Edges

bpy.ops.mesh.extrude_region_move(MESH_OT_extrude_region={"use_normal_flip":False, "use_dissolve_ortho_edges":True, "mirror":False}, TRANSFORM_OT_translate={"value":(0, 0, -0.577566), "orient_axis_ortho":'X', "orient_type":'NORMAL', "orient_matrix":((1, 0, -0), (0, 0, 1), (0, -1, 0)), "orient_matrix_type":'NORMAL', "constraint_axis":(False, False, True), "mirror":False, "use_proportional_edit":False, "proportional_edit_falloff":'SMOOTH', "proportional_size":1, "use_proportional_connected":False, "use_proportional_projected":False, "snap":False, "snap_target":'CLOSEST', "snap_point":(0, 0, 0), "snap_align":False, "snap_normal":(0, 0, 0), "gpencil_strokes":False, "cursor_transform":False, "texture_space":False, "remove_on_cancel":False, "release_confirm":False, "use_accurate":False, "use_automerge_and_split":False})

The difference seems to be that "use_automerge_and_split" doesn't activate when you just tick the "Dissolve orthographic edges" option. Probably just needs to be added when you enable "Dissolve Orthographic Edges". Or the setting could be exposed for those that want it.

I'm not much of a programmer. And I'm not the designer of this. I'll leave it up to you to decide.

@lichtwerk and @mano-wii **Extrude, Dissolve, and intersect** >bpy.ops.mesh.extrude_region_dissolve_move_intersect(MESH_OT_extrude_region={"use_normal_flip":False, "use_dissolve_ortho_edges":True, "mirror":False}, TRANSFORM_OT_translate={"value":(0, 0, -0.649887), "orient_axis_ortho":'X', "orient_type":'NORMAL', "orient_matrix":((1, 0, -0), (0, 0, 1), (0, -1, 0)), "orient_matrix_type":'NORMAL', "constraint_axis":(False, False, True), "mirror":False, "use_proportional_edit":False, "proportional_edit_falloff":'SMOOTH', "proportional_size":1, "use_proportional_connected":False, "use_proportional_projected":False, "snap":False, "snap_target":'CLOSEST', "snap_point":(0, 0, 0), "snap_align":False, "snap_normal":(0, 0, 0), "gpencil_strokes":False, "cursor_transform":False, "texture_space":False, "remove_on_cancel":False, "release_confirm":True, "use_accurate":False, "use_automerge_and_split":True}) **Dissolve Orthographic Edges** >bpy.ops.mesh.extrude_region_move(MESH_OT_extrude_region={"use_normal_flip":False, "use_dissolve_ortho_edges":True, "mirror":False}, TRANSFORM_OT_translate={"value":(0, 0, -0.577566), "orient_axis_ortho":'X', "orient_type":'NORMAL', "orient_matrix":((1, 0, -0), (0, 0, 1), (0, -1, 0)), "orient_matrix_type":'NORMAL', "constraint_axis":(False, False, True), "mirror":False, "use_proportional_edit":False, "proportional_edit_falloff":'SMOOTH', "proportional_size":1, "use_proportional_connected":False, "use_proportional_projected":False, "snap":False, "snap_target":'CLOSEST', "snap_point":(0, 0, 0), "snap_align":False, "snap_normal":(0, 0, 0), "gpencil_strokes":False, "cursor_transform":False, "texture_space":False, "remove_on_cancel":False, "release_confirm":False, "use_accurate":False, "use_automerge_and_split":False}) The difference seems to be that "use_automerge_and_split" doesn't activate when you just tick the "Dissolve orthographic edges" option. Probably just needs to be added when you enable "Dissolve Orthographic Edges". Or the setting could be exposed for those that want it. I'm not much of a programmer. And I'm not the designer of this. I'll leave it up to you to decide.

Philipp Oeser commented

2020-04-24 11:15:22 +02:00

In this case, the new tool is really a separate thing, so you cannot just turn a "regular" extrude/extrude_region_move into the extrude_region_dissolve_move_intersect by enabling that Dissolve Orthographic Edges option.
Would vote for this report being "Invalid", but leave the final word to @mano-wii...

In this case, the new tool is really a separate thing, so you cannot just turn a "regular" `extrude`/`extrude_region_move` into the `extrude_region_dissolve_move_intersect` by enabling that `Dissolve Orthographic Edges` option. Would vote for this report being "Invalid", but leave the final word to @mano-wii...

Germano Cavalcante commented

2020-04-24 14:25:56 +02:00

Changed status from 'Confirmed' to: 'Archived'

Germano Cavalcante closed this issue

2020-04-24 14:25:56 +02:00

Germano Cavalcante self-assigned this 2020-04-24 14:25:56 +02:00

Germano Cavalcante commented

2020-04-24 14:25:56 +02:00

This is not a bug but it works as designed.
There is a task proposing a replacement for the tool -> #75913

This is not a bug but it works as designed. There is a task proposing a replacement for the tool -> #75913

So3Datel commented

2020-04-24 17:53:45 +02:00

In #76039#916804, @mano-wii

What do you think about this? At this point, non-remote geometry is obtained.

Extrude, Dissolve and Intersect222.blend

> In #76039#916804, @mano-wii What do you think about this? At this point, non-remote geometry is obtained. ![hukgyctserg.gif](https://archive.blender.org/developer/F8492724/hukgyctserg.gif) [Extrude, Dissolve and Intersect222.blend](https://archive.blender.org/developer/F8492728/Extrude__Dissolve_and_Intersect222.blend)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Extrude, Dissolve and Intersect. Some problems. #76039