ZBrushCentral

[Bug?] Model composed of Z-spheres reverts to one Z-sphere on any action

ZBrush Usage Questions
#1

Hi all,

I couldn’t find any threads related to this phenomenon (It’s a bit of a flaky problem to search on so apologies if I missed anything…)

Problem:
I modelled a tree using z-spheres and saved the file. Opened it later, worked, saved again, no issues. Today I open the file and the moment I do anything the z-sphere tree disappears and becomes a single z-sphere. I reopened the file again without saving and hovered over the model snapshot, and it updated to show a single z-sphere, while the viewport still showed the tree. (see screenshot)

Does anyone know what caused this? and how this can be resolved? Although I don’t have high hopes for the latter…

Specs:
Z-Brush 4R7 64-bit
Win10 creator’s update
Processor Intel® Core™ i7-4930K CPU @ 3.40GHz, 3401 Mhz, 6 Core(s), 12 Logical Processor(s)
RAM 32.0 GB
GPU NVIDIA GeForce GTX 770

Thank you for your time!

Attachments

Zsphere error.jpg

#2

You should get updated to ZB4R7 P3
There’s ZTree which you should check out too.

#3

The patch notes for P3 don’t mention updates to the Z-sphere problem, so that still leaves me with the question of whether this issue can be re-encountered in some way (which I want to avoid).

I remodelled anew by now, but will check tonight whether this version of Z-brush isn’t on P3 already. Still, I can’t find whether this is a known issue or not.

#4

It’s not displayed as such :wink:

#5

I’ve updated to Patch 3, but the file itself did not change in any way and is still broken. This is not a big surprise considering the bug type.

The issue that is described in this thread remains valid and unanswered: It is possible for Z-brush to show users their modelled Z-sphere structures while in reality it has already completely destroyed the structure and returned it to a singular z-sphere state (model cannot be recovered). Considering that the patch notes did not mention changes to the Z-sphere functionality, I am not convinced this bug is on the radar or resolved.