Brush Flow bug in CO 11.1
Does anyone else experience a strange and very annoying bug with the latest CO version? When I select brush tool it goes to 100% although I have set it to 1% or 2%. After pressing cmd-Z and brushing again the flow returns to 1% (or at least to a lot slower flow). If I change brush settings, say the size or hardness, the problem returns and I have to do cmd-Z trick again.
Never experienced this before. I have contacted CO support and sent Logs and screen video- no cure so far.
Never experienced this before. I have contacted CO support and sent Logs and screen video- no cure so far.
0
-
Yep brush is doing strange things, first stroke is ok, subsequent as you describe. 0 -
Yes. I am experiencing very annoying and sluggish behaviour with the brush since 11.1. It is pretty much unusable as a tool at the moment. Turning off OpenCL doesn't help. Hopefully C1 will provide a fix soon. 0 -
Quick test looks like this is fixed in 11.1.1 which has just been released. 0 -
Spoke to soon, further testing during the day shows bugs still present.
I've logged a support case with P10 -
In reply to both Jason131 and Tim Trim:
Yes, and Yes. I have experienced all described brush issues in the 11.1 update. I reverted to 11.0.1 as I am in the middle of several studio projects and the brush was unusable. Based on Tim's post I too updated to 11.1.1 thinking the problem was solved, and as Tim stated, the bug is still very much alive in that update. I have reverted to 11.0.1 yet again. Starting with
11.0 there has been a distinct pause/delay in the first use of the brush on any layer and the brush is just as wonky as described. I am able to use 11.0.1 with the least issues. Turning hardware acceleration on/off does not seem to make a difference though initially turning screen off auto seemed to help at first. Again, no joy.
MacPro (Mid 2010) 3.2 GHz Quad-Core Intel Xeon, 32GB, AMD Radeon HD 7950 3072 MB, 1T SSD, NEC P242w, OS 10.12.60 -
Working with P1 support on this, I've managed to re-produce on video for them.
Seems to occur after adjusting brush settings, it will ignore the flow and brush to max nominated opacity.
Sometimes on a stroke this will be a circle at the start and end of the stroke.
Sometimes the whole stroke is impacted.0 -
I'm seeing this same issue on both my 2015 MacBook Pro and 2013 iMac (Core i7). Sounds like the same experience that everyone else here is having. Although it's the Hardness, not Opacity that I've noticed being reset. Due to this (and another issue involving the Quick Loupe), I've rolled back to 11.0.1 for the time being. 0 -
Hi Just adding my voice to this - brush is laggier than usual and sometimes reverts to quite a hard edge rather than the feather which I have set. Have tried this on wacom tablet and mouse - same issue. (intermittent though at about 70% of the times I try) Program is unusable and not sure if I have an earlier version on my machine. Will revert though as I need to get jobs out. Please sort out Phase if possible. Many thanks
Ros0 -
P1 have managed to reproduce this and it has been logged as a bug to be fixed in a future release. 0 -
Experiencing lag and disappearing brush on version 11.1.1 You will see the size of the brush one minute then it disappears (but still works) then reappears again a little later. Not sure if I'm the only one experiencing this. If I am, I think I'll try a fresh install later once I've finished in the studio today....
Also, memory usage creeps up very fast. One session open and the memory goes from 40% usage (16gb total) to 80-90% after a while. I use an app to reclaim memory from C1 Pro.0 -
[quote="DAndison" wrote:
Experiencing lag and disappearing brush on version 11.1.1 You will see the size of the brush one minute then it disappears (but still works) then reappears again a little later. Not sure if I'm the only one experiencing this. If I am, I think I'll try a fresh install later once I've finished in the studio today....
You are not the only one seeing it! It happens to me too.
Ian0 -
The descriptions stated in the prior 4 posts more adequately describe this issue than I did earlier. Can only hope Tims's advice that C1 is on this is accurate. 11.1 and 11.1.1 are unusable. Tim please advise if you happen to catch wind of a time frame. We can only hope. I am back and stuck at 11.0.1 until this is fixed. ☹️
asu_chic0
Post ist für Kommentare geschlossen.
Kommentare
12 Kommentare