BUG: Remeshing Artifacts

[nimajneb]

Having some problems with ZSpheres, Remeshing and combining of subtools. I created an armature for a pelvis with zspheres/zsketch and then went in and started filling in areas. These images are from an early stage.

Basically, Remesh is putting in mesh where there was none in the component parts. I’ve marked the area in red in the images. These little nodes crop up in many areas in the later stages of this piece, making the remesh unusable. What’s odd to me though is that the zspheres unified skin technology doesn’t seem to have this problem. Shapes like this in zsketch will unified skin fine. If they were part of the same subtool, their unified skin wouldn’t show these artifacts.

Other problems I ran into with Remesh:

1. ZSphere/ZSketch subtools need to be set in their preview modes to remesh. This one is known and mentioned in a couple of posts on ZBrush Central, but no where in the docs.

2. Remeshing proceeds down the stack from your selected subtool. It doesn’t matter if the ones above it are visible; higher than the selected elements do not seem to play a role in the remeshing operations. In this case, if the armature was the first subtool and I selected the filling parts below it and did the remesh, the result was only a remesh of the fillers. Swapping the two in the stack resulted in an only armature remesh. Only by selecting the top element in the subtool stack could I get them to union.

Attachments

[MarioBlanco]

before remesh, clone the subtool you want to…try it

[nimajneb]

before remesh, clone the subtool you want to…try it

Not quite following you, Andre. What do you mean by “clone the subtool you want”? I want a union of two subtools (w/o the artifacts). How will cloning one of them help? And do you mean clone to another subtool? A separate tool?

[MarioBlanco]

ok, if i understand well:
1.-If you wanto the union of two subtool, press the merge down button
2.-For that purpose you dont need remesh all
3.-Using the clone allow you to preserve intact the original mesh and play with the cloned subtools avoiding bizarre results with remesh all
4.-Remesh all is at least to have a base mesh to work on it
let me knowif this help you, and excuse i was not clear …

[nimajneb]

That would indeed work to give me a mesh without the artifacts, Andre. It is one thing I tried in the process of figuring out what was happening with remesh’s stack order. What I didn’t like about merging was the funky intersections that it makes between tools. Remesh surface is simpler (though wrong in the case of the artifacts). Still, there are ways, as you explain, to work around it. The point of my posting the thread though is to note that remesh is doing something I don’t think it should be, creating those artifacts. It’s not following the base volumes and I’m wondering why that is and if it can be fixed.

[zber2]

Did you play around with the resolution and polish sliders to see if you could get a better result?

[nimajneb]

zber2: Ayep, I did tweak around with those, but not to much effect. What they did do though is show me the artifacts more clearly when I turned up the res. These pictures are from the final zsketch (all I have here at home). You can see the the bowl of the pelvis is open, but after the remesh there’s all sorts of garbage thrown in there. What’s very odd about the garbage though is that is you look at the sketch from orthogonal views, you can’t see it. It’s almost like on the inside it’s doing something like a shadow box and just projecting the outside contours and generating an intersection. What I expected was a voxel based snapshot of my mesh, but that’s not what’s happening. It’s very odd. I left polish off on the remesh, so we can see exactly the solution that’s it’s calculating from the base.

Attachments