A fix has been committed Fix Subdivide, Reshape and Apply Base
I hope it works
@kosirm Why you deleted your āhonestā post?
Layered sculpting is "less important, extra polish, nice to have".
Thanks for this info, well yeah, sometime I feel like who am I to talk⦠Sorry. But I really think what I said
Ok, I will re-post itā¦
Hi, I would like to speak in the name of sculptors⦠I actually donāt believe that anyone from core team is reading this, but anyway⦠Multiresolution sculpting is CORE functionality of any sculpting app (ZBrush, 3DCoat, Mudbox⦠you name it), and all these apps are built arround that. Please look how elegantly and user friendly you can sculpt in multiple layers (not only multiple resolutions!) in Mudbox. And this stuff is more than 10 years old!!! Blender folks like to talk about pioneering, but you canāt pioneer nothing if core functionality is broken. Subdivide, Reshape and Apply base⦠all this looks like hacky workarround. Iām aware that Blender is completely different beast than some sculpting app, because it has ALL - modeling, rigging, animation and whatnot⦠and it is not the same story to integrate multires sculpting in Blender and do the same thing in some pure sculpting app.
But PLEASE, PLEASE, PLEASE, before you decide to introduce some gardening or vacuum cleaning feature in Blender, take a highly skilled contractor and do it once and for all, if Pablo Dobarro is not capable⦠I mean, he is excellent developer and also talented artist, but he is not god, I suppose
Please do this for all of us sculptors, who LOVE Blender>!
These descriptions arenāt really valid for this, they are generic ones from all modules pages but not every module uses them the same way. In this case itās just a relative ranking of long-term projects in the sculpt module.
This is the difficulty with having an open development process. If youāre just talking between developers within a company everyone knows what is meant by this, and for any external communication you take extra care. But if itās all in the open people will nitpick things like this.
We could rank everything as high priority but that would be meaningless. The point is just that core multires improvements and performance improvements were decided to be higher priority, before adding more features like layering. Adding those while the core architecture is changing would not work well.
We are reading these topics.
Multires is being worked on right now. Concrete next steps are here:
https://developer.blender.org/T73317
I donāt think official Blender communications are actually claiming this. We know there is still a big gap with dedicated sculpting apps. We canāt control what users say though.
These are fundamental operations in any sculpting app, they might just have different names or happen automatically under the hood. If you look at the planned task you will see that for example we are planning to automate apply base.
So good to know
Thanks for reply! Thank you for all information you gave me⦠hopefully in the near future I will be able to do all the work in Blender and I wonāt have to jump to other apps for sculpting.
Yeah, that was harsh, appologies to Blender team!
Thanks, yes I read that and tested immediately
So, to show you that Iām serious about this, I give you my promise:
the one who will implement multires sculpting on non-top level, will earn my lifetime ZBrush license ($895 value)! You can use it for further comparison with industry leaders
Wow that was incredibly fast! Hat off! Please PM me the name of the new ZBrush owner. Cheers!
I want to give little feedback on current MultiRes. The case is fairly straightforward:
- A mesh with 1 milion poly.
- 3 render/sculpt MultiRes layers on top of it.
- MultiRes is hidden in viewport.
- Go into edit mode.
- Add between 15-20% more mesh - extrude part of the mesh, add loop-cuts to match the original 1kk mesh density.
After applying loop cuts the RAM usage spiked and plateau at around 95GB. The CPU is used between 50-70% on all threads. And it sits on this for over 13 hours now, as Iām writing this post.
The CPU usage is indicating that some work is beeing done:
But I donāt know if this is some kind of bug with neverending loop, and I should break it. Or itās just taking so long for MultiRes to be updated to new mesh size.
I should add that CPU usage spikes are not repetitive.
Thank you for your efforts.
Yes for me it would be very important to make shapekeys on multires layers. Itās also important for the DAZ Genesis figures with HD-Morphs imported with the Diffeo DAZtoBlender tool. Till now itās not possible to handle the HD-Morphs of DAZ figures. We realy need shapekeys wich works on multires Layers.