In Photoshop CC the pen tool lags about half second from when it is initially clicked. This makes it very hard to work fast using paths. It literally takes half a second for an anchor point to appear after clicking.
3 weeks and no reply? Again, us Win7 users use the pen tool just as often as others. Not to be facetious, but this is beyond frustrating at this point. I just can't believe this issue still hasn't been addressed.
So looking at everyone's system info I find that we all share one thing in common. Our processor. We all have 8 logical processors. Could it be a multi-threading issue?
Can`t use pen tool on windows7(x86) on ps 13.0.1.2. and 13.0.1.3 because of hard lags and delay on mouse left click. These lags are also presents on cloud version of ps cs6 (13.1.2) and on all versions of ps cc include 14.1.2. On ps 13.0.1.1 and earlier there is no any pen lags.
Will be there any fix? Do you know about this ploblem?
So it appears our solution to solve this problem, which remember also includes not being able to set path operations with the hotkeys - and =, is install Windows 8? Really?? Could someone from Adobe please at least express concern at this point, and that the issue is being addressed?
Andy, what I mean is that we have high end processors that use 8 cores. The relation I see between all of us is somehow PS doesn't seem to work so well with 8 core processors?
Windows 8 does not solve the problem. I work on win7/win8 now on win 8.1,
I'm using at the moment and AMD (Phenom II) as well as Intel (Xeon) processors NVIDIA graphics Card and AMD GPUs, and still come across this problem. It is far better on my HP Z620, but still not perfect - especially after 2-3 hours with PS/Illustrator when only solution is close all projects and reload adobe programs because i can't see what i'm doing because of this lag.
My only response, and it's a very obvious one, would be- Why not find a colleague, friend, customer, whoever it may be, who is experiencing the pen tool lag and address the issue with his/her computer?
Ok, fair enough. Thanks again for responding. I suppose I'll be forced to reinstall CS6 until the issue is resolved. This glitch is just too frustrating.