![]() That would avoid the hashing, which I expect to be rather slow and memory intensive. Is having a layer exist for only part of the vertices really important, is that how other software works? I was expecting sculpt layers to exist for all vertices. It’s reasonable to ignore that for now though and make one case work well first. The proposal mostly deals with the dynamic topology bmesh case I think, it’s not entirely clear to me how it extends to multires for example. The main complexity here is dealing with the different mesh representations, there are regular meshes, multires meshes and dyntopo bmeshes. Write to disk, Expose to UI and Create the UI To be continued in part 2 (the focus of further research and investigation) when exiting sculpt mode delete CustomData and rewrite it to match current layer data. ![]()
0 Comments
Leave a Reply. |