If you’re asking what I responded to, cy asked for it. And a second time since.
If you’re asking where I saw cloth implimented in 2.5, that answer is “Siggraph” – I watched the booth demo several times, and Pix did it in each. Not sure if that made it into the online video or not. BUT… you can see how that’d work just by scanning through this thread (and see a bit of cloth yourself towards the end of it).
Again, you’re creating a costume based on the underlying character mesh. Like a cleaner version of Meats’ wire technique (in that you still have your low-subD levels to play with). This is not cloth in the sense that Max and Maya have cloth – when the 3D world speaks of “cloth,” they mean “cloth simulation,” with gravity and collision detection and all of that. If you tell people “ZBrush does cloth”, you’re implying a falsehood which can only lead to disappointment and a sense of betrayal.
I figured. That’s not a plugin; it’s the base functionality of ZBrush 2.5.
That’s a minor distinction, I guess, but since we were just told one plugin is running behind schedule to add new functionality, I want to make sure no one confuses those ideas.
Also, understand that it’s a modeling tool – we’ve seen no evidence that it can be exported or animated, and have no reason to think that’s been added.
Ah! This explains why everyone’s so anxious to get that – they probably all thought the same thing.
My understanding was that ZMapper was strictly a previewing tool, so you can see your model more closely to how it would appear in a game engine, and so you can admire your high-res detail from every angle without the performance hit of actually manipulating that many polygons. The realtime unwrap thing you were looking at was not creating UVs, but simply arranging all your polygons to match their positions in the existing map so you can identify problem areas.
That’s not to say UV mapping isn’t an area Pixologic might be concentrating on for the new release, especially now that Max and Modo have such nice tools for it. But I don’t think anything’s been promised or implied on that one (except that there are still surprises pending).
C’mon. You were here too.
The update has lost nothing. The schedule has lost it’s importance. And the thread lost it’s stickiness to send that message, because every time one of the dates mentioned approached, it brought only loss and dissapointment, and a sense of betrayal, made worse because some users tried to stir things up further to make their demands heard. The thread was too volatile, too powerful, and we used it irresponsibly.
Outside of restoring that power, I don’t see what making the thread sticky again will accomplish.
Honestly, I don’t think they do either. This was a projected roadmap; it charts new lands where no one’s been before, but we hold to it like gospel. That’s crazy. And if you’ll see any theme to my postings, it’s discouraging craziness.
Choose a different beacon. This one’s gone bad.
AGAIN… That’s not to say Pixologic can’t meet their release schedule, or that features you want will not be included. The point is, we don’t know. That we can’t know. If it were safe to tell us, we’d be told.
So it isn’t.
Don’t push.