Vertex merging: topology editing, x mirror, extrude, automerge off #76233

Closed
opened 2020-04-29 16:47:44 +02:00 by Vyacheslav Kobozev · 9 comments

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59

Blender Version
Broken: version: 2.83 (sub 15), branch: master, commit date: 2020-04-26 22:51, hash: d0d16eb7d3
Worked: (newest version of Blender that worked as expected)

Short description of error
If i extrude and cancel with mirror edit, Blender do automerge for some vertices (automerge is off). A know, that is wrong approach to select mirror vertices and use mirror, but I don`t think it should automerge.
2020-04-29_17-35-29.mp4

Exact steps for others to reproduce the error

  • Take default cube. Edit mode
  • Switch on X-mirror
  • Select face on the +Y-side
  • Extrude {key E} and cancel move {key RClick}
  • Move selection to +Y ({key G} {key Y})
**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59 **Blender Version** Broken: version: 2.83 (sub 15), branch: master, commit date: 2020-04-26 22:51, hash: `d0d16eb7d3` Worked: (newest version of Blender that worked as expected) **Short description of error** If i extrude and cancel with mirror edit, Blender do automerge for some vertices (automerge is off). A know, that is wrong approach to select mirror vertices and use mirror, but I don`t think it should automerge. [2020-04-29_17-35-29.mp4](https://archive.blender.org/developer/F8501213/2020-04-29_17-35-29.mp4) **Exact steps for others to reproduce the error** - Take default cube. Edit mode - Switch on X-mirror - Select face on the +Y-side - Extrude {key E} and cancel move {key RClick} - Move selection to +Y ({key G} {key Y})

Added subscriber: @Vyach

Added subscriber: @Vyach

Added subscriber: @Pasang

Added subscriber: @Pasang

I can confirm. But it isn't merged. It also happens in 2.79.

I can confirm. But it isn't merged. It also happens in 2.79.

@Pasang just checked, you are right.
So it looks like it work «properly»: vertices selected, with mirror mirrored (positions but not topology) selected virtually too.

But there is another strange thing then: why only one side captured and other isn`t.

@Pasang just checked, you are right. So it looks like it work «properly»: vertices selected, with mirror mirrored (positions but not topology) selected virtually too. But there is another strange thing then: why only one side captured and other isn`t.

Okay, it looks like an error in searching mirrored pair for each vertex.
I assume simple mirror just search for first vertex with mirrored cordinate. And that is a result. If so, It is not a bug but a limitation of current algorythm
2020-04-29_20-20-38.mp4

Okay, it looks like an error in searching mirrored pair for each vertex. I assume simple mirror just search for first vertex with mirrored cordinate. And that is a result. If so, It is not a bug but a limitation of current algorythm [2020-04-29_20-20-38.mp4](https://archive.blender.org/developer/F8501582/2020-04-29_20-20-38.mp4)

Added subscriber: @mano-wii

Added subscriber: @mano-wii

It would be necessary to look in more detail.
But unpredictable behavior is to be expected when more than one mirrored vertex has the same position.
Topology is not considered in the simple case.

I don't think it is worth investigating this issue.
This is certainly a limitation when vertices occupy the same position.

It would be necessary to look in more detail. But unpredictable behavior is to be expected when more than one mirrored vertex has the same position. Topology is not considered in the simple case. I don't think it is worth investigating this issue. This is certainly a limitation when vertices occupy the same position.

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

Changed status from 'Needs Triage' to: 'Archived'
Germano Cavalcante self-assigned this 2020-04-30 14:35:05 +02:00

As described in the comment above, although it is not ideal it is experimented with mirror logic without considering topology.
So closing.

As described in the comment above, although it is not ideal it is experimented with mirror logic without considering topology. So closing.
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
3 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#76233
No description provided.