MADjestic

Hey guys, I see that the custom brush creation works differently for Voxel sculpting (incl. surface mode) and LiveClay. Where the former allows a separate menu with presets to be saved, the latter allows duplicating existing brushes. I wonder where future releases of 3d-coat are heading, what's the preferred pipeline, in regards to custom brushes presets? (here I mean the brush parameters such as smoothing, falloff, inverse, etc. I am less concerned with custom alpha maps). Regards, Vlad

The 'pixelated' effect that you mention is due to aliasing. Anti-aliasing techniques is a well studied subject. Rather than being upset and going on rant how this techniques is useless to you, I suggest to take a look on the bright side of things. Good job, Andrew! Definitely something useful, especially if the painted attribute values can be exported from 3DC together with the mesh.

Wow, great build for OSX - it actually works, yay! 30 mins of doodling and no crash or explosions of LC. I noticed once that som LC brush effect 'exploded' the back surface of the cavity, however 'Undo' worked and LC behaved as expected. Great job, guys!

Yay! Thanks Andrew! You've got another tester-complainer aboard.

It seems to me that there's a sense of confusion, concerning the Smooth/TSmooth toolset. Fashtray, don't you think that, as a rule of thumb, it is better to have a 'smart' tool, that 'just works' from the begining, but then allows 'advanced' options for those who actually care for the difference? That's coming from somebody being a tool-maker for artists himself. And, frankly speaking, it is a much better experience to enjoy 3D Coat for just "sculpting stuff", without getting into technicalities of smoothing algorithms, unless for a real necessity Otherwise - can't wait for OSX build to try the goodness out! Good work!

Yep, I second that. Could be a nice UI navigation touch. Controller sensitivity as a function of the distance between the camera position and the point of interest/focal point. It could be effecting dolly/pan/zoom all together, but even better if there was an advanced option to tweak responsiveness per component (separate sensitivity curves per dolly/pan/zoom components) with some 'nice' defaults ofcourse. Can we has it?

OSX users are ready to jump onto the beta-testing bandwagon, as soon as OSX build is available.

First of all, thank you, Raul, for your hard work - it is not unnoticed, I am eager to share praise, you truly deserve it! As far as complains go - you set the bar high, so it is your own fault most people can clearly see the potential and expect nothing less than that. Now, whenever you introduce a new piece of technology, it's being perceived in the context of this imaginary super-goal, rather than "at least he did something" as in development for open-source community where there are no strict obligations or expectations, based on software price or contract. That's what makes it different, but there's one more much important thing in common, between Blender Unlimited Clay and 3DC Live Clay, and Ketano mentioned it - 3DC team, together with you, are pushing the technology of CG Art to and though the new limits, and it is exciting to be part of it.

And that's exactly what happened. Shall we start another off-topic now? You can always Private Message the Moderator if you disagree with a decision. Or do you consider the importance of your personal matter sufficient to keep hi-jacking the topic? I thought you already agreed above that the matter was not appropriate to the topic of the discussion?

Thanks, Andrew! That's exactly what SketchTool has been missing to let this gem shine. Now, anybody willing, can enjoy the precision and clear limits of projection sculpting, wrapped up inside a nice interface, all inside 3DC! Best luck with that, And, traditionally with all the new features sneak-peaks storming the community - can't wait to try them out!

My excitement is such, that a friend of mine will soon start taking hostages - just too try out the new brushes pack!

Proof-link or didn't happen :P

There are objective differences between the representations of surface data as voxels, and as polygons. Quite naturally, as long as the complexity of your model remains below a software/hardware limitations, results, as long as the toolset is consistent, would be nearly identical, irrelevant to whether it is polys or voxels. However, if one exceeds such limits, one hits objective limitations of voxel representation (higher complexity -> higher price => lower sculpting complexity threshold). Obviously enough, the desired level of complexity is a subjective thing, but so is your preference, possibly, to use 3dcoat voxel engine for lower resolution sculpting. Until we get an optimized voxel engine that is on par with the capacity of the poly engine in every way, and gives additional advantages unique to voxels - certainly, one would never have a reason to go back to polys, but that has not happened yet, has it? One may argue - why investing in poly-surface modeling, rather than investing further into voxel modeling? Raul is well known for his work related to Unlimited Clay in Blender (and LiveClay for 3dCoat), in a way, it's his speciality here - that's his contribution to 3dcoat. Possibly Andrew could overhaul the voxel engine, but I can imagine him being quite busy with 3dcoat upscaling and working on many other aspects of the application and toolset. That is a tremendous task, in accomplishing wich I wish them all best.

Woohoo! Is it in the builds yet? My hands are itching!

Great news, Raul! Thanks for your great work. LiveClay and Crease-like brush functionality were some of the longest awaited features for me Yay! As far as some impatient words written above - yes, development process takes time, especially knowing how it works with the story of 3D Coat - is it even a surprise? Nevertheless, I totally understand that "can't wait" feeling - seeing 3DCoat shaping up and being "almost there" - it's almost painful too see some feature not being quite there yet or or missing, or installing the latest build and finding something broken... Oh well, when was it not the case with betas? So, please excuse the impatience and emotions - it's so human and understandable and, ironically, comes out of best intentions, isn't it? Or it's just a bad demeanor Best wishes, Vlad