Page MenuHome

Remove Double Vertices
Closed, ArchivedPublic

Description

System Information
Operating system: Arch Linux
Graphics card: GTX 1060 6GB

Blender Version
Broken:
blender-2.80-e4dbfe0a98c1-linux-glibc224-x86_64
blender-2.80-0661bcba3210-linux-glibc224-x86_64

Short description of error

If you use the "vertices" button, duplicates are deleted regardless of the selected mode.
W menu which is now R click.
Remove duplicates now D.

In vertex selection mode, R click D to remove vertex duplicates.

In edge selection mode, R click D deletes the entire grid.

In face selection mode, R click D does not delete anything.

Exact steps for others to reproduce the error

Create any object.
In edit mode, create vertex duplicates on the object.
To remove duplicate vertices.

Details

Type
Bug

Event Timeline

I can't observe any strange behaviour on Win 10 in 0661bcba3210.

Afaik In edge selection mode, R click D is to Dissolve Edges (which makes sense), not to Remove Double Vertices.
And In face selection mode, R click D is to Dissolve Faces.

If Remove Double Vertices command is acting weird (= deletes everything) you can adjust Merge Distance parameter of the operator.

Excuse me.
Don't catch the logic.
In edge selection mode, R click D works correctly.
You have to get used to it and be careful.
Checked with WIN7.

Philipp Oeser (lichtwerk) triaged this task as Needs Information from User priority.

Also cannot really tell what is supposed to go wrong from the report.

As @artem ivanov (ixd) said, what context menu > D does is dependent on the context:

  • In vertex selection mode: Remove Doubles
  • In edge selection mode: Dissolve Edges
  • In face selection mode: Dissolve Faces

(you can also see this by looking at the entries in the menu, the corresponding entry will have the D underlined to indicate the shortcut)

All of these seem to work fine here.

If you are having problems with any of the operators, please attach an example blend file and exact steps to reproduce as well as a description of what the expected behavior would be vs. the 'wrong' behavior.

Marking as incomplete for the time being...

Philipp Oeser (lichtwerk) claimed this task.

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.