I am using an RTX 2080 laptop. Thanks for testing. Will do some troubleshooting to see what might be causing the lagging.
We got a few changes in the latest patch notes for Sculpt Mode. Now more operators are disabled based on objects being invisible or not.

Does anyone know why this is happening?
Iām using multires
Blender 4.0.2
Maybe thereās automasking activeā¦?
There is no automask, start a new file for testing, unfortunately this anomaly continues!
jpg in the brush alpha is scary. does it happen if you try a different image tiff psd png⦠?
The best format for large displacements in Blender is .exr actually (as the GPL does not allow Blender to have proper support for the proprietary .psd format). EXR is an open format.
Why it works is because their format supports what is known as deep color (a standard 32-bit color depth is insufficient if you are using a very high mesh resolution).
Yes, I used TIF and the error continues
I will write this text
Itās discouraging to think about converting so much alpha, but if itās the solution, so be it!
canāt reproduce your issue!!!
i assume youāre using Anchored try to take of the alpha and just do it with the circle (standard brush falloff)
i just think itās a combination of low res in alpha + low res in mesh
subdivide more and see if the effect change
something else i noticed if youāre using a tablet in the test, try to disable the pressure for the strength and see if itās the same behavior. or test with a mouse
Post the blend, people will be able to help you a lot better than just speculating.
test .blend (476.4 KB)
The file
I have no issue with you blend file.
The brush does not seem to have a weird set-up.
So, I suppose problem is relative to image, you forgot to pack.
edit:
was curious and opended it in 3.6 and there is a big difference!!! so there is an issue i think ![]()
big difference between 3.6 and 4.0.2 with the same alpha . he is right
test .blend (2.2 MB)
Pack
I edited my post above: no need for the texture it is an issue in this version
I used 3.6 and the difference is dramatic
That is relative to Front Faces Only option.
Yes, it is because Front Faces Only is checked. But it must be a bug in 4, because it works fine in 3.6 with that option active⦠![]()
I think itās worth a bug report
