ZBrushCentral

Make 3D from Alpha Not working since 2021.7.1

ZBrush Usage Questions
#1

Hey everyone!
For a while now, we’ve been using alphas to create our jewelry. This all worked perfectly until the 2021.7.1 update, and still doesn’t work as of 2022.0.1.
The issue seems to be that when you import a grayscale alpha, and choose the “Make3D” option, it ignores all the grays. It seems to only focus on the white and black. I’ve uploaded a couple images to show the difference. One is the 2D grayscale image that we import in to ZBrush, and the other is a side-by-side comparison of what the 3d generation does in 2021.6.1 (the model on top) vs 2022.0.1 (the model on the bottom).

Anyone have any idea as to why this doesn’t work anymore? It’s pretty much essential in our work flow, and the fact that it doesn’t work anymore really messes with our process. At the moment we are working around it by creating the 3D model in 2021.6.1, saving it, and then importing the .stl file in to 2022, but it would be nice if we didn’t have to do it this way.

Hopefully there’s just a random setting that got changed with the update.

Thanks in advance!
Richard

Here’s a link to the images:

2 new items by Richard Gretz Goldsmiths

PS: is anyone else having issues uploading photos? I tried, but it keeps giving me an error, or is stuck at 100%, and the post button is grayed out.

1 Like
#3

Hi @RichardGretz

This looks like a job for Pixologic Support. I don’t think anybody on the forum will be able to help you with this.

1 Like
#4

Hi @RichardGretz ,

Welcome to ZBC! :slight_smile:

Many thanks, I can reproduce this problem and have reported it to the developers. (Though @zber2 is absolutely right, it is best to report bugs through Pixologic Support!)

#5

Thanks for the response!
I’m glad you were able to reproduce the problem. That helps me not think it’s just something weird I’m doing wrong :smiley:

I went ahead and messaged Pixologic Support, and I’ll try to remember to post back here if/when some sort of resolution happens.

1 Like
#6

I’m having the exact same problem and I’m doing the same workaround as you, going to a previous version, saving the model and bringing it to the newer version. I hope it gets fixed soon. 2022.0.2 still has this issue.