Page MenuHome

Mask brush freezes with "Topology Automasking"
Closed, ArchivedPublic

Description

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: Radeon RX 560 Series ATI Technologies Inc. 4.5.13558 Core Profile Context 26.20.11015.5009

Blender Version
Broken: version: 2.81 (sub 13), branch: master, commit date: 2019-10-04 22:33, hash: rBab519b91b2c4
Worked: (optional)

Short description of error
Mask brush freezes with "Topology Automasking" option

Exact steps for others to reproduce the error
-add a high poly object
-go into sculpt mode
-activate the option "Topology Automasking"
-use the mask brush
-detect

[Based on the default startup or an attached .blend file (as simple as possible)]

Event Timeline

@Pablo Dobarro (pablodp606), can you confirm this?
For me sculpt mode usually works with highpoly meshes.
So such a problem would be easily detected.

The smooth brush was initializing the connectivity data before each stroke, but the mask brush is not doing anything special as far as I know. I've never had any performance problems with it.

Germano Cavalcante (mano-wii) lowered the priority of this task from 90 to 30.Oct 8 2019, 5:47 PM

@Igor (unumex), we need more information.
Could you provide a simple file demonstrating the problem?

I'm sorry. The problem was in the new option "Topology Automasking". If you activate it, the mask brush starts to lag.
https://youtu.be/pj_--qL27BU

Igor (unumex) renamed this task from Mask brush freezes on highpoly mesh to Mask brush freezes with "Topology Automasking".Oct 9 2019, 5:48 PM
Igor (unumex) updated the task description. (Show Details)

Yes, that is expected. It needs to initialize the automasking factors from that vertex each time you start a stroke. The more vertices you have in your sculpt the slower it is.
We can improve this in future releases by limiting the topology initialization to nodes that are visible inside the viewport.

Germano Cavalcante (mano-wii) changed the task status from Unknown Status to Unknown Status.Oct 9 2019, 8:50 PM

Closing since it is a known limitation.