think you missed my above post #56, yes alpha and tried the intensity, sorry but its not as good as lazymouse, i really hope trails isn’t going to replace lazymouse in the future.
Spaceboy
The lazymouse is not going any where. This LazyMouse issue is not happening to everyone though. Have you played with any of the fall off settings in Tails?
There is no other work around right now, sorry.
Paul
glad to hear its not going anywhere. i have played with all the settings but they are a little unclear as to their effect. Also with trails you’re back to the old broken stroke issue where its dotted.
I’m going to just wait for z4 or hopefully another fix.
also specs:
q6600 2.4ghz
8gb ram
xp64
this bug has absolutely destroyed my work flow . is there any word if the programmers on z 4 even realize there is an issue i really dont want to never have lazybrush again.
The best workaround I can find is to save often. Thankfully most of the time I can tell when LazyMouse is about to crash ZBrush. It’s when you make a stroke and it gets interrupted halfway through. Then it’s time to save, because the next stroke will make it crash.
I used to lose about 30 minutes of work a day before I got used to how broken 3.5 is, and now it’s just 5 minutes at the most that gets lost every day. Is there some way we can bill Pixologic for this? 
(I know, I know, I could have figured out a workaround, but it’s always been part of my main technique and workflow, it’s gives great results, and I’m quite stubborn.)
Almost as bad is that I’ve really championed ZBrush at work and we’ve had to fight tooth and nail to have our leads buy ZBrush licenses instead of Mudbox ones just because we’re convinced it’s the best. Our leads looked at the GUIs and figured people could get into Mudbox much faster, and easier, but we promised we’d bring people up to speed, just because ZBrush is superior.
It’s a bit embarrassing to be honest. “I thought you said ZBrush was superior, why does it keep crashing when using a basic function like this? 3.5 has been out how long now and has had how many revisions and they haven’t fixed this yet? At least Mudbox’s LazyMouse function doesn’t crash…” Etc, etc.
I totally agree! Lazy mouse crashing is the biggest flaw of ZBrush in my opinion. As I’ve said countless times on these forums, I can make any computer crash with lazy mouse (I’ve tried it on nine different systems here at work, and I’ve crashed all nine…Even people’s machines who say theirs doesn’t crash with lazy mouse!!!) Please, Pixologic, understand, it’s not a machine issue. Those people who haven’t had it crash are just using it differently somehow, and are frankly lucky. All I know is, I save about once every ten strokes when working on something like hair. And it annoys the Bajeebies out of me.
I was hit with this last night 
Had spent around 90 mins - 2 hrs making straps and buckles between LW and Zbrush, then sculpting in wrinkles and stitches and alpha’ing on a material texture. Only to lose it, when I starting using a brush with Lazy mouse without saving. I haven’t noticed this problme and have been using lazy mouse a lot on this project.
What really bothers me is that they took the time to implement the crash detection of the problem instead of fixing this bug ( so auto recovery can kick in, but this does only work like 50% of the time ).
Guess we’ve to wait for v4 … maybe someday.
v4? what’s that? :rolleyes:
is this a plug in lucky?
V4 = ZB4
I guess what we all were expecting from the beginning was something like:
support: We are aware of this horrible bug and are working very hard to fix this awfull issue as soon as possible, thank you for your understanding.
We have been trying to duplicate this without success.
For those of you who are encountering this problem, please do the following:
Submit a Support Ticket. In that ticket include:
- Your tablet (or Cintiq) model number.
- Your tablet (including Cintiq) driver version number.
As we get in enough of these tickets we will hopefully be able to find the threads in common. Please do NOT post that information in this thread. We need it sent as a support ticket at http://support.pixologic.com.
Thanks!
Well that’s interesting.
I wonder if anyone who’s had this problem has used a mouse(non tablet).
also i find it strange that with the same tablet in 3.1 this never occurs but does now in 3.5, doesn’t that point more to a zbrush issue instead of wacom?
I give up…
I’m done/finished.
I don’t know how many times I can say it. This is not a hardware issue. I have two completely different systems, work and home. I just got a new system for work, making three, and it happens on all of them. I have made it happen on several other systems here at work, all different brands, different graphics cards, different types of tablets, (mine are cintiques). It happened several times yesterday while doing hair: many quick strokes with an alpha (dam Standard). Sometimes you can work for 45 minutes without a crash, sometimes it will crash in seconds. If it doesn’t crash fast enough, try making a few dozen quick strokes, then add an alpha for a few dozen more, back and forth. This is my foolproof method. I’ve been able to crash every machine in minutes this way.
BTW, I’m in LA, if you can’t repeat it, come over to Gentle Giant Studios, and we’ll show you in person. Otherwise, I give up.
Okay, you guys got me questioning my sanity, so I decided to see if I can make it crash at will, again. This time it took about 15 minutes of continuous slashing, switching back and forth between brushes, turning alphas on and off. I was just about to give up when, Whamo! Crash. You guys just aren’t being patient enough. And for those who say, “if you have to work that hard to make it crash, it’s nopt that big a problem,” I say this: after a few crashes, the very THREAT of another crash at any second makes you work very differently. You never know exactly when it will happen, so you save every minute.
Again, for those of you who are encountering this problem, please do the following:
Submit a Support Ticket. In that ticket include:
- Your tablet (or Cintiq) model number.
- Your tablet (including Cintiq) driver version number.
As we get in enough of these tickets we will hopefully be able to find the threads in common. Please do NOT post that information in this thread. We need it sent as a support ticket at http://support.pixologic.com.
This is what our development team asked for. [COLOR=White]PLEASE HELP US HELP YOU!
Thanks!
I’ve been looking for awhile and can’t seem to locate the driver version number. Can you explain where exactly to find it. In the device manager, under human interface devices there are three wacom drivers, but none of them are the one that I downloaded two months ago when I got my new computer. I was on the phone with a Wacom rep, and she sent me the most recent driver in April.
Thanks
Launch the Wacom Tablet Properties program. Click the About button. 
I’ll get the IT guys here at work to raise a ticket with the information you requested. Thanks, aurick