I agree, 3DCoat for sculpting is totally not at the standard of ZBrush - but I’m also wondering if there’s a bit of modification of workflow to get it to work the same way. Like we’ve had this way of working with ZBrush for years, and that’s why we’re so fast, but the fun question is how to we analyse our own workflow and start to create equivalencies in other tools. I’ve started with some of that, as time allows, and with some help, but this weekend has been a question of how do we want to proceed if we can see the future of ZBrush marked by Maxon’s very first action: without any information or knowledge about future plans or updates, they immediately change the licensing terms and start rolling out upgrade costs that reflect what they think we’ll pay for it rather than what they’re adding that justifies that.
3DCoat is certainly not slow, at least not on my hardware, and it’s not wanting for brushes - and I hadn’t paid much attention to it because I use Houdini and it has vellum for cloth, and that’s a real simulation. But apparently cloth dynamics have been in 3DCoat for about five years. They are, in fact, far more stable and accurate compared to Zbrush dynamics I guess simply because like Houdini it can use the GPU for far more accurate floating point calculations. And it can certainly beat ZBrush in terms of polycount - there’s no memory or cache based limits.
Thing is, in our team here we have no reason to upgrade ZBrush but every reason to start exploring alternatives - Maxon’s recent history with Forger (Forger Classic abandoned, the exact same program released as Forger Subscription) concerns me.
If we plan to use 3DCoat for retopo and UV instead of Houdini anyway, then we already made it part of the pipeline, so starting out sculpts there and passing them to ZBrush to take advantage of the detailing brushes we know before we retopo in 3DC isn’t a huge pain. We’re not jumping away from ZBrush just yet, but with the range of specialist tools available to us outside ZBrush we don’t see why we should be trying to make ZBrush that one program that we use. It’s really good at sculpting, but average at a lot of the other things Pixologic have tried to make it do. If it were still Pixologic or the update costs were more reasonable, or if it had taken them longer to make these licensing changes, I might feel differently about it - but as of now, if we’re not getting feature updates and the features they currently have are better done in Houdini, 3DCoat, Substance or Mari, which we have to have anyway, then ZBrush can just be the sculpting solution we originally got it for.