Cloning/healing: Defining source via ALT + CLICK inconsistent (after Win 8 -> Win 10 switch)

[Fabiantech]

Hello, after switching from Windows 8 to Windows 10 (on same hardware) I'm struggling with clone / heal:

Most annoying issue: Taking the source (ALT + click): It works erratically when using wacom tablet (intuos5)

• ALT + click only works in about 30 to 50% of clicks (extremely annoying and a no-go for fast prof. retouching with taking source points all the time)
• It happens both when I use the ALT-key of normal keyboard, a button on the Intuos5 set to ALT-modifier (maybe a bit less often though), and a button set to ALT on ShuttlePRO v2 input device (I loved to use while working under Win 8.1)
• ALT + click ALWAYS works when using the normal mouse to click instead of the wacom pen (it's not a hardware problem of the pen though)
• Strange: Sometimes the ALT + click results in a context menue (after some little lag). So somehow a right-click is triggered?? Why??
• Strange: Sometimes the ALT + click is accompanied by a little lag + a short standard windows sound. Why??

By the way, probably another issue, when doing the actual healing:

• Sometimes the cursor changes to a kind of round "work in progress/hourglass" cursor and slight lag. This never happened on Windows 8.1. Is there a way to prevent this cursor change? Why just sometimes?

I tried all sorts of seetings, both in Wacom tablet driver (of course newest version) as well as PS (e.g. "Use Graphics Processor" and "Advanced settings"). I tried to set smoothing to 0 of course. Without any consistent results. Every other software works flawlessly, but I can't get a working PS/Wacom system to do professional retouching... 😞

Does anybody have a tip? *desperate*

What is the main determining factor for ALT + click performance when taking clone/healing sources? (So I can focus my efforts to fix the issue on this).

I'm very experienced both with retouching and IT. Running a fast Win 10 x64 machine. It took me some time with Win 8.1 to get PS + Wacom + ShuttlePro + 3 monitor setup working (I vaguely remember all sorts of issues with windows ink etc.), but at least it DID work without any lag or performance issues after some time...

But now after switching to Win 10 the nightmare starts again... 😞

Retouching is just horrible - I even switched to using the mouse instead of wacom....  accepting poorer retouching results, but not constantly annoyed by inconsistent behaviour.

Maybe the problem has to do with a not very common NVidia Quattro K4200 graphics card (the bottleneck concerning performance, but offering 10bit). Never had any performance problems due to this on Win 8.1 though....

Maybe I should upgrade my Intuos5 and buy the newer Wacom Tablet? Though it works flawlessly with every other software...

Many thanks for any input. *knocking on wood and hoping*

Yours Flo

[Fabiantech]

Hello, I bought a new Wacom Tablet (Pro M):

Exactly same behaviour:

Wacom Tablet works perfectly in all other software.

Cloning and Healing performance in PS is just a nightmare: ALT + click to define source just works erratically in about 30% of the cases.

Any idea, why the ALT + click sometimes works and sometimes doesn't when healing and cloning using wacom pen??

(Already reinstalled Wacom drivers. Seems to be a compatibility issue of Photoshop (Wacom + Windows 10)?)

[Fabiantech · Accepted solution]

I finally solved the problem with the help of other (non English-speaking) forums, applying (awkward/temporary) work-arounds.

I'm EXTREMELY annoyed by Adobe:

The problem is known! Since the introduction of Windows 10 (and the way, (tablet) driver API was changed when introducing Windows Ink). The culprit is NOT MS or Windows though, but the way, Adobe didn't respond to this change in a professional way. (Probable, because the consequences of not investing in new/clean code only manifest themselves in certain situations with tablets and is only noticed by professionals, who need absolutely lag-less response.)

• I invested many many hours into this
• finally found out it's a known bug (or let's call it euphemistically: "performance issue")
• Adobe "help" had no idea whatsoever about it...

[OT: This behaviour of Adobe is simply appaling. Another example of trying hard to lose loyal long year customers.

Please: Stop investing in fancy tools, if you don't have the ressources. Concentrate on getting the programming CORE of the software right. Invest in good code and high performance, if you want to be taken serious by professionals in the long run.]

[omarjosef.com]

Why not explain how you solved the problem or at least link to the places you found the solutions?
For fast professionals, APassistant is not enough. There's still some lag and some erratic behavior in the alt-click when sampling with the healing brush.

[rollendp654221478]

That's a lot of words to give no answer. And your fix was????

[PECourtejoie]

pinging @Fabiantech for a possible answer. 
@rollendp654221478 are you experiencing the same issue? using a tablet? please share meaningful information.