I’m getting a consistent string of crashes when I try to use surface noise. I was able to use it once, but as soon as I clicked OK, it crashed. Now I can’t use the function at all without a crash. I thought the problem may have had something to do with the poly count, but when I tried applying surface noise to a simple sphere, zbrush crashed again.
Has this been reported before? What can I do about it?
so are you saying that preview works, but when you hit ok, accept, you crash? Or you have used it successfully all the way through once?
The very first time I tried, everything worked fine until I hit OK to close the preview and apply the noise. After that first time, I usually can’t even get a preview without a crash. If get lucky and the preview works, and then I start to adjust any of the settings it will crash. Especially with the Noiseplug button in that menu. Just clicking on it shuts me down.
You may need more ram or multithreading enabled. Good luck.
Hmm. I’ve got 8 gigs of RAM and a six-core processor.
Is multithreading not enabled by default? That just may be the issue.
well, that’s one nice setup you have.
Maybe run a mesh integrity check first, although I am not sure this will help, hopefully you will get a solution. Take care.
Thanks. After your last post I checked the preferences tab to make sure that multithreading was enabled in Zbrush, unfortunately it was (I was hoping that was the issue but…), I also ran the system capacity test, just to see if anything came up. That was fine too.
I tried other meshes too, just to make sure that it wasn’t that one particular model - no dice. Now I’m stumped.
Hi hol,
i have the same problem but mine only happens when i use noiseplug.
i’m using snowleopard on macpro 16 gig ram quad.
did u resolve this issue yet ?
Many thanks
Not yet. I’m mostly getting it with noiseplug too, though the problem seems to bleed into the surface noise function proper after I restart from a crash. l’ll be sure to post anything I find as soon as I figure out what’s going on.
Noise plug seems to be working again…sort of. I’m still not sure what is causing the problem. I’ll post an update as soon as I find out.