Skin Resize(Ctrl + A) does not work in Symmetry #84376

New Issue

Bookyakuno · 2021-01-04T14:41:21+01:00

Bookyakuno commented

2021-01-04 14:41:21 +01:00

Blender Version
Broken: version: 2.92.0 Alpha, branch: master, commit date: 2021-01-03 01:04, hash: 1e8f266591

Short description of error
If you try to skin resize symmetric vertices with symmetric editing enabled, it will only work for one mesh.

When the symmetric editing option is enabled, selecting symmetric vertices and performing a skin resize will only affect the selected vertices.
Therefore, you should turn it off every time you want to edit the skin size symmetrically.

(You can change both sides by enabling the "Topology Mirror" option and selecting both sides)

Exact steps for others to reproduce the error

Launch Blender
Set skin modifiers to the default cube
Enter edit mode
Property → Tool Settings → Options → Enable Mirror X Option
Select a vertex on one side
Run skin resize (Ctrl + A)
Skin resizing does not work for symmetric vertices

**Blender Version** Broken: version: 2.92.0 Alpha, branch: master, commit date: 2021-01-03 01:04, hash: `1e8f266591` ![2021-01-04_22h36_07.png](https://archive.blender.org/developer/F9550309/2021-01-04_22h36_07.png) **Short description of error** If you try to skin resize symmetric vertices with symmetric editing enabled, it will only work for one mesh. When the symmetric editing option is enabled, selecting symmetric vertices and performing a skin resize will only affect the selected vertices. Therefore, you should turn it off every time you want to edit the skin size symmetrically. (You can change both sides by enabling the "Topology Mirror" option and selecting both sides) **Exact steps for others to reproduce the error** - Launch Blender - Set skin modifiers to the default cube - Enter edit mode - Property → Tool Settings → Options → Enable Mirror X Option - Select a vertex on one side - Run skin resize (Ctrl + A) - Skin resizing does not work for symmetric vertices

Bookyakuno commented

2021-01-04 14:41:21 +01:00

Added subscriber: @Bookyakuno

Philipp Oeser commented

2021-01-04 16:29:46 +01:00

Added subscribers: @mano-wii, @lichtwerk

Philipp Oeser commented

2021-01-04 16:29:46 +01:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Philipp Oeser commented

2021-01-04 16:29:46 +01:00

Dont think all transform operations are guaranteed to be supported for Mirror X.
In fact: which of the transform tools that work on custom data layers would do this? Dont think there is any?
(e.g. edge crease, bevel weight etc...)

So this might be a feature request? And not a bug?
@mano-wii: what do you think?
Not sure if it would be easy to implement this for TFM_SKIN_RESIZE, looks like the whole mirroring TransDataMirror works with locations?

Dont think all transform operations are guaranteed to be supported for `Mirror X`. In fact: which of the transform tools that work on custom data layers would do this? Dont think there is any? (e.g. edge crease, bevel weight etc...) So this might be a feature request? And not a bug? @mano-wii: what do you think? Not sure if it would be easy to implement this for `TFM_SKIN_RESIZE`, looks like the whole mirroring `TransDataMirror` works with locations?

Germano Cavalcante commented

2021-01-04 17:09:28 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'

Germano Cavalcante commented

2021-01-04 17:09:28 +01:00

For some historical design reason, the TransData used in this transform mode is the same TransData converted from mesh vertices of conventional modes (Move, Rotate, Scale).
On the one hand this seems to be convenient because in theory it reuses all the extra features (constraint, customdata correction, mirror, updates).
But since all these features are only related to the position of the vertices, it seems that it would be more convenient to create another type of TransData (and TransDataMirror) that is specific to this customdata and this mode (TFM_SKIN_RESIZE).
Although the solution to this problem does not necessarily need this cleanup/refactor, this would be a good step to take first.

I will analyze this better, for now I am confirming it as a bug.

For some historical design reason, the TransData used in this transform mode is the same TransData converted from mesh vertices of conventional modes (Move, Rotate, Scale). On the one hand this seems to be convenient because in theory it reuses all the extra features (constraint, customdata correction, mirror, updates). But since all these features are only related to the position of the vertices, it seems that it would be more convenient to create another type of TransData (and TransDataMirror) that is specific to this customdata and this mode (TFM_SKIN_RESIZE). Although the solution to this problem does not necessarily need this cleanup/refactor, this would be a good step to take first. I will analyze this better, for now I am confirming it as a bug.

Bookyakuno commented

2021-01-04 19:27:56 +01:00

The reason I find this an inconvenient bug is that I can't do symmetric editing when symmetric editing is enabled.
Various other operations can be done on both sides by selecting the meshes on both sides, but not for skin resizing.

The reason I find this an inconvenient bug is that I can't do symmetric editing when symmetric editing is enabled. Various other operations can be done on both sides by selecting the meshes on both sides, but not for skin resizing.

blender-admin commented

2021-01-04 21:36:51 +01:00

This issue was referenced by 54ee410914

This issue was referenced by 54ee4109143b6fdabf749d2fde183907469cfa3b

Germano Cavalcante commented

2021-01-04 21:37:41 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Germano Cavalcante closed this issue

2021-01-04 21:37:41 +01:00

Germano Cavalcante self-assigned this 2021-01-04 21:37:41 +01:00

Germano Cavalcante referenced this issue from a commit

2023-10-16 15:39:42 +02:00