ZBrushCentral

Brush strokes more "segmented" now in 3.5? (See page 5 for more information)

This is what is shown at the title bar, it is not your key, no need to worry.

I asked you to activate the auto recovery since you stated that you are using Vista. For Windows 7, you should not activate it. Please Disable the auto recovery and save your config.

Please try…

Launch ZBrush and immediately hold the SHIFT key, keep SHIFT key down until you see the PolySphere3D ready to be edited, this will disable Startup plugins. If done correctly, you’ll see in the title bar “User-customized plugins disabled”.
Now test the LazyMouse and let me know if you are experiencing the same problem.

Yep. User plugins disabled. Yep. Crash. Again I resorted to adding an alpha after a few minutes. Got bored.

For whatever its worth, here’s a link to a video of the process from immediately after starting zbrush to the crash. I think its about 30 seconds and is in real time. Thanks for your help. http://screencast.com/t/NWY2MzJhMjEt

Does it crash with the brush download support provided? That was my good ol’ lazy mouse trick in the vid. Seems the alpha is what immediately caused you problems, although you said it happens without.

Also, what are your preference>mem settings? Are you running background apps, etc? I’m no IT guy, just freewheeling.

Wow, I’m sad. I really can’t use these new so called brush behaviors. I hope the guys give us a patch for this “dotted effect”. Please, or could someone write a plugin to give is some sort of spacing control.

I’ve tried all of the tweaks I can find and the brushes are still unusable.
Tutorial please?

Well out of desperation I tried the lazymouse settings and I found that

LazyStep: .12
LazySmooth: 0
LazyRadius: 1

seems to give the best duplication of the old 3.1 standard brush.

Slight Lag but nothing that one couldn’t get used to.

I’ve had my share of freezes with R1 & R2, but it seems that they are gone with R3…- knocking on wood.

Can’t reproduce a freeze with the settings like in omulu01’s vid.

My current system is XP 32 - dual core with 4 GB ram ( + 3GB switch)

I updated my wacom drivers to the latest available (RC) recently…maybe
this solves the lazymouse/freeze issue…(probably a long shot)

good luck

We are trying to figure out what is causing the LazyMouse problem on a small number of system (we are not yet able to reproduce this problem).
If you do encounter this problem, please follow the instructions given to omulu01.

Nonetheless, jaystein777, you should be very happy, not sad. Here is why…

ZBrush 3.5R3 brushes are…

1. More accurate. The ratio of signal to noise is much (much) better than 3.1
2. More capable. Capable of handling smaller as well as larger meshes. You can also zoom in as much as you need, or out.
3. More advanced. More advance calculation - for placement of the brush and its interaction with the surface of the mesh.
4. Better At Masking. Masking is 16 bits accuracy (not 8 as in 3.1)
5. Better At painting. Painting is 16 bits (not 8 bits as in 3.1).
6. More Customizable. Have many more modifiers which allow you to design brushes not previously possible. Look at the depth controls, depth masking, directional masking, Polygroups Masking, profile for tablet response. Stabilization code. Tilt controls, Trails controls,Smart Smoothing and more.
7. Smarter. Just test the mPolish or hPolish brush and you’ll understand how brushes dynamically adjust their behaviour.

The above is just a partial list of the enhancements to the brush system. All these advancements means that 3.5 brushes are superior to 3.1, but they also require more calculations. ZBrush is highly optimized and able to execute these calculation extremely fast but it can not be as fast as no-calculations at all. However, even this should not stop you from achieving smooth strokes. Smooth strokes can be achieved with LazyMouse or with the new Trails feature (or even both).

THAT is why you should be happy.

I truly enjoy creating with ZBrush 3.5R3, give it a chance, and you will too:)

P.S. I am including another variation of the standard brush. Give it a try.

Attachments

Standard31B.zip (8.43 KB)

I like new brush options BUT I also liked 3.1 brush strokes without dots.Why can’t we goth both of them,would it be impossible to add a “old style” button in brush options:)?

Did you try the brush I have included in my post?

I have. It works good-I know that trick with lazy mouse:)But unfortunately lazy mouse trick don’t works too good on high poly meshes for me(over 4 mln).Thanks anyway :)I think I just have to get used to new brushes work style:)

Sorry for My English.

I am feeling better about the brush situation, I am not actually experiencing the LazyMouse crash as of yet, and the LazyMouse settings that spaceboy and I posted actually do reproduce the clean lines that 3.1 has. I guess I just have some uneasiness about adding LazyMouse to my standard sculpting workflow mainly because of the slight drag that seems to accompany the LM settings.
As I said earlier I will probably find it quite useful.

I am amazed however at the incredible additions to the the brushes as described above and I am quite eager to learn to control and use them, so I guess all it will take is to wait for the tutorials and documentation.

Thank you again for the reassuring and informative reply.
I will also try the new brush that you uploaded.

I really don’t like using Lazy mouse to avoid dot problems, because after 4 millions of polygons it is so slow.
I preferred the old way a lot more, now I simply can’t use clay tubes in the same way as before, because at higher resolutions it is laggy, while it was a brush designed to sculpt on denses meshes :frowning:

Please add a button to activate or not all the new brush features, so one can choose between 3.1 or 3.5 brush style

What is strange to me is that my computer has high performance, and that my stroke is dotted also at lower subdivision levels.

I hope Pixo will consider seriously to increase the performance of the brushes to have the great “brush feeling and experience” Zbrush had in 3.1, because currently I hate this behaviour.

Maybe CUDA could help ?

wouldn’t this all be solved if they would simply unlock the stroke settings in the stroke palette?

I tried the LazyMouse solution and my ZBrush (3.5 R2) froze up as well after about 5 minutes. Very frustrating! I trust that this will be addressed soon by Pixologic.

I want to expand on the point brought up by Lucky_1 about the bump at the beginning of the Standard Brush stroke. Much of the subtlety of the 3.1 brush is now gone. I’ve tried all sorts of adjustments including raising the depth but I can’t seem to achieve the same stroke as in the earlier version. To illustrate, I’ve included a screenshot below. The little dots at the beginning of each stroke, on their own, aren’t so bad but when your whole sculpt is covered with them it’s very annoying.

Don’t get me wrong. I totally appreciate all the effort at Pixo to deliver a better product. I also understand that the new brushes are more precise and “smart” and have a lot more settings to be experimented with. However, shouldn’t the Standard Brush (being the most important) be usable right out of the box without any adjustments? :cry:

Attachments

Stroke_comparison.jpg

R2 is no longer supported. You need to be using R3. Emails with the update instructions were sent out last week. If you didn’t get your instructions, please submit a ticket in the Upgrade category at http://support.pixologic.com

I’m using R3 at home but my work place still hasn’t upgraded to the newest version.

Nonetheless, I’m still having the same freezing problems and stroke problems with R3 as with R2.

Yeah, I missed the brush stroke flow in 3.1. It is like they fix one problem and then another one pops up. The programmers seem to be slacking.

For whatever its worth, I deactivated my zbrush R3 from my new computer and installed it on my old one. Specs are: Windows xp, 4 gigs of ram, intel core 2 duo cpu. Zbrush 3.5R3 right out of the box. No customization at all. Crash in 15 seconds. This is a completely different machine with a different graphics card, different operating system, different everything. I did exactly what you see in the above video. The only difference was, it didn’t crash the first time, so I turned alpha back off, then made a few strokes, then back on. I did this back and forth about three times, then poof. However, since this machine isn’t Windows 7, I was able to recover the .ztl and ui state. Thanks for your help.