It’s behaviour seems odd - whenever I adjust the size of my brush while texturing it constantly snaps back to an old setting (e.g. I’ll have green on my brush, select blue from the model, shrink the brush and it’ll snap back to green).
Anyone else encountered this and know if there’s a fix/work around? It’s not critical - but annoying.
You might have a sticky key on your keyboard.
Also, please follow this forum’s guidelines when posting any troubleshooting inquiry. With each troubleshooting post, please include your full system specs and any other pertinent information which will allow us to determine if this is one of the following: a) user error? b) Misunderstanding of a specific feature, such as its usage and limitations? c) An item which has already been resolved. d) An item which needs to be resolved.
IMPORTANT: Before posting a troubleshooting item, make sure that:
You are using the latest ZBrush version.
You have a ‘clean’ ZBrush install. i.e. remove any items which you have added (such as older ZScripts and other startup items) which may result in unexpected - and difficult to resolve - problems.
You did not increase the PreferencesMax polygon count or Compact Mem to a level which can not be supported by your system specs.
Any threads that do not follow these guidelines will be closed. Thank you for your cooperation.
Sorry aurick - didn’t include them because the same happens at home on my macbook pro in windows mode as happens on my pc at work - I’d assumed it was simply one of those odd bugs 
And no - no sticky key.
Ok, I’ve duplicated this now. You can avoid it by dragging from the color swatch onto the canvas to create the picker. The error is only cropping up when using the C shortcut.
You can also avoid it by changing your brush size before you sample the color, or by making any brush stroke after sampling. The error only appears when you pick a color and then immediately change the brush size.
Thanks.
Ah great… not just me then! I’ll try the dragging technique for now - but would be ace if it got sorted at somepoint - although obviously it’s only a minor thing. Thanks again 
Actually this error also appears when you C color pick and do other things. For example I wanted to fill the entire object with a color I picked. So I pressed the c key, the color got sampled, then I went and clicked on the Color menu(to choose fill object), and as soon as i clicked on the color menu the color swatch changed back. It happens if you click on any menu actually.
This happens to me all the time. I always use C to grab a color, then I go up to the brush size, immediatly the color changes, often to something I never even used before.
I have to remember that after I eye drop to click somewhere on the object, then when I adjust anything in the interface, the color stays.
Just one of many annoying things in Zbrush I hope will be fixed. The most annoying this is changing something, then I do a brush stroke, but I messed up, so I undo, but it then undoes something at the same time.
Color Pick with ‘C’ shortcut, then Fill Layer bug
Happens with Fill Layer (CNTL-F) as well.
Steps:
The drag-picker works fine, but the ‘C’ picker doesn’t.
The color it ‘goes back to’ appears to be a slight offset from the color active prior to the C-pick.
Marcus, does this affect the ZSwatch zscript? Or does it function fine?
Thanks,
I can’t answer for Marcus but I had to abandon the color swatch mouse-click in the ZMats-31 release because this bug also affects the ZScript IKeyPress command which I use to simulate pressing the “c” key to sample the color in the material icon. (In fact I found that there were other IKeyPress failures as well.)
I really hope all this makes it onto the update list of “bugs that-MUST-be-fixed.”
Sven
That’s what I was afraid of…
But if you have a color value in your script memory, as in ZSwatch, and you want to set this as the current color when the user pushes a button, is that affected?
Me too!
Fooling around with the “c” hotkey again I discover that, AFTER capturing a color, if you immediately left-click at some random spot on blank canvas, the selected color then seems to take.
I might try simulating something like that in a script - could be the work-around that might let me select colors again in script!
As to Jay’s question, I guess it will depend on how Marcus has implemented the swatch plugin. Marcus?
Sven
Marcus, Sven,
Is there an example zscript for coding with the Z3 interface? It used to be that you could inspect the programming of someone’s zscript, but now everything is .zsc. In particular, I’d like to know how to do some of the things in the ZSketcher program.
Thanks,
Jaycephus,
ZSwatch simulates a drag from the color swatch to pick colors so that works ok in 3.1. (There’s a different problem with hotkeys & zscripts though, so even that doesn’t always work. I’m planning a plugin update that avoids the problem.)
There are a few sample scripts at the top of the ZScript Help forum & on the Wiki. There are no particular differences in zscripting for 3.1, except that some commands no longer work correctly (e.g. some Note options such as pointing out an interface item).
Thanks, Marcus,
Since the changes are less than I thought they might be, I’ll go back to sample code I already have. It’s just that I was afraid that the real killer is the new bugs that may force you to work around something that used to work a certain way. That, and there seems to be some techniques used in the better scripts that have no available examples. I could be wrong, but I don’t know of an example that uses the UI like ZSketchPad does.
Regarding the PM,
Would Pixologic be willing to give out the txt version of ZSketchPad?
Good Luck, can’t wait to see what you come up with!!!
Best Regards,
Jay,
I don’t think there’s any secret over the UI aspect of ZSketchPad. It is simply a custom UI which is provided with the plugin and loaded using [FileNameSetNext]. It’s an idea which you rightly point out is under-used.
HTH,