models with applied subdivisions bugs mesh #79002

Closed
opened 2020-07-16 20:05:28 +02:00 by Anoca · 10 comments

Blender Version
2.83.1

Short description of error
Appearently, applying a subdivision modifier on the mesh first, and then applying the automatic weights leads to Bone Heat Weighting failure.
My guess is that there's either something wrong with the subdivision modifier, or the automatic weight system

Exact steps for others to reproduce the error

  1. Import a model which wasn't subdivided
  2. Apply subdivision surface on it
  3. Have a ready armature and use the automatic weights to bind the mesh to the bones

Blender gives you a Bone Heat Weighting error. If you won't apply the subdivision surface on the model FIRST, blender will apply automatic weights with no issues

**Blender Version** 2.83.1 **Short description of error** Appearently, applying a subdivision modifier on the mesh first, and then applying the automatic weights leads to Bone Heat Weighting failure. My guess is that there's either something wrong with the subdivision modifier, or the automatic weight system **Exact steps for others to reproduce the error** 1) Import a model which wasn't subdivided 2) Apply subdivision surface on it 3) Have a ready armature and use the automatic weights to bind the mesh to the bones Blender gives you a Bone Heat Weighting error. If you won't apply the subdivision surface on the model FIRST, blender will apply automatic weights with no issues
Author

Added subscriber: @Maker26

Added subscriber: @Maker26

Added subscriber: @Josephbburg

Added subscriber: @Josephbburg

Did you test the mesh before you applied the subdivision surface? Bone Heat Weighting failure shouldn't have anything to do with the resolution of the mesh. The heat computation fails for geometry that is non-manifold or otherwise weird. You will need to provide the .blend file, anyways, so this can be tested.

This does not occur in a simple test case (one bone, default cube before and after subsurf modifier applied). I don't think there is any kind of bug here.

Did you test the mesh before you applied the subdivision surface? Bone Heat Weighting failure shouldn't have anything to do with the resolution of the mesh. The heat computation fails for geometry that is non-manifold or otherwise weird. You will need to provide the .blend file, anyways, so this can be tested. This does not occur in a simple test case (one bone, default cube before and after subsurf modifier applied). I don't think there is any kind of bug here.

Added subscriber: @iss

Added subscriber: @iss

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

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

Please upload example file.

Please upload example file.
Author

In #79002#980586, @Josephbburg wrote:
Did you test the mesh before you applied the subdivision surface? Bone Heat Weighting failure shouldn't have anything to do with the resolution of the mesh. The heat computation fails for geometry that is non-manifold or otherwise weird. You will need to provide the .blend file, anyways, so this can be tested.

This does not occur in a simple test case (one bone, default cube before and after subsurf modifier applied). I don't think there is any kind of bug here.

I did test it, like I mentioned above, no error occurs if I don't apply any subdivision surface on the mesh. if this doesn't happen on a model made in blender, then does that mean that this only happens on models made in maya and exported into blender? Cause this mesh that I am having trouble binding the weights on is made in maya.

> In #79002#980586, @Josephbburg wrote: > Did you test the mesh before you applied the subdivision surface? Bone Heat Weighting failure shouldn't have anything to do with the resolution of the mesh. The heat computation fails for geometry that is non-manifold or otherwise weird. You will need to provide the .blend file, anyways, so this can be tested. > > This does not occur in a simple test case (one bone, default cube before and after subsurf modifier applied). I don't think there is any kind of bug here. I did test it, like I mentioned above, no error occurs if I don't apply any subdivision surface on the mesh. if this doesn't happen on a model made in blender, then does that mean that this only happens on models made in maya and exported into blender? Cause this mesh that I am having trouble binding the weights on is made in maya.

No, it makes no difference where the model came from. Please upload an example file.

No, it makes no difference where the model came from. Please upload an example file.

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

Changed status from 'Needs User Info' to: 'Archived'
Richard Antalik self-assigned this 2020-07-31 15:14:04 +02:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
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
3 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#79002
No description provided.