Every time I try to use topological masking in transpose in 3.5 R2 with a partially hidden mesh, I get a crash. Anyone else getting this? Any workarounds?
A quick test with the demo soldier tool, partially hidden and not, topological masking, and various transposes produces no crash for me.
Does it happen with every tool? Can you isolate a specific situation that is causing the crash?
oh no. please tell me this is fixed, it would happen to me all the time in 3.1
I can’t reproduce either. Windows Vista64. Any steps to reproduce?
-K
No problems here. Tested on SuperAverageMan and the DemoSoldier, with and without UVs.
Vista 64 bit, intel.
i get this as well…try it on your own model not the demo things… i have it on any base mesh i have imported from either modo or maya
I did try it on my own imported mesh without any immediate problems. Something more specific is causing your issue.
(Also vista 64, sp1)
yesss it happens here too, the problem is quite random, always with the mesh partially hidden, sometimes will crash, some other times it won’t, using even the same mesh…i was hoping it was fixed in 3.5, too bad… 
I would like to add that I have had this happen many times, and yes it seems almost random. Tool would usually have multiple subtools, and subdivions, layers. I would usually have hidden it maybe twice or by polygroups then hiding more. Eventually it started to become predictible, especially if I had been working on the piece for a long time. If say more than 80% of the model was hidden it would crash like this. OH OH and it would really happen if I did the transpose too quickly between other commands. I alway make my models in zbrush using either edge looping (which causes some weirdness itself) zspheres or retopology.
xp64
8gb ram
Thanks for the responses thus far.
I too can load a default tool and hide/sculpt parts. I agree with some of the other posters, I’ve been getting seemingly random crashes and freezes with ZB 3.5 R2, in particular when portions of the mesh are hidden. At work, I’ve reverted back to 3.1 completely. Same Ztools that were crashing in 3.5 R2 are fine in 3.1 (again, both home and work).
I decided to try messing with the unified skin tonight, and after about 30 min. Got this nice freeze / crash to happen: It should be noted, this mesh comes from Zspheres, and not from an external app. You can see the polycounts etc. in the lower right if you go fullscreen. The polycount at time of crash was in the mid 500K. Also, I’ve had this problem with both my custom UI and the default UI. In short, I don’t think I’m doing anything to cause this behavior, I think ZB is broken (hopefully, I’m wrong).
Here are my specs at home (where I made this particular video):
OS: Vista Ultimate X64: SP1
Video card: NVIDIA GeForce 8800 GT
Procs: Intel Quad CPU Q6600 @ 2.4GHz
Ram: 4 Gigs.
Here are my work specs:
OS: Vista Ultimate X64: SP1
Video card: NVIDIA GeForce 8600
Procs: Intel Quad CPU Q6600 @ 2.4GHz
Ram: 4 Gigs.
Any help would be greatly appreciated.
Yes it happens here too.
Say I want to mask away the arms to do some transpose on the legs only I first mask the body, hiding the arms. Then everytime (this is not random for me. It happens every time) I ctrl-drag to mask the legs from the rest of the body I get a crash.
Dell Precision T7400
Intel Xeon E5440 2.83GHz, 2.83GHz
8GB Ram
Quadro FX 3700, latest NVidia Drivers.
Windows XP64
ZBrush 3.5r2.
Anyone found any solution for this yet?
I’ve started to see this mostly on objects made outside of Zbrush where the topology contains significant merging/diverging of flow (or other complex flows where the surface has lots of poles) and is open at one end. I suggest people open support tickets and attach sample .objs. The problem seems to be driven by the topology, so if a particular object causes the crash, it will always cause the crash.
-K