Dissolve Edges should not dissolve vertices that are not previously selected #109765

Open
opened 2023-07-06 03:42:18 +02:00 by kursad k · 14 comments
Member

System Information
Operating system: Win 11

Blender Version
Broken: 1a44120d71
Worked: N/A

Updated description:

The "Dissolve Vertices" option from "Dissolve Edges" operator should not dissolve vertices that are not previously selected.

The vertex in red circle should not be dissolved in any way, no matter whether "Dissolve vertices" option is on or off. And this only happens when the vertex in red circle and the adjacent selected one being 3-way connected.

图片

Reproduce:

  1. Open 109765.blend.
  2. x > Dissolve Edges.
  3. Try enabling and disabling "Dissolve Vertices" option in the operator arguments panel, either way it's incorrect.

Expected behaviour:

"Dissolve Vertices" option should never dissolve the vertex circled in red.


Original description:

It seems like Blender removes non connected vertices during edge dissolve. See the video and the image

blender_bP0X8NRcFs.jpg

Exact steps for others to reproduce the error

  1. Load bug_05072023_2041_45 file.
  2. delete the selected edges using "X->Dissolve Edges".
**System Information** Operating system: Win 11 **Blender Version** Broken: 1a44120d7175 Worked: N/A Updated description: The "Dissolve Vertices" option from "Dissolve Edges" operator should not dissolve vertices that are not previously selected. The vertex in red circle should not be dissolved in any way, no matter whether "Dissolve vertices" option is on or off. And this only happens when the vertex in red circle and the adjacent selected one being 3-way connected. ![图片](/attachments/54d72881-1695-45e7-a282-306764297870) Reproduce: 1. Open `109765.blend`. 2. x > Dissolve Edges. 3. Try enabling and disabling "Dissolve Vertices" option in the operator arguments panel, either way it's incorrect. Expected behaviour: "Dissolve Vertices" option should never dissolve the vertex circled in red. ------- Original description: It seems like Blender removes non connected vertices during edge dissolve. See the video and the image | | | |--|--| | ![blender_bP0X8NRcFs.jpg](/attachments/c9597eba-e7f4-468f-b032-8ad0f9eec160) | <video src="/attachments/66033c0c-1856-484c-b187-53c1e907c924" title="blender_mqFBR66QUe.mp4" controls></video> | **Exact steps for others to reproduce the error** 1. Load `bug_05072023_2041_45` file. 2. delete the selected edges using "X->Dissolve Edges".
kursad k added the
Type
Report
Status
Needs Triage
Priority
Normal
labels 2023-07-06 03:42:19 +02:00
kursad k changed title from Edge disolve removes the corner vvertices that are not connected to the dissolved edges to Edge dissolve removes the corner vvertices that are not connected to the dissolved edges 2023-07-06 03:42:27 +02:00
kursad k changed title from Edge dissolve removes the corner vvertices that are not connected to the dissolved edges to Edge dissolve removes the corner vertices that are not connected to the dissolved edges 2023-07-06 03:46:26 +02:00
Member

I'd say this result is expected, because for a 3-edge connected vertex, if you dissolve two of the edges, the other edge has nothing to connect to, hence it's also removed. if you don't want that vertex to be removed, you can make a 4-way connection like this: So I believe this is not a bug.

图片 图片

I'd say this result is expected, because for a 3-edge connected vertex, if you dissolve two of the edges, the other edge has nothing to connect to, hence it's also removed. if you don't want that vertex to be removed, you can make a 4-way connection like this: So I believe this is not a bug. ![图片](/attachments/919ae58e-889b-498a-94c7-8dba986c18c0) ![图片](/attachments/952f611a-b8c2-4256-bc0c-7d94d3a614e9)
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-07-06 04:04:00 +02:00
Author
Member

This is not how it works in other DCCs. It would be nice if this produces the desired effect given, it is deleting a vertex that has nothing to do with the intended edge.

This is not how it works in other DCCs. It would be nice if this produces the desired effect given, it is deleting a vertex that has nothing to do with the intended edge.
Member

图片

You probably meant something like this?

Humm after thinking about it for a while, it does appear that the "dissolve vertices" will dissolve vertices that's not selected but affected by the "adjacently removed edges". I guess this can be improved.

![图片](/attachments/47413033-860a-4546-97f1-2cc94cff99a5) You probably meant something like this? Humm after thinking about it for a while, it does appear that the "dissolve vertices" will dissolve vertices that's not selected but affected by the "adjacently removed edges". I guess this can be improved.
YimingWu reopened this issue 2023-07-06 04:16:42 +02:00
Blender Bot added
Status
Needs Triage
and removed
Status
Archived
labels 2023-07-06 04:16:45 +02:00
YimingWu added
Module
Modeling
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-07-06 04:17:47 +02:00
YimingWu changed title from Edge dissolve removes the corner vertices that are not connected to the dissolved edges to Dissolve Edges > `Dissolve Vertices` option should not dissolve vertices that are not previously selected. 2023-07-06 04:22:04 +02:00
Member

Updated description for more clear topology.

Updated description for more clear topology.
Author
Member

Thanks for reopening this. The solution you provided is super messy because one has to triangulate, dissolve edges then remove the temporary edge, which is really way too much work in a real world scenario given this operation could be employed many times on denser meshes, it will create so much friction. That is the reason I opened the bug, not that i could not find a work around, it is just that this is promoting bad practices and wastes time away beside deleting something that is not part of the operation directly.

Thanks for reopening this. The solution you provided is super messy because one has to triangulate, dissolve edges then remove the temporary edge, which is really way too much work in a real world scenario given this operation could be employed many times on denser meshes, it will create so much friction. That is the reason I opened the bug, not that i could not find a work around, it is just that this is promoting bad practices and wastes time away beside deleting something that is not part of the operation directly.

This is expected behavior and there is a separate setting for what you want:
image
Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

This is expected behavior and there is a separate setting for what you want: ![image](/attachments/f4ad40cc-cebd-40f5-8147-b03976f9e7c1) Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2023-07-06 09:44:57 +02:00
Member

@mod_moder Nope, disabling that option will also preserve vertices from the edges being dissolved, so either on or off the result is incorrect

@mod_moder Nope, disabling that option will also preserve vertices from the edges being dissolved, so either on or off the result is incorrect
YimingWu reopened this issue 2023-07-06 09:55:48 +02:00
Blender Bot added
Status
Needs Triage
and removed
Status
Archived
labels 2023-07-06 09:55:50 +02:00
Iliya Katushenock added
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-07-06 09:57:35 +02:00
Iliya Katushenock changed title from Dissolve Edges > `Dissolve Vertices` option should not dissolve vertices that are not previously selected. to Dissolve Edges should not dissolve vertices that are not previously selected 2023-07-06 09:58:51 +02:00
Author
Member

@mod_moder Disabling the "dissolve vertices" is a completely different operation and has nothing to do with the original operation. Keeping all the vertices of the edges after dissolve is not what what the original report is about.

Photoshop_JKRrbb2BEm.jpg

Photoshop_JKRrbb2BEm.jpg

@mod_moder Disabling the "dissolve vertices" is a completely different operation and has nothing to do with the original operation. Keeping all the vertices of the edges after dissolve is not what what the original report is about. ![Photoshop_JKRrbb2BEm.jpg](/attachments/f5d28a6c-5feb-4a0c-bf39-977d1cffb272) ![Photoshop_JKRrbb2BEm.jpg](/attachments/6d73217b-a1af-4ebd-9e90-16c7f56e72d4)

Such cases are usually solved with loopslide, which provide a better control over the result, so we never considered it as critical.
A video:

Such cases are usually solved with loopslide, which provide a better control over the result, so we never considered it as critical. A video:
Author
Member

@1D_Inc Sure but that is a completely different operation that happens to give a similar result. It does not address the issue with dissolve.

@1D_Inc Sure but that is a completely different operation that happens to give a similar result. It does not address the issue with dissolve.

Can you provide a case with similar problem, in theory solvable by dissolve and not solvable with edge loop sliding?
We didnt found when tried, so we thougth that use cases that produce this issue are supposed to be solved by edge slide instead of dissolve, so we never considered reporting it.

(Unlike vertex deletion checkbox in dissolve operator locking)

Can you provide a case with similar problem, in theory solvable by dissolve and not solvable with edge loop sliding? We didnt found when tried, so we thougth that use cases that produce this issue are supposed to be solved by edge slide instead of dissolve, so we never considered reporting it. (Unlike vertex deletion checkbox in dissolve operator locking)
Member

@1D_Inc , using edge slide in this case would need to have auto-merge on, and in some cases if you don't want to dissolve the full loop, it won't work.

Here the main problem is that "Dissolve Vertices" option removed vertices that are not previously selected. That should not happen either way.

@1D_Inc , using edge slide in this case would need to have auto-merge on, and in some cases if you don't want to dissolve the full loop, it won't work. Here the main problem is that "Dissolve Vertices" option removed vertices that are not previously selected. That should not happen either way.
Author
Member

I was just saying that the edge slide is a completely different operation, and this issue needs to be solved with edge dissolve, not that edge slide cant do what needs to be done.

I was just saying that the edge slide is a completely different operation, and this issue needs to be solved with edge dissolve, not that edge slide cant do what needs to be done.

Okay, hope it is mathematically possible to solve this for edge dissolve. That will be useful for sure.

Okay, hope it is mathematically possible to solve this for edge dissolve. That will be useful for sure.
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
4 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#109765
No description provided.