Multires & Undo & Frame Change causes weird behaviour with shapekeys #76842

Closed
opened 2020-05-17 23:21:48 +02:00 by Joseph Brandenburg · 12 comments

System Information
Operating system: Kubuntu 19.10
Graphics card: Nviia GTX 1080 (driver 440)

Blender Version
Broken: 2.90.2; 20202-05-15 19:12
Hash eaf7d36d66
Built by running "make full"

Short description of error
When using a multi-res mesh with certain shape-keys, bad results may occur. Create a multi-resolution modifier and subdivide with at least one shapekey active. While subdividing, artifacts may appear in the multiresolution levels. Even if they do not appear, sculpting, undo-ing, then changing frame causes a multi-res explosion.

Exact steps for others to reproduce the error
bug0001-2952.mp4

  1. Create a mesh and do some editing.
  2. Create a shapekey and do some editing. Modify the topology of the mesh in the shape key. (This bug seems to occur even if you don't modify the topology, but doing this seems to make it worse).
  3. Repeat step 2 as desired. The more, the messier!
  4. Optional: now edit the topology of the basis shape.
  5. Exit edit mode -- make sure at least one shapekey is enabled.
  6. Create a multiresolution modifer and subdivide a few times.
  7. Enter sculpt mode and do some sculpting.
  8. Undo
  9. Change frames

In Sculpt mode with multi-resolution, if I sculpt a bit, undo, then change frame, I get a multi-res explosion.

Additionally, the transform tools seem to cause the same explosion, without changing frame
I think that it's just any update to the depsgraph
So I want to know: Is it user error to use a mesh with shapekeys in Multires, especially a mess of broken shapekeys caused by editing the mesh/topology?
Or should Blender support even this case?
please @ me
This bug does not seem to occur if none of the shapekeys are enabled/ if their influence is set to 0.

My Observations:
It doesn't seem to matter what kind of shape keys are present- weird results will occur. The weirder the shape-key, however, the weirder the result.
After playing around with it, it even seems like causing a depsgraph update (in this case, by changing frame) simply causes Multires to add the shapekey's displacement to the current sculpt level. I do not know why undo is necesary to create the bug. Perhaps it is creates an outdated depsgraph? This doesn't seem to be related to the new undo system; I was able to get the bug with "Undo Legacy" enabled. I have not, however, tested this in older versions of Blender. I would be happy to do so.

I think the explosions that occur are not so much the product of bad shape-key handling, but rather, editing shapekeys in destructive ways is a good way of producing bad geometry that confuses multi-res. Have I found two bugs, then?

maybe related? #76769 #76313

**System Information** Operating system: Kubuntu 19.10 Graphics card: Nviia GTX 1080 (driver 440) **Blender Version** Broken: 2.90.2; 20202-05-15 19:12 Hash eaf7d36d66e5 Built by running "make full" **Short description of error** When using a multi-res mesh with certain shape-keys, bad results may occur. Create a multi-resolution modifier and subdivide with at least one shapekey active. While subdividing, artifacts may appear in the multiresolution levels. Even if they do not appear, sculpting, undo-ing, then changing frame causes a multi-res explosion. **Exact steps for others to reproduce the error** [bug0001-2952.mp4](https://archive.blender.org/developer/F8540444/bug0001-2952.mp4) 1. Create a mesh and do some editing. 2. Create a shapekey and do some editing. Modify the topology of the mesh in the shape key. (This bug seems to occur even if you don't modify the topology, but doing this seems to make it worse). 3. Repeat step 2 as desired. The more, the messier! 4. Optional: now edit the topology of the basis shape. 5. Exit edit mode -- make sure at least one shapekey is enabled. 6. Create a multiresolution modifer and subdivide a few times. 7. Enter sculpt mode and do some sculpting. 8. Undo 9. Change frames In Sculpt mode with multi-resolution, if I sculpt a bit, undo, then change frame, I get a multi-res explosion. Additionally, the transform tools seem to cause the same explosion, without changing frame I think that it's just any update to the depsgraph So I want to know: Is it user error to use a mesh with shapekeys in Multires, especially a mess of broken shapekeys caused by editing the mesh/topology? Or should Blender support even this case? please @ me This bug does not seem to occur if none of the shapekeys are enabled/ if their influence is set to 0. **My Observations:** It doesn't seem to matter what kind of shape keys are present- weird results will occur. The weirder the shape-key, however, the weirder the result. After playing around with it, it even seems like causing a depsgraph update (in this case, by changing frame) simply causes Multires to add the shapekey's displacement to the current sculpt level. I do not know why undo is necesary to create the bug. Perhaps it is creates an outdated depsgraph? This doesn't seem to be related to the new undo system; I was able to get the bug with "Undo Legacy" enabled. I have not, however, tested this in older versions of Blender. I would be happy to do so. I think the explosions that occur are not so much the product of bad shape-key handling, but rather, editing shapekeys in destructive ways is a good way of producing bad geometry that confuses multi-res. Have I found two bugs, then? maybe related? #76769 #76313

Added subscriber: @Josephbburg

Added subscriber: @Josephbburg

#80285 was marked as duplicate of this issue

#80285 was marked as duplicate of this issue

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

I can confirm this.

Here is example file, but you have to sculpt twice now to cause this bug. Not sure if this is best example file - it's very lazy version.
#76842.blend

I can confirm this. Here is example file, but you have to sculpt twice now to cause this bug. Not sure if this is best example file - it's very lazy version. [#76842.blend](https://archive.blender.org/developer/F8542648/T76842.blend)

Added subscriber: @KidTempo

Added subscriber: @KidTempo

Added subscriber: @PabloDobarro

Added subscriber: @PabloDobarro

it even seems like causing a depsgraph update (in this case, by changing frame) simply causes Multires to add the shapekey's displacement to the current sculpt level.

I've been doing some multi-resolution sculpting on a character and this bug has caused me to accidentally apply shape keys on the sculpt I was working on. I think this bug is important to address for production since it can cause artists to lose work in a way that is not easy to recover. Has @PabloDobarro seen this bug?

To be specific about my workflow: I have a human character. Her face has some asymmetrical details, so I use a shapekey to morph the symmetrical topology into the assymetrical shape. I use the shape key to preview what this will look like without affecting the symmetry of the sculpt, but at some point during the process I left it on, and now it is permanent because of the bug. I also use shapekeys to, perhaps, preview a pose before rigging, or to reshape soft parts of the body to fit into clothing meshes or the like. I don't think shapekeys/blendshapes are available in other sculpt software, so this could be a big advantage for Blender. It's certainly a convenient way of non-destructively testing things, when it works.

Thanks again

> it even seems like causing a depsgraph update (in this case, by changing frame) simply causes Multires to add the shapekey's displacement to the current sculpt level. I've been doing some multi-resolution sculpting on a character and this bug has caused me to accidentally apply shape keys on the sculpt I was working on. I think this bug is important to address for production since it can cause artists to lose work in a way that is not easy to recover. Has @PabloDobarro seen this bug? To be specific about my workflow: I have a human character. Her face has some asymmetrical details, so I use a shapekey to morph the symmetrical topology into the assymetrical shape. I use the shape key to preview what this will look like without affecting the symmetry of the sculpt, but at some point during the process I left it on, and now it is permanent because of the bug. I also use shapekeys to, perhaps, preview a pose before rigging, or to reshape soft parts of the body to fit into clothing meshes or the like. I don't think shapekeys/blendshapes are available in other sculpt software, so this could be a big advantage for Blender. It's certainly a convenient way of non-destructively testing things, when it works. Thanks again

Added subscriber: @JanezRupar

Added subscriber: @JanezRupar

Added subscriber: @CheesecakeCG

Added subscriber: @CheesecakeCG
Philipp Oeser removed the
Interest
Sculpt, Paint & Texture
label 2023-02-10 09:12:32 +01:00
Member

I can no longer reproduce this. I know this is an old report so I don't know if you are available right now @Josephbburg to confirm.
Leaving this open for now but will eventually close.

I can no longer reproduce this. I know this is an old report so I don't know if you are available right now @Josephbburg to confirm. Leaving this open for now but will eventually close.
Julien Kaspar added
Status
Needs Information from User
and removed
Status
Confirmed
labels 2023-04-18 18:49:53 +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.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2023-06-12 04:35:31 +02:00
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
6 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#76842
No description provided.