Unexpected merging of vertex groups with different names #53206

Closed
opened 5 years ago by SergeL · 8 comments
SergeL commented 5 years ago

System Information
Win 7 64 bit

Blender Version
Broken: 2.79

Short description of error
Mesh called Array is using array modifier with start cap option, all vertices of it belong to "Mask" vgroup. Some vertices of Start Cap mesh belong to "Bevel" vgroup.

When I choose "Bevel" group in Bevel modifier, vertices that are not in this group somehow merging with "Mask" group of Array mesh.

Exact steps for others to reproduce the error
Open file, choose "Bevel" vgroup in Bevel modifier -> see how another mesh is masking

PS. Workaround is to create another empty vgroup in the Start cap mesh and place it before "Bevel" group
Vgroup.blend

**System Information** Win 7 64 bit **Blender Version** Broken: 2.79 **Short description of error** Mesh called Array is using *array modifier* with *start cap* option, all vertices of it belong to "Mask" vgroup. Some vertices of Start Cap mesh belong to "Bevel" vgroup. When I choose "Bevel" group in Bevel modifier, vertices that are not in this group somehow merging with "Mask" group of Array mesh. **Exact steps for others to reproduce the error** Open file, choose "Bevel" vgroup in Bevel modifier -> see how another mesh is masking PS. Workaround is to create another empty vgroup in the Start cap mesh and place it before "Bevel" group [Vgroup.blend](https://archive.blender.org/developer/F1077533/Vgroup.blend)
SergeL commented 5 years ago
Poster

Changed status to: 'Open'

Changed status to: 'Open'
SergeL commented 5 years ago
Poster

Added subscriber: @SergeL

Added subscriber: @SergeL
SergeL changed title from Unexpected merging of vertex groups to Unexpected merging of vertex groups with different names 5 years ago
zeauro commented 5 years ago

Added subscriber: @zeauro

Added subscriber: @zeauro
zeauro commented 5 years ago

It looks like array modifier is not using name but index of vertex group.

It is interesting to be able to apply an effect depending of vertex group on cap and array after array modifier.
But yes ! Vertex groups with different names should not be merged.
Or, at least user should be warned.

It looks like array modifier is not using name but index of vertex group. It is interesting to be able to apply an effect depending of vertex group on cap and array after array modifier. But yes ! Vertex groups with different names should not be merged. Or, at least user should be warned.
Foaly commented 5 years ago

Added subscriber: @Foaly

Added subscriber: @Foaly
Foaly commented 5 years ago

I have added a patch, but I don't know if I did it correctly.
If you can see it: Is it okay to fix it that way?

I have added a patch, but I don't know if I did it correctly. If you can see it: Is it okay to fix it that way?
Collaborator

This issue was referenced by d9d3ed16a8

This issue was referenced by d9d3ed16a8c61bb1c780d81a2cf398be92cd16c1
Owner

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
ideasman42 closed this issue 5 years ago
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Sculpt, Paint & Texture
legacy module/User Interface
legacy module/VFX & Video
legacy project/BF Blender: 2.8
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/OpenGL Error
legacy project/Retrospective
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#53206
Loading…
There is no content yet.