Newest update for AnimateCC has pretty much broken it for me.
Whenever using the brush tool at any size and any smoothing, after about 2-3 minutes a new window pops up saying 'Animate is processing strokes, Please wait'. System hangs after that and I need to restart the program.
Is there any way to roll back? This is a massive problem and I have deadlines this friday and I can't get any work done.
That dialog will come up even after a few seconds if you have managed to draw quite a lot of curves, stop drawing, and then tried to modify what you have drawn. The main addition that has helped with brush strokes is that the smoothing is handled by another thread. This means you could rapidly draw a lot of different curves, and the previous curves are smoothing while you're drawing the new ones. Previously if you drew quickly you would have to wait after every brush stroke.
So, the dialog is intentional but will hopefully only come up under specific cases. It shouldn't cause a crash though. The progress should fill in and you're all set, ready to modify what you just drew.
I'm not able to draw fast enough to invoke the dialog on my computer, so I'm having to remember how the dialog behaved the one time I saw it a few weeks ago.
If the app does hang, are you able to find any crash reports?
I been having problems with the brush tool as well. Its not as severe as pop up loading box but for me even the smallest sized strokes have a delay in where Animate takes about .5 seconds to process the smoothness and I'm not running Animate on no toaster either. I just wished the brush tool was as effective like it was on Adobe Flash. All these problems seem to derive from the smoothness percentage. (For me anyways.)
You are able to continue drawing during that half second, aren't you?
Yes, is just extremely annoying
I've been having the same problem. I literally just switched from Fash CC to Animate CC, and this issue is so frustrating. I draw fast, so when i draw my first line it registers the brush stroke but it wont pick up my second. I guess this is because of the program is still smoothing out the line from my first brush stroke, but regardless this is annoying. I need this issue to be addressed.
I just had this problem and managed to save my file. Writing it here for future reference: I tried to shut down the computer (or switch accounts) so it forces Flash to close. Cancel the shut down so you get back into windows and Flash asks you if you want to save your file. Click yes and it gets saved, though it stays blocked and you need to force its restart from task manager anyways
I'm having the same issue. Not sure what's triggering it. I just picked up a wacom mobile studio and I've been having that message come up .... but when it does, the progress bar never moves and the program just sticks. I end up having to end the task.
Same here. I was drawing in my normal pace (slightly fierce) and the dialog box poped up, with a no-progress bar that didn't allow me further interaction with the app. No draw, no save... Happily the RECUP document had all the information before the crash, but I'm afraid this doble-thread stroke vectorizer is even worse than prior system.
By the way, the high amount of nodes per line issue is not solved.
From what I understand, most brush issues have been fixed on devices running on Mac OS (Sierra).
I checked with the product team, and they told me that they have a few bugs related to Surface pro that they are working on.
Can you provide me with details about the OS on your device, and also if you have updated all drivers?
I'm running Windows 10 on a Wacom mobilestudio pro 16 ... i7 processor, 16GB RAM.
So what you're saying is unless the mac's OS is Sierra- theres no fix?
Let me check with the team and get back to you. They are fixing a few bugs on surface pro, and I am not sure if this is a related issue.
I am having the same issue on Windows 10 64bit pro on a 24" cintiq
Hopefully Preran is asleep for another couple of hours. But I'm sure he'll notice that you tagged him.
It's starting to get real annoying. I'm on a TV production right now and I keep having these crashes come up. It seems to happen when I hit undo ... it's happened twice today and if I wasn't a save-all-the-time freak, I'd be losing a lot of work.
the second day in a row! It is impossible to work !!!!
Same issue here, after drawing for a while I hit Ctrl+Z to redo a brush stroke and get the popup. No option to get a crash report as the program just hangs and I have to close it with task manager.
Really frustraiting when your into the swing of things and haven't saved for over a minuite. Re-doing something you've just done is not nice at all when your on a roll.
Windows 7, i5 CPU and 8GB RAM
I've experienced same issue on my Win 10 machine. I waited about 30 minutes and the dialogue never went away. Had to force quit. Thankfully Animate's auto-save prevented a complete loss of work. This issue has been reported to the team internally.
Apologize for the late response. This is the response I received from the team
Like Colin observed, the progress-bar is supposed to go away as soon as the processing is complete in the background, which should be very quick in most cases. If it doesn’t go even after leaving it idle for a while then there’s a problem that we need to investigate and fix.
I suggest reaching out to customer care using this link Contact Customer Care and ask them to investigate your issue. They should be able to log a bug on your behalf as well.
Thank you Preran,
Unfortunately for most of us the issue seems to be that the progress bar does not go away, not quickly and not at all. I’m literally running on a brand-new, high-speed dedicated workstation and when it happens to me, the progress bar stays on 0% until I end the task with task manager. The first couple times it did it, I let it sit , and after an hour it never resolved itself.
I will reach out to customer care. Thank you for your response.
I wonder if it's possible to be drawing so fast that the second curve you drew needs smoothing before the first curve you drew had started to smooth. That sort of thing could cause confusion.
If the dialog gets stuck again can you describe your physical movement at the time?