Undo several times after enabling dyntopo corrupts the mesh #86104

Closed
opened 2021-02-28 22:01:36 +01:00 by Leonid Sedov · 7 comments

System Information
Operating system: Linux-5.10.9-051009-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: Radeon RX 570 Series (POLARIS10, DRM 3.40.0, 5.10.9-051009-generic, LLVM 11.0.0) X.Org 4.6 (Core Profile) Mesa 20.2.6

Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: 02948a2cab
Worked: 2.91.2 works perfectly well
Short description of error
Opening a file with dyntopo enabled and clicking undo disables dynopo and corrupts the mesh. The same happens when creating a new file, clicking dyntopo, making any change to the mesh and clicking undo again.

Exact steps for others to reproduce the error

  1. File -> New -> Sculpting
  2. Enable dyntopo by clicking on the button on the toolbar to the right of mirror options (XYZ buttons).
  3. Draw one single line on the sphere
  4. Click Ctrl+z two times.
  5. Draw on the sphere again.

As a result, the dyntopo is disabled and parts of the mesh are broken (sometimes it creates holes, sometimes face sets), which can easily be tested by trying to draw on it again.

Clicking Ctrl+z again after drawing on the broken mesh seems to fix everything (at least in the simplest example with the default sphere).

I also tested it on my laptop on Windows where I did a fresh installation of Blender 2.92 build from the official website without any changes to any default settings and the result is the same.

It may look as a silly bug, but I believe that it affects me also long after this simple example, because I got my more complex mesh corrupted and dyntopo disabled after clicking Undo several times. The corruption is different: sometimes a subset of faces disappears, sometimes some new face sets appear.

I apologize if it is a known bug, I did my best searching on the bug tracker and didn't find anything relevant by the keyword "dyntopo".

blender_bug.png

**System Information** Operating system: Linux-5.10.9-051009-generic-x86_64-with-debian-bullseye-sid 64 Bits Graphics card: Radeon RX 570 Series (POLARIS10, DRM 3.40.0, 5.10.9-051009-generic, LLVM 11.0.0) X.Org 4.6 (Core Profile) Mesa 20.2.6 **Blender Version** Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: `02948a2cab` Worked: 2.91.2 works perfectly well **Short description of error** Opening a file with dyntopo enabled and clicking undo disables dynopo and corrupts the mesh. The same happens when creating a new file, clicking dyntopo, making any change to the mesh and clicking undo again. **Exact steps for others to reproduce the error** 1. File -> New -> Sculpting 2. Enable dyntopo by clicking on the button on the toolbar to the right of mirror options (XYZ buttons). 3. Draw one single line on the sphere 4. Click Ctrl+z two times. 5. Draw on the sphere again. As a result, the dyntopo is disabled and parts of the mesh are broken (sometimes it creates holes, sometimes face sets), which can easily be tested by trying to draw on it again. Clicking Ctrl+z again after drawing on the broken mesh seems to fix everything (at least in the simplest example with the default sphere). I also tested it on my laptop on Windows where I did a fresh installation of Blender 2.92 build from the official website without any changes to any default settings and the result is the same. It may look as a silly bug, but I believe that it affects me also long after this simple example, because I got my more complex mesh corrupted and dyntopo disabled after clicking Undo several times. The corruption is different: sometimes a subset of faces disappears, sometimes some new face sets appear. I apologize if it is a known bug, I did my best searching on the bug tracker and didn't find anything relevant by the keyword "dyntopo". ![blender_bug.png](https://archive.blender.org/developer/F9853525/blender_bug.png)
Author

Added subscriber: @leose

Added subscriber: @leose
Author

Actually, now when I am playing with it, it looks like the mesh is not corrupted, just a part of it is hidden as a result of clicking "Undo". Saving the scene with the "corrupted" mesh produced from my bug report and opening it again results in a mesh where the "corrupted" part is in a different face set.

bug_blender2.png

Please let me know if what I am describing in my bug report is too convoluted and I will figure out how to make a recording to demonstrate the problem.

Actually, now when I am playing with it, it looks like the mesh is not corrupted, just a part of it is hidden as a result of clicking "Undo". Saving the scene with the "corrupted" mesh produced from my bug report and opening it again results in a mesh where the "corrupted" part is in a different face set. ![bug_blender2.png](https://archive.blender.org/developer/F9853626/bug_blender2.png) Please let me know if what I am describing in my bug report is too convoluted and I will figure out how to make a recording to demonstrate the problem.

Added subscriber: @TheRedWaxPolice

Added subscriber: @TheRedWaxPolice

Hmm, sounds like the same issue as this: #85989 (Sculpting error ) 🤔

Hmm, sounds like the same issue as this: #85989 (Sculpting error ) 🤔
Author

In #86104#1120876, @TheRedWaxPolice wrote:
Hmm, sounds like the same issue as this: #85989 (Sculpting error ) 🤔

Yes, I believe it is the same bug. Should I duplicate the steps mentioned here to that bug report? I am not sure what is the protocol for such cases.

> In #86104#1120876, @TheRedWaxPolice wrote: > Hmm, sounds like the same issue as this: #85989 (Sculpting error ) 🤔 Yes, I believe it is the same bug. Should I duplicate the steps mentioned here to that bug report? I am not sure what is the protocol for such cases.

In #86104#1120878, @leose wrote:
Should I duplicate the steps mentioned here to that bug report? I am not sure what is the protocol for such cases.

Don't worry about that... Some staff member will merge those reports soon enough... 😎

> In #86104#1120878, @leose wrote: > Should I duplicate the steps mentioned here to that bug report? I am not sure what is the protocol for such cases. Don't worry about that... Some staff member will merge those reports soon enough... 😎
Member

Closed as duplicate of #85989

Closed as duplicate of #85989
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#86104
No description provided.