Auto merge sometimes doesn't work in edit cage display #40680

Closed
opened 2014-06-18 00:54:56 +02:00 by gandalf3 · 8 comments
Member

System Information
Archlinux
GTX 460

Blender Version
Broken: 2.71 RC2
Worked: 2.62

Short description of error
Some vertices snapped on top of each other in applied edit cage mode don't merge when auto merge is enabled. This used to work (tested in 2.62, but possibly works in newer versions too). It always works when not in applied edit cage mode (the triangle icon on some modifiers, e.g. subserf).

Exact steps for others to reproduce the error

  1. Open auto_merge_and_snapping_with_edit_cage.blend
  2. Press G and move the cursor over a corner vertex (the ones in the middle seem to work in both 2.62 and 2.71. If you try the corner ones you'll notice that snapping does not use the applied edit cage, but that's a whole different thing..)
  3. In 2.62 the vertices are merged as expected. In 2.71 they are not.
**System Information** Archlinux GTX 460 **Blender Version** Broken: 2.71 RC2 Worked: 2.62 **Short description of error** Some vertices snapped on top of each other in applied edit cage mode don't merge when auto merge is enabled. This used to work (tested in 2.62, but possibly works in newer versions too). It always works when not in applied edit cage mode (the triangle icon on some modifiers, e.g. subserf). **Exact steps for others to reproduce the error** 1. Open [auto_merge_and_snapping_with_edit_cage.blend](https://archive.blender.org/developer/F94594/auto_merge_and_snapping_with_edit_cage.blend) 2. Press G and move the cursor over a corner vertex (the ones in the middle seem to work in both 2.62 and 2.71. If you try the corner ones you'll notice that snapping does not use the applied edit cage, but that's a whole different thing..) 3. In 2.62 the vertices are merged as expected. In 2.71 they are not.
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @gandalf3

Added subscriber: @gandalf3
Campbell Barton was assigned by Sergey Sharybin 2014-06-18 09:58:57 +02:00

Added subscriber: @Sergey

Added subscriber: @Sergey
Author
Member

Added subscriber: @ideasman42

Added subscriber: @ideasman42
Author
Member

@Sergey to (hopefully) make some things clear, @ideasman42 clarified some points of this issue over on #40679 (an unrelated but similar issue), whether by coincidence or mistake..

Anyway, I think there might be some confusion going on and mixing up of reports (I know I was confused at least).

@Sergey to (hopefully) make some things clear, @ideasman42 clarified some points of this issue over on #40679 (an unrelated but similar issue), whether by coincidence or mistake.. Anyway, I think there might be some confusion going on and mixing up of reports (I know I was confused at least).

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

I can see that in this case it might be nice for auto-merge to detect this case and act differently.
But this is really a mix of conflicting options.

If you snap to self, you may want to snap to the modified or the non modified geometry.
Currently it just follows the cage option, which is at least logical. - Rather not attempt to guess user needs here.

closing.

I can see that in this case it might be nice for auto-merge to detect this case and act differently. But this is really a mix of conflicting options. If you snap to self, you may want to snap to the modified or the non modified geometry. Currently it just follows the cage option, which is at least logical. - Rather not attempt to guess user needs here. closing.
Author
Member

For the record, here is the comment I also mistakenly wrote on the other report:

I see now. I didn't realize the snapping behavior has been improved between 2.62 and 2.71 to use the deformed edit cage. Very nice addition, thanks to whoever added that :)

However, I'm still not quite sure this is the most useful behavior..
Maybe when snapping with modified edit cage enabled, perhaps there should be an option to snap to the true position of the geometry instead?

So in the case of the vertex snapping to the modified edit cage, with the cursor on the apparent, modified location of the target vertex, the vertex being transformed would go to the true (unmodified) location of the target vertex.

*For the record, here is the comment I also mistakenly wrote on the other report:* I see now. I didn't realize the snapping behavior has been improved between 2.62 and 2.71 to use the deformed edit cage. Very nice addition, thanks to whoever added that :) However, I'm still not quite sure this is the most useful behavior.. Maybe when snapping with modified edit cage enabled, perhaps there should be an option to snap to the true position of the geometry instead? So in the case of the vertex snapping to the modified edit cage, with the cursor on the apparent, modified location of the target vertex, the vertex being transformed would go to the true (unmodified) location of the target vertex.
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
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#40680
No description provided.