ZBrushCentral

The great list of Z3 quirks...

ZBrush Usage Questions
#61

Reactor, unconfirmed, randomly reported “quirks” should not be listed at all until they are confirmed. If the list is composed of heresay, its of no use…and plus it would save space…the front page is really hard to read through.

You’ve got “Mesh with layers not saving subtools…needs confirmation” listed, when its clearly not true as stated, as far as I can see…in that I’m saving tools with both subtools and layers quite often. Other issues are listed that also are of questionable merit, or unverifiable by any scientific measure.

If you’re going to list every casual observation from some inexperienced user, or every bit of heresay from someone who “thinks that Z3 gives you a mild rash”, theres really no point to all this. Most of these issues could be verified (or not) with a simple check in the program, and if youve got time to keep posting them to the front page, you’ve got the time ( and a common sense obligation) not to spread misinformation in the user community.

Its not my intention to be harsh…it’s good to see members try to contribute, in a way that is, presumably, well intentioned. But you did take this upon yourself, and some accountability is in order.

#62

I’m getting a problem where by if I try and crop and fill an alpha it just fills the canvas white or some other shade. Closing Zbrush down and re-doing the operation seems to fix it. Could be a graphics card thing. I have a ATI 9800 pro with the latest drivers.

Pete B

#63

Reactor, unconfirmed, randomly reported “quirks” should not be listed at all until they are confirmed. If the list is composed of heresay, its of no use…and plus it would save space…the front page is really hard to read through.

I think they should be listed, because then people can test for them, or keep their eye out for them. However, I agree they clutter things. I’ll move them to a new section.

Other issues are listed that also are of questionable merit, or unverifiable by any scientific measure.

There’s obviously a problem somewhere in relation to those quirks. If they aren’t dealt with after a fair while they’ll be scrubbed, but they’re there for the time being in case someone wants to comment or confirm a similar issue they’ve had.

…not to spread misinformation in the user community.

If it’s going to happen, it’ll happen regardless. But, I don’t think it will. Generally if people don’t run into a problem, they won’t take any notice of it being mentioned until they see it for themselves.

But you did take this upon yourself, and some accountability is in order.

I appreciate the feedback, and I’ll make the changes. But, you have to take the good with the bad when it comes to this sort of thing, and although I can tell you’re frustrated about bad bug reporting, the guys who mentioned those things deserve to have them listed. Often it’s those kinds of reports, as obscure and initially unhelpful as they might appear, which are some of the most benifit to users (and developers!) who are looking to confirm something they’ve seen.

#64

I am totally agree with you including the purpose to be constructive and not to be harsh.
I spent most of my time learning through the Question and Troubleshoting segment, whatever post a problem, a bug, “quircks” i tested everyone(if possible) and most of then are not bug but misunderstanding or missing tips that already have been posted in the wiki or in the forum.
Reactor consider that is helpful to put here i respect a lot your opinion but i will respect a lot more if you take the time to test each one before give credit to it, in that way your for sure purpose to be constructive to the Pixologic Team will be more reality, and i guess will be more appreciated and i can learn from your post too:D :+1:
Andreseloy

#65

I’d love to have the time to test all the submissions, andreseloy, but I’m afraid I don’t. I’m happy to collect information, but it’s a team effort here on ZBC, as you know!

#66

Here was my only point Reactor, and bear in mind, I’m not attacking you, and I dont think anyone should. I’m don’t have an agenda of squashing your thread…I contributed an issue…a verifiable, repeatable issue. I have others, but I wont submit them here…I’m not sure I have any faith that there would be a point…they would just be lost in all the chaff.

Your goal with this post was, ostensibly, to provide a list that would be of use to Pixologic in addressing these “quirks”. That may or may not be likely to happen…but its distinctly less likely to happen if the list is a swirling, illegible mass of new user error, spurious observation, and heresay. They already have that…it’s called The Question and Troubleshooting forum.

The “list” is only of any value if its a concise, readable list of testable items, that have been subjected to some reasonable degree of verification. Quality over Quantity.

Many of the items submitted would be quicker to test in Z3, than the time it takes to copy them to the front page and organize them. This is your post…its not a wiki…no one else has access to that list. I understand if you dont think you have the time to account for the information, but then the post should be closed or abandoned, as any post spreading misinformation to the community eventually would.

My recommendation, if you dont have the time to be personally accountable for your own post, would be to move all this information offsite to a Wiki format, where it can be subject to group scrutiny and editorial oversight. It may then develop into something of real value to Pixologic and the community at large. At the very least, remove any item not explicitly verified to its own easily identifiable “unverified” subsection, possibly with a different text color. Remove items that aren’t testable just for the sake of limiting the scope of the list.

I appreciate all your effort to this point.

#67

I just want to say that I have no idea whether Pixologic is taking anything on this list into consideration (though I suspect maybe), but the fact this list exists make me feel better. It hasn’t helped that there’s been nary a peep out of Pixologic since the release of ZB3…so many are left wondering if and when any updates/quirk fixes will be made.

I imagine the beta testers are getting a bit more info (no idea really)… but as much as I love ZB3, I think we’re all, in fact, beta testers here. Just my opinion.

I do think rather than just list unsubstantiated quirks, it would be better to confirm them, but without more organization, that may be a little difficult. It certainly shouldn’t be one volunteer’s job to confirm every quirk submitted. It should be a team effort (or the job of some person who’s paid for it).

I, for one, am happy to try and confirm some quirks, but many don’t apply to me as I still have a relatively shallow understanding of the software. I’m learning as I go. But perhaps we can come up with some sort of organized way of quirk checking?

I guess the only other problem I can see beyond that is once we’ve confirmed a quirk, we have no control at all over fixing it… though I suppose work-arounds are a possibility. As is just knowing what to avoid.

Remember, we may disagree on how something is done, but I think we’re all on the same team and we’re all seeking a positive end result and solution.

Just my 2 cents.

#68

I’m on Windows XP Pro with ZB3.

I loaded a ZB2 tool (actually a low res copy of the horse.ztl d/l). Then
I imported a texture (also created with ZB2). Looked OK, but wrong mat’.
So…

Selected the ‘Glow’ material (OK, that was a mistake).

Hit ‘Best Render’, render crashed part way through.

I can reproduce, but not 100% of the time.

Since my machine has a JIT debugger installed (day job is S/W eng’)…
I have stacks as follows:

Crash #1

NTDLL! 7c92ae22()
ZBRUSH3! 01ba2ed5()
ZBRUSH3! 004037a3()

Crash #2

ZBRUSH3! 018613f0()
ZBRUSH3! 0044b639()
ZBRUSH3! 0206f612()

Crash #3 was trhe same as crash #1

#69

  1. If I enter ‘Projection Master’ with ‘Perspective mode’ ON and ‘Focal Legth’ to 65+, If i do just one Deco Brush Stroke with ‘Zadd’ on and no alpha and texture activated and then when I “pick up” the mesh from Projection Master, Zbrush 3 will crash. Try it on the ‘DemoHead’ that comes with the Application.

  2. Some Buttons will not Save to coustom UI, Like the SubDiv level Slider. there are many others that after I have placed neatly on my iterface; have disappeared

  3. I have a model im working on, and i disabled UV’s; as is Recommended to work with high levels of Subdivs. Well, The Uv’s Have been deleted, and if i import a version from an external application, like maya, in attempt to get my UV’s back, ZB3 will crash.

  4. While ZB3 is loading when executed, if i click anywhere , it will crash.

Hope this and many other problems get fixed.
I am working on Windows XP, BTW.

Best Regards - Jay Lenn

#70

They already have that…it’s called The Question and Troubleshooting forum.

That’s true, but this forum is about submitting questions to receive tech support- not reporting bugs or quirks. (see the forum guidelines) The only reason this thread is here, is because I couldn’t find a better forum to place it in. I contacted Ryan at Pix and asked if a thread or wiki entry would be a good idea, and he said, “Go for it.” At the time the wiki wasn’t operational, so that’s why I posted here. Perhaps now would be a good time to move it to the wiki. I’m up for that.

The “list” is only of any value if its a concise, readable list of testable items, that have been subjected to some reasonable degree of verification.

All of the items on the list are testable. By all means, test them so I can mark them as one thing or another. If something isn’t testable, or can’t be confirmed, I’ll either place it in a seperate section or remove it.

I understand if you dont think you have the time to account for the information, but then the post should be closed or abandoned, as any post spreading misinformation to the community eventually would.

As I said, I disagree this will happen. This post will fall deeper into the archive as people stop posting to it, anyway.

Zerodean, I agree with your sentiments. What do you think on shifting this post to the wiki?

On a side note: I doubt Pix will fix the issues on this list. Zbrush 2 had tons of nasty little bugs, and not one of them got fixed before Zbrush 3. I think that’s pretty darn crappy. I also think Pixologic’s way of dealing with the community is pretty crappy too, considering the kind of community they have… but, I have high hopes that sooner or later they’ll realise they should do more to create a workable bit of software than adding zscripts and features to it, and will deal with the little issues. That’s why I started the list. It’s not meant to be perfect, but considering I’m not getting paid for my time, it works fairly well as the community’s way of saying, “Hey, Pixologic! Please fix these!” which so many people wanted to say.

In summary then: yes, let’s move this sucker to the wiki. Feel free to PM (or email) me, or post here, and we’ll work together to organise the list in a way that suits… well, those of are who are the more picky :wink:

#71

No thanks. I now see the real agenda behind this thread, and doubt our aims would be compatible. I was of the opinion that a scientifically verified list might be of actual use to Pixologic and the community. You seem more interested in regurgitating any negative thing that anyone has to say, legitimate or no, because in your mind Pixologic pissed in your cheerios at some point.

Bye bye now. Buh-bye.

#72

You seem more interested in regurgitating any negative thing that anyone has to say, legitimate or no, because in your mind Pixologic pissed in your cheerios at some point.

What a load of rubbish. Did you read anything I said in my previous posts? That’s the first time I’ve said anything on the topic. I have no gripe against Pixologic. I’d do things differently personally, and my general thought was- if I can help the community by trying to list the issues while Pix do what they’re doing now, great. That’s it.

…scientifically verified list might be of actual use to Pixologic and the community.

Have you ever bug tested a program? Have you ever developed a program? For the record, you don’t need a ‘scientifically verified’ list to be a help to both developer or community member. The list could be better, granted. But, it’s the way it is, and thanks to your rediculious outburst, I think it’s best to leave it as is. I’ll update it as the rest of the community post to this thread. If this thread isn’t helpful to you, why don’t you go and post your own thing to the wiki and show everyone how it’s done? You obviously have no adjenda on this thread other than to shove your own ideas down my throat, and then try and make me look like an idiot when I offer to hear your thoughts, instead of immediately doing what you suggest.

#73

The wonderful thing about public forums is that anyone can post their opinions about something… whether right, wrong, mistaken, unjustified, mispercieved, negative, positive, or whatever. It often takes a very open mind to read and react accordingly.

As has been proven time and time again, probably the easiest way to react to something online is in a negative fashion. And it’s also been proven time and time again that written words, particularly without knowing the personality typing them, can very easily be misread and misinterpretted.

One person may accuse someone of having a hidden agenda… someone else may think that’s a load of crap. One person may think this quirks list is a good idea. Another person may think it’s a waste of time. We all have different opinions. Who cares.

Let’s just keep moving forward in as positive a fashion as possible.

Quirks or not, we love ZB. That’s why we’re all here.

#74

Well said, and moving forward is a good idea.

#75

im thinking about a new etch-a-schetch, i think all the bugs are worked out by now.

#76

hi guys
i just got this quirk

#77

hi guys
i just got this quirk
in the attached screen shot there is a head i made from sphere in zbbrush and
started re topology on it
wen i reached around the lower lip/chin area… it just stopped showing me the new points that i make… they exist coz wen i press A mesh appears which is pretty fine but i cant adjust any othose points and after adding 2 .3 points blindely now i cant move further to add more points… so i m stuck here
have restarted zbrush . restarted my pc everything but no solution.
anyone please help and tell me is this a quirk?? has anyone else faced this problem???
plpease confirm or give me some idea??

Attachments

retopologized.jpg

retopologized with A.jpg

#78

Trying pressing Masking:Clear Mask

#79

thanx marcus for reply but its not tha masking issue. i just confirmed it again.
i have quickely checked few other issues as well. i made another sphere did sculpting and added topology it was perfact. and wen i loaded this tool again
it was the same. new points are there, adaptive skin appears but i cant see the new points… the curser detects points underneath(gets red) but points and edges dont appear…

#80

I’m not sure that it’s the same as you have but I can create ‘ghost’ points if I load a saved retopo tool. These can appear in the manner you describe even if I simply try moving existing points (which fail to move). The solution is to turn off ‘Edit Topology’ then turn it on again. The points then behave as expected and the ghosts have disappeared.