ZBrush 3.5 Announced
polycounter lvl 12
So I was just browsing Zbrush Central and I see an announcement for Zbrush 3.5. Apparently ZB 4 is now delayed, but they are including a lot of the shown off features. Take a look.
http://www.zbrushcentral.com/zbc/showthread.php?t=073517
http://www.zbrushcentral.com/zbc/showthread.php?t=073517
Replies
Well, having some new stuff is better than having to wait a long time for a release. I prefer shorter incremental releases. Though, if all of the new stuff is what was going to be in 4, I wonder how much different 4 will really be from 3.2.
Basically just typical pixologic behavior.
AO baking will be awesome, provided the quality is ok, which at this point I'd hope nobody can get wrong given that there's so many examples of "good" AO baking out there, you'd have to be actively trying to make a bad implementation. Lack of AO bake was pretty much the only thing stopping me using ZMapper, as bakers go it's bloody fast and has a huge amount of options so your output can work with pretty much any engine or 3D app, which is quite impressive.
As mentioned too, it's free, I'm not going to complain unless they actually make the app worse somehow
Hopefully ZB4 has some even more useful stuff. And hopefully they've improved the file browse dialog systems, those things are so outmoded it's like a kick in the face every time I have to browse for an external file. Remember the bloody directory per file type, that's all I ask! Since when has anyone wanted to browse for ZTL files in the folder they just loaded an alpha or imported a TGA from? Those things are totally separate actions, they should not share default directory lookup... rant over.
Mop, you serious on the Zmapper? that thing always scared me....
Has there been anything about a tool in 3.5 or 4 that will project a texture onto a surface that follows the contours of that surface? The projection tool projects head on, even with wrap. So from the side of the projection is elongated.
Zmapper wouldnt be so bad if they would use more relevant terms. Nvidia normal mapping means nothing to me. I need to know what is _+ for each of the axis. Which AFAIK I cant directly access.
Well, maybe not mine...but probably someone else's.
Looking forward to GoZbrush though, hope it soon becomes available to be used with the other apps too.
In the meantime what I've done is actually saved over the default brushes with my settings (each brush is it's own separate file in the ZData Brushes folder).
Also you can get the "Reset Brush" script although that means you need to hit a hotkey every time you switch brush while keeping the settings, to set them back to your values.
well then could you not wrap the call for that script and the switch to a brush into a macro and assign your brush icon/hotkey to that? seems i have to check that reset brush script out.
Here's the old post:
"You may notice if you turn ZAdd on and off through the menu before switching your brush via hotkey you won't have this issue. I'm not sure why this is the case, but it appears to break whatever is causing Zbrush to think you want to transfer brush settings. So the idea here is to create a macro that turns ZAdd on and off and then selects the desired brush. You then assign a hotkey to this newly created macro and use it as your new brush.
For example, lets say you wanted to create a macro to fix the Clay brush:
1. Start a new macro.
2. Turn ZAdd off and then back on via the menu button.
3. Navigate to the brush menu and choose the Clay brush.
4. End the macro and save it in your Zbrush3/ZStartup/Macros/Brushes folder under the name ClayFIX.
5. Navigate under the macro menu and find the button for the ClayFIX macro you just created. Assign a hotkey to it that you would have normally used for the Clay brush.
6. You should now be able to switch to the Clay brush without encountering the bug. Repeat these same steps for every other brush you use. It didn't take me much longer than 10-20 minutes to replace all my brushes with the fixed versions."
Curious as to what this unannounced feature is.
EDIT: Oh, nevermind. Yes =]
PaintStop, a new plugin for ZB3.1 . Well I'm a little bit divided here, seems a good add but won't change a thing in my workflow, probably cool for ilustrators and so on, but isn't Photoshop better for that? Perhaps some good use on the sculp paintovers for quick concepting and developing ideas?
http://www.zbrushcentral.com/zbc/showthread.php?t=073956
i've always had seams on it(
As a side note, I really like how they always try to mimic sa much as possible the process of a real traditionnal sculpture.
/me CAN'T WAIT.
Can't Wait +1
+1
I was hopeing for something like for some time now, painting real geometry which adds to the topology. The Topology that comes out of it seems pretty high from what i could see from the short wireframe shot in the vid but it also seems very even which was always a big problem of zpheres.
conte: I've used ZMapper before, it is very powerful and has a lot of options, so you really have to know what methods your target renderer is using to calculate tangent space etc. otherwise you might bake completely inappropriate normals just by having one wrong setting in ZMapper.
Try loading one of the different presets that matches your requirements (eg. Maya or 3DSMax) - ZMapper comes with a lot of presets so you should choose the right one, or learn the settings needed for your target renderer.
Don't worry Autodesk will implement it in mudbox 2011
I always find polymodeling faster and more practical than zspheres though.
I wouldn't really expect to see Pixo release this bad boy until the 31st at midnight.
Log on to your Zbrush Support Account and you should see the following message
Sweet
For terrain sculpting, I'd still take Mudbox. Zbrush's shitty camera controls, specially zoomed in close and trying to rotate the camera in a predictable way make it a pain in the arse for this kind of thing.
Like the look of zspheres II. If they'd show a movie of someone making a five-fingered hand with them......
HOLY SHIT!
-
New 3.5 VID CLICK!!
http://www.zbrushcentral.com/zbc/showthread.php?p=599965#post599965