Added operator to select verts based on vertex group count #33713

Closed
opened 2012-12-31 08:45:42 +01:00 by Jesse Werner · 13 comments

%%%The operator selects all verts based the number of vertex groups they are contained in. The inputs are operation type (equal, greater than, less than), the comparison number, and of course selection extend. I calculated the number of vertex groups an object has by iterating over all the groups. I could not if that information is stored anywhere. Please let me know if there is a better way to do this.%%%

%%%The operator selects all verts based the number of vertex groups they are contained in. The inputs are operation type (equal, greater than, less than), the comparison number, and of course selection extend. I calculated the number of vertex groups an object has by iterating over all the groups. I could not if that information is stored anywhere. Please let me know if there is a better way to do this.%%%
Author

Changed status to: 'Open'

Changed status to: 'Open'
Member

%%%what would a typical use case be like?%%%

%%%what would a typical use case be like?%%%
Member

Added subscriber: @totoro-4

Added subscriber: @totoro-4
Member

I think it could be helpful if you clean up a weight painted mesh and want to select the vertices with

  • no weight (not moved by any bones),
  • only one weight (moved by only one bone, in this case the weight value can fail you sometimes),
  • more than two weights (maybe unnecessary "garbage" weights).
I think it could be helpful if you clean up a weight painted mesh and want to select the vertices with - no weight (not moved by any bones), - only one weight (moved by only one bone, in this case the weight value can fail you sometimes), - more than two weights (maybe unnecessary "garbage" weights).

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Agree with @totoro-4, these 3 options make sense, but not sure why you would for example - want to select vertices used by 4+ vertex groups.

Agree with @totoro-4, these 3 options make sense, but not sure why you would for example - want to select vertices used by 4+ vertex groups.

Added subscriber: @Sergey

Added subscriber: @Sergey
Author

I initially wrote the functionality to help with real time application performance. For instance, the Unity game engine only supports up to 4 vertex groups per vert, and it has options to set it to 1, 2, 3. Even if you are under the limits, it can have performance issues if you use too many groups-- depending on your mesh density, target OS, number of animated models, etc. Other applications may have different limits as well. Additionally, if you do go over the limits in Unity's case, you will end up with unexpected animation results and it can be difficult to figure out why.

I initially wrote the functionality to help with real time application performance. For instance, the Unity game engine only supports up to 4 vertex groups per vert, and it has options to set it to 1, 2, 3. Even if you are under the limits, it can have performance issues if you use too many groups-- depending on your mesh density, target OS, number of animated models, etc. Other applications may have different limits as well. Additionally, if you do go over the limits in Unity's case, you will end up with unexpected animation results and it can be difficult to figure out why.

Added subscriber: @mont29

Added subscriber: @mont29

Maybe we could add an enum/invoke behavior (to get short menu with three options above) as 'default access'? But think keeping generic 'advanced' behavior is indeed best, even if not directly exposed to user.

Too late in release cycle to merge this now anyway imho, will have to wait after 2.75.

Maybe we could add an enum/invoke behavior (to get short menu with three options above) as 'default access'? But think keeping generic 'advanced' behavior is indeed best, even if not directly exposed to user. Too late in release cycle to merge this now anyway imho, will have to wait after 2.75.

Added subscriber: @dfelinto

Added subscriber: @dfelinto

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
Dalai Felinto self-assigned this 2019-12-23 18:47:38 +01:00

Hi, thanks for your patch.

We are undergoing a Tracker Curfew where we are automatically closing old patches.

If you think the patch is still relevant please update and re-submit it. For new features make sure there is a clear design from the user level perspective.

Hi, thanks for your patch. We are undergoing a [Tracker Curfew ](https://code.blender.org/?p=3861) where we are automatically closing old patches. If you think the patch is still relevant please update and re-submit it. For new features make sure there is a clear design from the user level perspective.
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
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#33713
No description provided.