WIP: Fix #108880: Skin and Miffor modifiers cause mesh collapse #108915

Closed
Germano Cavalcante wants to merge 1 commits from mano-wii/blender:blender3.6-fix_108880 into blender-v3.6-release

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.

Before 4369627e71, the Mirror modifier merge did not interpolate customdata.

That merge just copied the customdata from the original vertex. Thus, flags like MVERT_SKIN_ROOT were kept.

#108880's solution would be simple if it weren't for one detail: the Skin mod requires only one "root" per island.

For that reason, this commit does two things:

  • copies the flags MVERT_SKIN_ROOT and MVERT_SKIN_LOOSE from the skin to the resulting vertex.
  • Removes the MVERT_SKIN_ROOT flag from different roots on the same island.
Before 4369627e71, the Mirror modifier merge did not interpolate customdata. That merge just copied the customdata from the original vertex. Thus, flags like `MVERT_SKIN_ROOT` were kept. #108880's solution would be simple if it weren't for one detail: the Skin mod requires only one "root" per island. For that reason, this commit does two things: - copies the flags `MVERT_SKIN_ROOT` and `MVERT_SKIN_LOOSE` from the skin to the resulting vertex. - Removes the `MVERT_SKIN_ROOT` flag from different roots on the same island.
Germano Cavalcante added 1 commit 2023-06-12 23:37:20 +02:00
Germano Cavalcante changed title from Fix #108880: Skin and Miffor modifiers cause mesh collapse to WIP: Fix #108880: Skin and Miffor modifiers cause mesh collapse 2023-06-12 23:41:32 +02:00
Member

TBH I'm not sure it's worth the complexity to support the specific format the skin modifier needs here. It's clearly possible to do here, but I don't think it's really doable to maintain this data in general, especially given the performance cost. At least the behavior should be generalized a bit conceptually, so it won't just apply to this specific data type for the skin modifier (which will probably be replaced soon enough, like the other non-attribute types).

For example, another way to deal with this is to allow setting the root vertices after the merging. If the skin modifier used more generic inputs (attributes), that would already be possible with geometry nodes.

TBH I'm not sure it's worth the complexity to support the specific format the skin modifier needs here. It's clearly possible to do here, but I don't think it's really doable to maintain this data in general, especially given the performance cost. At least the behavior should be generalized a bit conceptually, so it won't just apply to this specific data type for the skin modifier (which will probably be replaced soon enough, like the other non-attribute types). For example, another way to deal with this is to allow setting the root vertices _after_ the merging. If the skin modifier used more generic inputs (attributes), that would already be possible with geometry nodes.
Author
Member

Oh @HooglyBoogly, thanks for the feedback!
I believe I was a bit rash in considering multiple roots on the same geometry island a bug. There are many cases where multiple roots can appear like:

  • apply mirror modifier;
  • create an Edge connecting two islands each containing a root;
  • Merging vertices from different islands...

So this is quite common and not really a buug.

So I submitted a simple fix: f8617fe71b

(This PR can be good for reference in case we need a function that computes the islands in the future).

Oh @HooglyBoogly, thanks for the feedback! I believe I was a bit rash in considering multiple roots on the same geometry island a bug. There are many cases where multiple roots can appear like: - apply mirror modifier; - create an Edge connecting two islands each containing a root; - Merging vertices from different islands... So this is quite common and not really a buug. So I submitted a simple fix: f8617fe71b (This PR can be good for reference in case we need a function that computes the islands in the future).

Pull request closed

Sign in to join this conversation.
No reviewers
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
2 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#108915
No description provided.