Skip to main content
Adobe Photoshop Family

704 Messages

 • 

9.4K Points

Tue, Jul 23, 2019 3:16 AM

Solved

Photoshop: Clone stamp source crosshair missing/not showing/disappeared photoshop 20.0.5

The Clone Source Cursor cannot be seen on white in photoshop 20.0.5.
(also applicable to the Healing Brush Tool)

To test just make a new document with a white background, draw something with the brush tool
or draw out a shape.

Now try to clone the brush stroke or shape using the clone stamp tool and notice the clone stamp source cursor cannot be seen on the white background.

https://forums.adobe.com/thread/2634651

Responses

Official Solution

Adobe Administrator

 • 

15.4K Messages

 • 

291.4K Points

9 months ago

Yes. This should be fixed by today's 21.1 update. Thanks.

Sr. Product Manager, Adobe Digital Imaging

Adobe Administrator

 • 

3.5K Messages

 • 

53K Points

a year ago

What OS are you seeing this on?  When I try it with that version, I can see the Source cursor without a problem.  Have you tried turning off GPU support to make sure it's not your card?

Thanks,
David

704 Messages

 • 

9.4K Points

a year ago

Both windows and mac.

704 Messages

 • 

9.4K Points

a year ago

Both mac and windows machines exhibit the problem.
It looks like the cursor is there it's just not changing from white to black when going over lighter colors like white.

Yes turning off gpu support works, but i don't recall this being a problem before the photoshop 20.0.5 update.

Champion

 • 

3.2K Messages

 • 

56.7K Points

I see this too on my Mac Mini with a Blackmagic eGPU.

Johan W. Elzenga,

http://www.johanfoto.com

Adobe Administrator

 • 

3.5K Messages

 • 

53K Points

Okay, JEA, if turning off GPU support makes this problem go away, it might be that we're having issues supporting your graphics card.  What kind are you running?

Ditto for you, Johan, if you're seeing this now.  I'm definitely NOT seeing it on either platform (just checked again).

23 Messages

 • 

520 Points

I've had this same issue over 3 different computers, a MacBook Air, a Lenovo Laptop, and a home built PC running Windows 10. I edit a lot of headshots on white backgrounds so it's impossible to see where the clone source is. Turning on/off GPU does absolutely nothing.  Trashing preferences does absolutely nothing. I would tend to think this is a bug in the software as it happens on different PCs, with different operating systems. As far as I can recall it started happening in the CC 2018 version... and has carried over to CC 2019 without any fix. 

UPDATE: I didn't realize that I had to restart Photoshop in order to actually see the effect change. When it wasn't working, I just assumed that like most photo software these days, it was not in need of a restart. I can now also confirm that no matter which GPU state I choose (Basic, Normal, or Advanced - Open CL - on or off etc. only by turning off the "Use Graphics Processor" will bring back the black cross hairs on the clone stamp tool. 

I do hope this bug is fixed in some upcoming update. Having an Intel i9-9900k processor and not being able to utilize it in Photoshop for this one reason is quite annoying. 

39 Messages

 • 

926 Points

a year ago

Can confirm, running Windows 10 and NVidia GTX2027. If I disable the GPU, the clone and stamp cursor correctly shifts through various inverse greys as I clone through different areas. With the GPU enabled, the source crosshair remains solid white regardless of what I drag through. The brush cursor and crosshair are fine, the source crosshair is not.

Adobe Administrator

 • 

15.4K Messages

 • 

291.4K Points

a year ago

Thanks. Engineering is investigating this.

Sr. Product Manager, Adobe Digital Imaging

39 Messages

 • 

926 Points

a year ago

Thanks Jeff! (Incidentally, EVGA GeForce RTX 2070/PCIe/SSe2 is my graphics card--I seem to have just mashed a bunch of incorrect number keys when I tried to type it before)

23 Messages

 • 

520 Points

a year ago

Thank you Jeff, most appreciated! 

704 Messages

 • 

9.4K Points

9 months ago

Seems to be fixed in the 21.1.0 update.

Thanks