Merge by distance produces unexpected results #78916

New Issue

Andrii Mykhailov · 2020-07-14T14:06:54+02:00

Andrii Mykhailov commented

2020-07-14 14:06:54 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48

Blender Version
Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-07-12 09:05, hash: f319eec881
Worked: N/A

Short description of error
Merging vertices of a few straight edgeloops produces jagged edgeloop instead of straight one.

Exact steps for others to reproduce the error

Open attached blend file
Select vertices of three edgeloops in the middle.
Apply Merge by distance and increase threshold until they collapse into single edgeloop.
Check attached image to compare results of same operation in other editors.

by_distance.blend

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48 **Blender Version** Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-07-12 09:05, hash: `f319eec881` Worked: N/A **Short description of error** Merging vertices of a few straight edgeloops produces jagged edgeloop instead of straight one. **Exact steps for others to reproduce the error** 1. Open attached blend file 2. Select vertices of three edgeloops in the middle. 3. Apply Merge by distance and increase threshold until they collapse into single edgeloop. 4. Check attached image to compare results of same operation in other editors. [by_distance.blend](https://archive.blender.org/developer/F8693512/by_distance.blend) ![merge_by_distance_bug.jpg](https://archive.blender.org/developer/F8693513/merge_by_distance_bug.jpg)

Andrii Mykhailov commented

2020-07-14 14:06:54 +02:00

Added subscriber: @zelfit

blender-admin commented

2020-07-14 14:06:54 +02:00

#98438 was marked as duplicate of this issue

blender-admin commented

2020-07-14 14:06:54 +02:00

#83273 was marked as duplicate of this issue

Diogo Valadares Reis dos Santos commented

2020-07-14 14:55:35 +02:00

Added subscriber: @Diogo_Valadares

Diogo Valadares Reis dos Santos commented

2020-07-14 14:55:35 +02:00

I never noticed it, it doesn't merge "at center", it merges on one of the vertices "randomly".

I never noticed it, it doesn't merge "at center", it merges on one of the vertices "randomly". ![image.png](https://archive.blender.org/developer/F8693626/image.png) ![image.png](https://archive.blender.org/developer/F8693628/image.png)

Andrii Mykhailov commented

2020-07-14 15:09:07 +02:00

Yes exactly. It is kinda unpredictable and can create unnecessary problems when i simplify lowpoly for example.

Diogo Valadares Reis dos Santos commented

2020-07-14 15:14:51 +02:00

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

Jacques Lucke commented

2020-07-14 15:44:07 +02:00

Added subscribers: @ideasman42, @JacquesLucke

Jacques Lucke commented

2020-07-14 15:44:07 +02:00

This might be a feature request, will let @ideasman42 decide.

Bastien Montagne commented

2020-07-29 18:56:09 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2020-07-29 18:56:09 +02:00

Would call that a known issue/TODO. Current behavior is clearly not desired one, but code is behaving as expected (one vertex can only have one detected double, so depending on their order in the mesh both side ones will have center one as double, and merge into it, or the middle one will have one of the side ones as double and merge into it, and then the other side one will merge later when distance is further increased).

This likely needs quiet some refactor of the merge BMesh code...

Would call that a known issue/TODO. Current behavior is clearly not desired one, but code is behaving as expected (one vertex can only have one detected double, so depending on their order in the mesh both side ones will have center one as double, and merge into it, or the middle one will have one of the side ones as double and merge into it, and then the other side one will merge later when distance is further increased). This likely needs quiet some refactor of the merge BMesh code...

Germano Cavalcante commented

2020-12-03 16:48:12 +01:00

Added subscribers: @mano-wii, @Stan_Pancakes

thin soldier commented

2022-01-20 08:45:55 +01:00

Added subscriber: @thinsoldier

thin soldier commented

2022-01-20 08:45:55 +01:00

Any chance of this being fixed this year?

Germano Cavalcante commented

2022-05-27 15:32:48 +02:00

Added subscribers: @Rigoletto, @OmarEmaraDev

Rigoletto Eikenberg commented

2022-05-27 16:02:52 +02:00

I understand that it is by design, snapping to the first found vertex in the threshold,
but when i visually snapping to a vertex for merge, and then it is merged with another vertex is bad. You expect to merge what you see.

It should merge to the nearest in the threshold, to take randomize away and make it predictable.
If "Snap" is turned on it should use the snapping target instead.

I understand that it is by design, snapping to the first found vertex in the threshold, but when i visually snapping to a vertex for merge, and then it is merged with another vertex is bad. You expect to merge what you see. It should merge to the nearest in the threshold, to take randomize away and make it predictable. If "Snap" is turned on it should use the snapping target instead.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Merge by distance produces unexpected results #78916