Uncontrolled vertex movement in symmetric editing #74340

Open
opened 2020-03-01 18:23:51 +01:00 by Alexey Michaylov · 13 comments

System Information
Operating system: Windows 7
Graphics card: AMD Radeeon R9 200 Series

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd7, type: Release; build date: 2020-02-13, 01:56:46
Worked: (optional)

Short description of error
When symmetrical editing about the X axis with proportional editing of an almost symmetric object, model changes are detected in places where editing was not performed.

Moreover, these changes occur asymmetrically. For example, in a key with a changed shape of the legs of a human model, a significant asymmetric change in the neck region with a shift of the line of symmetry itself was found. So it is with most other shape keys. Thus, the symmetry of the entire model is violated, which entails other undesirable consequences. These problems cannot be solved programmatically or manually, and the data on the coordinates of the vertices strangely diverge from the observed form.

Exact steps for others to reproduce the error
#74340.blend

  • Open file
  • Move selected vertex

vertices in unconnected mesh on mirror side will move

Model Genesis 8 exported from DAZ Studio in Base Resolution .obj file and imported to Blender.
https://youtu.be/HMiU6BYcl2E

**System Information** Operating system: Windows 7 Graphics card: AMD Radeeon `R9` 200 Series **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: `77d23b0bd7`, type: Release; build date: 2020-02-13, 01:56:46 Worked: (optional) **Short description of error** When symmetrical editing about the X axis with proportional editing of an almost symmetric object, model changes are detected in places where editing was not performed. Moreover, these changes occur asymmetrically. For example, in a key with a changed shape of the legs of a human model, a significant asymmetric change in the neck region with a shift of the line of symmetry itself was found. So it is with most other shape keys. Thus, the symmetry of the entire model is violated, which entails other undesirable consequences. These problems cannot be solved programmatically or manually, and the data on the coordinates of the vertices strangely diverge from the observed form. **Exact steps for others to reproduce the error** [#74340.blend](https://archive.blender.org/developer/F8401187/T74340.blend) - Open file - Move selected vertex # vertices in unconnected mesh on mirror side will move Model Genesis 8 exported from DAZ Studio in Base Resolution .obj file and imported to Blender. https://youtu.be/HMiU6BYcl2E

Added subscriber: @pryboss

Added subscriber: @pryboss
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Could you share your .blend file with the model already imported?
Also please share the exact steps to reproduce the issue (which vertices to select, how to transform them etc,)
What might help here are screenshots also (showing "wrong" results vs. "expected" results)

If we dont have the above, I think there is no way to reproduce this issue... Thx for your help in advance...

Could you share your .blend file with the model already imported? Also please share the exact steps to reproduce the issue (which vertices to select, how to transform them etc,) What might help here are screenshots also (showing "wrong" results vs. "expected" results) If we dont have the above, I think there is no way to reproduce this issue... Thx for your help in advance...

I give a link to the video of the process and the file.

Here's what happens: a shape key is created and the first shift of the selected vertex causes an uncontrolled shift of the vertices in other areas with symmetry breaking. The next offset of the selected vertex works fine. With the new form key, the situation repeats and violations accumulate.

I give a link to the video of the process and the file. Here's what happens: a shape key is created and the first shift of the selected vertex causes an uncontrolled shift of the vertices in other areas with symmetry breaking. The next offset of the selected vertex works fine. With the new form key, the situation repeats and violations accumulate.

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs User Info' to: 'Confirmed'

Changed status from 'Needs User Info' to: 'Confirmed'

I could reproduce this only with proportional editing, and behavior is definitely weird.

Since this model is asymetrical in the first place not sure if this would be considered a bug.
Perhaps you could delete half of model vertices and use mirror modifier to make it perfectly symetrical?

I could reproduce this only with proportional editing, and behavior is definitely weird. Since this model is asymetrical in the first place not sure if this would be considered a bug. Perhaps you could delete half of model vertices and use mirror modifier to make it perfectly symetrical?

In order to maintain the order of the vertices, the destruction of the grid is unacceptable. To fix the defect, I tried to set all the middle vertices to the zero coordinate - this did not work. Symmetry is not restored or new vertices are added during symmetrization - this is unacceptable. But when working with symmetrical sculpting, I did not notice such a problem. It may be necessary to prepare the model in some other editor (I don’t know which one) or to make Blender somehow work ...

In order to maintain the order of the vertices, the destruction of the grid is unacceptable. To fix the defect, I tried to set all the middle vertices to the zero coordinate - this did not work. Symmetry is not restored or new vertices are added during symmetrization - this is unacceptable. But when working with symmetrical sculpting, I did not notice such a problem. It may be necessary to prepare the model in some other editor (I don’t know which one) or to make Blender somehow work ...
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

I simplified the file step by step until I got this:
2020-03-18 14-43-33.mp4
T74340_1.blend

Looks like a bug to me.

I simplified the file step by step until I got this: [2020-03-18 14-43-33.mp4](https://archive.blender.org/developer/F8413921/2020-03-18_14-43-33.mp4) [T74340_1.blend](https://archive.blender.org/developer/F8413923/T74340_1.blend) Looks like a bug to me.

Added subscriber: @mano-wii

Added subscriber: @mano-wii

I don't think this is a bug.
With proportional activated, all vertices are transformed, but some of them are far away and their transformation value is multiplied by zero.
Mirror elements are not affected by proportional edit. If the element they mirror is transformed they are transformed as well.
It is good to remember that the proportional edit radius can be changed while transforming.

It would first be necessary to discuss how to resolve this. Here are some options with their disadvantage:

  • copy the porpocional distance value to the mirror elements as well. (this would increase the structure of the mirror elements which need to be small since it can work on high poly objects and could bring other unfavorable results since it would not affect all elements).
  • add an option for mirror with offset. (Currently the code is efficient because it works with the coordinate pointer directly. With this new option, the coordinate values ​​would be obtained indirectly. It would be less efficient, but it would be the only disadvantage).

I added a task to solve this in #68836 (Transform Refactoring)

I don't think this is a bug. With proportional activated, all vertices are transformed, but some of them are far away and their transformation value is multiplied by zero. Mirror elements are not affected by proportional edit. If the element they mirror is transformed they are transformed as well. It is good to remember that the proportional edit radius can be changed while transforming. It would first be necessary to discuss how to resolve this. Here are some options with their disadvantage: - copy the porpocional distance value to the mirror elements as well. (this would increase the structure of the mirror elements which need to be small since it can work on high poly objects and could bring other unfavorable results since it would not affect all elements). - add an option for mirror with offset. (Currently the code is efficient because it works with the coordinate pointer directly. With this new option, the coordinate values ​​would be obtained indirectly. It would be less efficient, but it would be the only disadvantage). I added a task to solve this in #68836 (Transform Refactoring)
Philipp Oeser removed the
Interest
Modeling
label 2023-02-09 15:29:19 +01:00
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
5 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#74340
No description provided.