Skip to main content
Carlos de Leon
Known Participant
April 7, 2024
Question

REMOVE TOOL BUGGY USING WACOM PEN

  • April 7, 2024
  • 1 reply
  • 542 views

I’m getting strange behavior when using the Remove Tool with my Wacom Pen on an updated Windows 11 desktop. The first issue: When I circle an object to be removed, it does not fill in the area to remove the encircled section; only the outline is removed. The second issue: After making 3-5 pen strokes with the Remove Tool brush, the program freezes for about three minutes, followed by an error message that I’m out of RAM.


Here’s the strange part: None of these issues occur when I use a mouse. I can use the Remove Tool all day without any problem, as long as I set aside my Wacom Pen in doing so.


It’s an annoyance, and I’d love any thoughts on how I may remedy the bug.


Before posting, I reset my Photoshop Preferences and ensured that my graphics driver and Wacom Tablet were up to date – all to no avail. Additionally, I confirmed that I have plenty of Scratch Disk space and no RAM problems. Finally, I increased the Photoshop RAM allowance to 85 percent from the 70 percent default.


Thanks.

This topic has been closed for replies.

1 reply

Participant
May 3, 2024

I have the same exact issue. haven't found a fix yet (other than using the mouse)

Carlos de Leon
Known Participant
May 3, 2024

Carlos de Leon
Known Participant
May 4, 2024

Oh, yes this works too but then you can't have pen pressure which to me defeats the purpose of the Wacom 🙂


No doubt. But by making the brush thin and circling the objects I want to remove rather than filling them in, PS does a great job of cleanly excising the items I want removed. Granted, it is a pain to have to resize your brush with each use, and it's odd to have pressure sensitivity work on everything but this tool, but it beats having the screen freeze up after weeks and weeks of trying to troubleshoot the issue. I use the pen for everything, so using my mouse just to remove an object is too much of a hassle for me. Hopefully, an upcoming build will resolve this issue for good. 

Happy editing!