Single vertex shows strange behavior when moved in 3D space #53252

Closed
opened 2017-11-05 13:03:45 +01:00 by Gaia Clary · 16 comments
Member

Blender Version
Broken: hash 78c2242
Worked: (optional)

Short description of error

open fixed-verts.blend and grab the selected vertex (using "G")
Try to move the vertex around. It does not move freely as expected .

Exact steps for others to reproduce the error

  • type "G" and move the selected vertex: The vertex does only move along an invisible line in 3D
  • Grabe the entire mesh: all verts except the one behave correct
  • switch to Face Select mode: Same behavior.

Something tells this vertex to misbehave :)

**Blender Version** Broken: hash 78c2242 Worked: (optional) **Short description of error** open [fixed-verts.blend](https://archive.blender.org/developer/F1096103/fixed-verts.blend) and grab the selected vertex (using "G") Try to move the vertex around. It does not move freely as expected . **Exact steps for others to reproduce the error** - type "G" and move the selected vertex: The vertex does only move along an invisible line in 3D - Grabe the entire mesh: all verts except the one behave correct - switch to Face Select mode: Same behavior. Something tells this vertex to misbehave :)
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @GaiaClary

Added subscriber: @GaiaClary

Added subscriber: @Ko

Added subscriber: @Ko

Worth to add: it moves, but only by 0.000something. And after using "smooth selected vertices" it start to moving normally.

Worth to add: it moves, but only by 0.000something. And after using "smooth selected vertices" it start to moving normally.

Added subscriber: @VukGardasevic

Added subscriber: @VukGardasevic

Unchecking the Toolbar > Options> Mesh Options > Mesh Mirror > X Mirror option will allow the vertex to move freely.
Not sure why it is stuck for that specific vertex (index 92).

Unchecking the `Toolbar > Options> Mesh Options > Mesh Mirror > X Mirror` option will allow the vertex to move freely. Not sure why it is stuck for that specific vertex (index 92).

Added subscriber: @FloridaJo

Added subscriber: @FloridaJo

Also, upon opening, the vertex 'X' position is .00078. If you manually change it to something like .00079 and above or .00076 and below, it works normally.

  • update, also if you select a another close verex vertically and set that 'x' value to .00078, it also seems to resist changing the 'x' value from that point also upon Grabbing.
Also, upon opening, the vertex 'X' position is .00078. If you manually change it to something like .00079 and above or .00076 and below, it works normally. - update, also if you select a another close verex vertically and set that 'x' value to .00078, it also seems to resist changing the 'x' value from that point also upon Grabbing.

Added subscriber: @mano-wii

Added subscriber: @mano-wii

This happens because the local coordinate 'x' of the locked vertex has the value 0.0. So it becomes a "reflection" of itself.

When X-Mirror is enabled, the only thing that indicates whether a pair of vertices is mirrored or not are their coordinates.

If the coordinate of a vertex is (x, y, z), its mirrored vertex would have the coordinate (-x, y, z). Vertices with 'x' zero do not move either to the right or to the left to remain mirrored.

Therefore this behavior is expected. But some questions remain open:

  • Would it be better to disable this behavior when proportional editing is not enabled?;
  • Should Topology Mirror prevent this from happening?;
This happens because the local coordinate 'x' of the locked vertex has the value 0.0. So it becomes a "reflection" of itself. When `X-Mirror` is enabled, the only thing that indicates whether a pair of vertices is mirrored or not are their coordinates. If the coordinate of a vertex is (x, y, z), its mirrored vertex would have the coordinate (-x, y, z). Vertices with 'x' zero do not move either to the right or to the left to remain mirrored. Therefore this behavior is expected. But some questions remain open: - Would it be better to disable this behavior when `proportional editing` is not enabled?; - Should `Topology Mirror` prevent this from happening?;
Author
Member

It sounds odd to do a mirror on self when x location is 0.
Would it be convenient to add a simple check like:

if (no mirrored vertex found or mirrored vertex is self) then treat as simple vertex
It sounds odd to do a mirror on self when x location is 0. Would it be convenient to add a simple check like: ``` if (no mirrored vertex found or mirrored vertex is self) then treat as simple vertex ```

Added subscriber: @zeauro

Added subscriber: @zeauro

It makes sense to have vertices on symmetrical plane locked on this plane by X Mirror when they are included into a bigger selection.

You just have to try to move an edge or a face that have vertices on a YZ plane at X=0 with X Mirror ON to understand why.

But if the selection is limited to vertices on YZ plane at X=0, I don't see an issue to disable the locking of vertices.

It makes sense to have vertices on symmetrical plane locked on this plane by X Mirror when they are included into a bigger selection. You just have to try to move an edge or a face that have vertices on a YZ plane at X=0 with X Mirror ON to understand why. But if the selection is limited to vertices on YZ plane at X=0, I don't see an issue to disable the locking of vertices.

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Campbell Barton self-assigned this 2017-11-20 03:29:56 +01:00

This is working as intended so its not a bug,
we've had many reports over the years from users leaving x-mirror on by accident, then noticing strange behavior - in nearly all cases it's because they're not actually editing a symmetrical mesh.

We could have visual feedback for this, see related patch: D2839

This is working as intended so its not a bug, we've had many reports over the years from users leaving x-mirror on by accident, then noticing strange behavior - in nearly all cases it's because they're not actually editing a symmetrical mesh. We could have visual feedback for this, see related patch: [D2839](https://archive.blender.org/developer/D2839)
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
7 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#53252
No description provided.