AbnRanger

This video might offer some good practices to use in such situations.

I did a quick test and can confirm that there is a bug. I will report this immediately and hopefully we will see a fix in the next build

Yeah, as Carlos said, it appears that a stencil is active, and is the reason this pattern is appearing.

I don't think so. Another option is to go to the GEOMETRY menu and choose SEPARATE DISCONNECTED PARTS (the layer needs to be in Surface mode). Assign a hotkey to that menu option and the next time you want separate a part quickly, you can just hit that hotkey and 3DCoat will do it for you.

Sabastian, it's understandable to have some frustrations, but what Carlos suggested is actually not a work-around. If a user has multiple objects on the same Sculpt Tree layer, they are indicating that they want them all to be treated as a single unit/object. The Pose Tool is actually a more advanced TRANSFORM tool, and thus it can do things the TRANSFORM tool cannot do. I have asked Andrew to change the name so new users understand this without the need of a tutorial. You can also have 3DCoat separate individual objects on the same layer, so that they are completely independent. With your layer in Surface mode, go to the GEOMETRY menu and choose SEPARATE DISCONNECTED PARTS.

Thanks, but for some reason the recording lasts about 32 seconds, so I didn't get to see the part where the brush performance stuttered or anything. I am very curious about this because AMD is coming out with a new series of CPU's that can get up to 5.7Ghz with it's own default OC/boost

Yeah, but the more the number of people ask for the same thing, the more priority it gets.

Okay. I was wondering if maybe the Voxel Paint Depth (in the Tool Options panel) was a bit too thin, but knowing this happens just when you save, seems like a bug for sure. Can you go to the HELP Menu and send that workfile to Support and then email (support@pilgway.com) to explain what steps you were taking to produce this? Andrew will probably have it fixed by the next build.

+1. I have asked Andrew about this before, as well. Would be a very welcome addition.

Sabastion, does it do this when you hit the CTRL + S hotkey combination, to save? Is this a Sculpt Object (object either imported into or created from scratch in the Sculpt Workspace) or Paint Object (Object...usually a low polygon UV mapped model...imported directly into the Paint Workspace, or a copy of a Retopo mesh after baking sculpt details from a Sculpt object)?

Could you screen record this happening, using a default object like the Splash Screen > Voxel Sculpting > Bust? Maybe increase the resolution to where it is about 1-2 million triangles (count is visible at the bottom of the UI, in the status bar) and try to test it? If it is still a problem, letting Andrew see that it indeed is, can be a huge assist. He used OpenGL acceleration to a few other Voxel Brushes (Fill, Grow and Smooth) and perhaps this will compel him to apply it to Airbrush also.

There could be a bug, but I think I would try a few "house cleaning" tips before proceeding. 1) Delete the empty Piston head Retopo group layer...Autopo always creates it's own new layer using the name of the voxel object 2) RMB click the Voxel layer (Piston Head) and choose FILL VOIDS and then RMB click the layer and choose TO GLOBAL SPACE 3) Switch the layer to Surface mode and then in the GEOMETRY menu (Sculpt Workspace) choose SEPARATE DISCONNECTED PARTS. This should separate those rings on the side, which I think could be messing with the Algorithm since it is so close to the actual piston head. It seems to me that making that its own separate object would give you MUCH, MUCH cleaner results. 4) Choose a lower estimated polycount at the top of the Autopo wizard. 50k seems a bit high. Maybe 20-30k? 5) During the calculation I could see a mess of green strokes. I would recommend clearing those. At the bottom of the Autopo wizard, there is an option to bypass strokes and details painting. Uncheck that and see if those strokes appear when you get to the STROKES creation stage. If you see any, go to the section of the tool panel, called SPECIAL and hit the CLEAR button. That should clear that mess of strokes, which I think is the biggest culprit, here.

Please send support@pilgway.com this feature request. I have made the same request multiple times over the past 5 years or so. The more users who request a given feature, the higher the priority it gets. There are different tools that make use of procedural NOISE, and all of them could use a nice large library to choose from. Even the FILL tool has more procedural noise types than what is available in the Smart Materials panel. I wish Andrew would make those and other noise types available. There is a large opensource noise library called Bercon Maps, which is used in 3dsMax. I wish Andrew would try to add these procedural maps to all the Noise-based tools in 3DCoat, including the NOISE tool in the Sculpt Workspace. https://github.com/Bercon/BerconMaps

RMB clicking on a Voxel layer > FILL VOIDS is always a good idea, in case there are any voids inside the volume which can mess with the Auto-Retopo algorithm.

Can you screen record what is occurring in your Viewport/UI when you try to do this? A lot depends on the shape/complexity of the object, and the estimated polycount.