Sculpting: glitches after undoing a Dyntopo stroke #77974

Closed
opened 2020-06-18 00:21:35 +02:00 by Andrew Allen · 16 comments

System Information
Operating system: Windows 10
Graphics card: NVIDIA GeForce RTX 2060

Blender Version
Broken: 2.83 and 2.90 Alpha
Worked: I remember this not being an issue in one of the Sculpt Branch versions. I believe is was 2.81.

Short description of error

After turning on Dyntopo, changing the Detail Size, then drawing a stroke, if I immediately undo the stroke, the mesh bugs out, and Dyntopo is automatically turned off.

NOTE: The mesh bugging out seems to be fairly inconsistent. Sometimes when working on my sculpts, after changing the Detail Size, drawing a stroke, then undoing, the vertices will bug out and the colors will change, but sometimes they won't. It's hard to tell what's really causing the issue. What is consistent though, is the fact that Dyntopo always turns off after doing the steps below.

Exact steps for others to reproduce the error

  1. Enter Sculpt Mode.
  2. Turn on Dyntopo for any brush.
  3. Change the Detail Size to a different value.
  4. Draw a stroke on the mesh.
  5. Undo the stroke you made.
  6. The mesh will bug out, having some of the vertices mess up and/or having some of the mesh change color. Dyntopo will also be Unchecked.

Screenshot:

image.png

Temporary Fix:

  1. Switch out of Sculpt Mode, then Switch Back into it.
  2. If you are still seeing the weird colors on the mesh, turn on Dyntopo again, and draw a stroke on the mesh. Should get rid of the colors.

This temporary fix is fine for getting rid of the screwed up vertices and weird colors, but the fact that Dyntopo is turned off every time I change the Detail Size, draw a stroke, then immediately undo, is pretty annoying. I can work around it, but it's definitely an inconvenience.

**System Information** Operating system: Windows 10 Graphics card: NVIDIA GeForce RTX 2060 **Blender Version** Broken: 2.83 and 2.90 Alpha Worked: I remember this not being an issue in one of the Sculpt Branch versions. I believe is was 2.81. **Short description of error** After turning on Dyntopo, changing the Detail Size, then drawing a stroke, if I immediately undo the stroke, the mesh bugs out, and Dyntopo is automatically turned off. **NOTE:** The mesh bugging out seems to be fairly inconsistent. Sometimes when working on my sculpts, after changing the Detail Size, drawing a stroke, then undoing, the vertices will bug out and the colors will change, but sometimes they won't. It's hard to tell what's really causing the issue. What *is* consistent though, is the fact that Dyntopo always turns off after doing the steps below. **Exact steps for others to reproduce the error** 1. Enter Sculpt Mode. 2. Turn on Dyntopo for any brush. 3. Change the Detail Size to a different value. 4. Draw a stroke on the mesh. 5. Undo the stroke you made. 6. The mesh will bug out, having some of the vertices mess up and/or having some of the mesh change color. Dyntopo will also be Unchecked. **Screenshot:** ![image.png](https://archive.blender.org/developer/F8628951/image.png) **Temporary Fix:** 1. Switch out of Sculpt Mode, then Switch Back into it. 2. If you are still seeing the weird colors on the mesh, turn on Dyntopo again, and draw a stroke on the mesh. Should get rid of the colors. This temporary fix is fine for getting rid of the screwed up vertices and weird colors, but the fact that Dyntopo is turned off every time I change the Detail Size, draw a stroke, then immediately undo, is pretty annoying. I can work around it, but it's definitely an inconvenience.
Author

Added subscriber: @aallen170

Added subscriber: @aallen170
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

I cannot redo it on 7dae6eb5a2 .Which version did you test ?

I cannot redo it on 7dae6eb5a2 .Which version did you test ?
Ankit Meel changed title from [SCULPTING] After turning on Dyntopo, changing the Detail Size, then drawing a stroke, if I immediately undo the stroke, the mesh bugs out, and Dyntopo is automatically turned off. to Sculpting: glitches after undoing a Dyntopo stroke 2020-06-18 05:52:37 +02:00
Author

I tested it on both 2.83 and 2.9 Alpha. Would it have something to do with my Graphics Card?

I tested it on both 2.83 and 2.9 Alpha. Would it have something to do with my Graphics Card?
Member

I tested it on both 2.83 and 2.9 Alpha

Please also mention hash

Would it have something to do with my Graphics Card?

Can't tell without knowing the driver version. But it's good to stay updated.

> I tested it on both 2.83 and 2.9 Alpha Please also mention hash > Would it have something to do with my Graphics Card? Can't tell without knowing the driver version. But it's good to stay updated.

Added subscriber: @Foaly

Added subscriber: @Foaly

Probably the same bug: #75846
Back then we were unable to reproduce.

Probably the same bug: #75846 Back then we were unable to reproduce.
Member

@Foaly are you able to redo it now ?
as I said, I cannot. Is it GPU specific ?

@Foaly are you able to redo it now ? as I said, I cannot. Is it GPU specific ?

@ankitm I cannot reproduce it with the instructions here.
I can reproduce it with the file from #75846 (as mentioned there).

I also know of a related situation where (apparently) incorrect face sets are present:

  • Add a Cube (A)
  • Enter Sculpt Mode
  • Exit Sculpt Mode
  • Add a second Cube (B). (Do NOT duplicate Cube A)
  • Join both cubes.
  • Enter Sculpt Mode
  • Cube B will appear colored. The color will disappear on sculpting with Dynamic Topology enabled.
@ankitm I cannot reproduce it with the instructions here. I can reproduce it with the file from #75846 (as mentioned there). I also know of a related situation where (apparently) incorrect face sets are present: * Add a Cube (A) * Enter *Sculpt Mode* * Exit *Sculpt Mode* * Add a second Cube (B). (Do **NOT** duplicate Cube A) * Join both cubes. * Enter *Sculpt Mode* * Cube B will appear colored. The color will disappear on sculpting with *Dynamic Topology* enabled.
Member

Oh I can redo the bug with that, Thanks!
So IMO best is to confirm that in a new report, close #77974 and #75846 as its duplicates and revisit them when the new report is fixed.

Oh I can redo the bug with that, Thanks! So IMO best is to confirm that in a new report, close #77974 and #75846 as its duplicates and revisit them when the new report is fixed.
Author

In #77974#956570, @ankitm wrote:

I tested it on both 2.83 and 2.9 Alpha

Please also mention hash

2.83 Hashes:

MD5: a10762e5f1ff93f0fe48202ab3bef700
SHA256: fff0fc02b284df4dfcc1568b5c9a5ea9fe47f3c6f77c5c52f71eb7f44255c34d

2.9 Alpha Hashes:

MD5: ef577af8891746c5a0fd3e876412a6fd
SHA256: 94bb0a75ae0cd1e31cfd733fd839914b991329851fd46ade1b18cb1a8684299d

Also, I looked at the other issue and it's very similar to mine. I guess this bug is still being looked into?

> In #77974#956570, @ankitm wrote: >> I tested it on both 2.83 and 2.9 Alpha > Please also mention hash 2.83 Hashes: **MD5:** a10762e5f1ff93f0fe48202ab3bef700 **SHA256:** fff0fc02b284df4dfcc1568b5c9a5ea9fe47f3c6f77c5c52f71eb7f44255c34d 2.9 Alpha Hashes: **MD5:** ef577af8891746c5a0fd3e876412a6fd **SHA256:** 94bb0a75ae0cd1e31cfd733fd839914b991329851fd46ade1b18cb1a8684299d Also, I looked at the other issue and it's very similar to mine. I guess this bug is still being looked into?

Added subscriber: @iss

Added subscriber: @iss

They meant git commit hash (next to version like d994391e0c). It will be auto-filled in when you click on Help > Report a Bug.

@ankitm Not sure if we should close as duplicate since @Foaly can reproduce other one but not this one. But I agree on making new report if there is (yet) another method to trigger this issue.

In any case I wasn't able to confirm this one as well.

They meant git commit hash (next to version like `d994391e0c`). It will be auto-filled in when you click on Help > Report a Bug. @ankitm Not sure if we should close as duplicate since @Foaly can reproduce other one but not this one. But I agree on making new report if there is (yet) another method to trigger this issue. In any case I wasn't able to confirm this one as well.
Member

But I agree on making new report if there is (yet) another method to trigger this issue.

#78125 (Face sets: glitch in sculpt mode after joining two objects. )
Please edit the title if it's wrong.. I don't know a lot about it.

> But I agree on making new report if there is (yet) another method to trigger this issue. #78125 (Face sets: glitch in sculpt mode after joining two objects. ) Please edit the title if it's wrong.. I don't know a lot about it.
Member

In #77974#962099, @ankitm wrote:
#78125 (Face sets: glitch in sculpt mode after joining two objects. )

So that is intended behaviour apparently.

> In #77974#962099, @ankitm wrote: > #78125 (Face sets: glitch in sculpt mode after joining two objects. ) So that is intended behaviour apparently.

Closed as duplicate of #80174

Closed as duplicate of #80174
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
4 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#77974
No description provided.