Cursor disappears when using a brush (Arrow)
- May 24, 2023
- 12 replies
- 2469 views
I've reported this many times, and many people report it, but it gets moved from the Bugs tab to the Discussion tab, or merged into the wrong, completely unrelated bug thread, and never gets fixed.
This is an independent bug that is completely unrelated to layermasks/panels.
Please do not merge it into another thread.
Occurs in Photoshop 24.0 and later. (Some users also experience this bug in 24.0 and use 2022 instead of 2023 to resolve it)
The cursor should be visible while using the brush.
However, the cursor disappears and turns into the default mouse arrow.
And it stays that way until you stop rubbing the brush on the tablet or mouse.
Take a look at the video I attached.
One is what I recorded the other day, and the other is what another user recorded on reddit. The video on reddit is longer and better expresses the pain we're experiencing.
(What we=user know so far)
1. This bug occurs when "painting" a brush.
2. Most people who have experienced this bug use a Wacom.
3. This happens not only with brushes, but also with healing brushes and clone stamps.
4. This is said to occur not only in Windows OS but also in Mac OS.
5. This has nothing to do with the currently open panel, layer mask, or anything else.
6. I tried all the options currently available to the user in Photoshop, including disabling the native canvas, and none of them had anything to do with it.
7. Not sure about 24.0. It works for me, but the
It's pre-2022 Photoshops that are really risking everything and not experiencing this bug 100% of the time. I have never experienced this bug before this year.
(Why this bug needs to be fixed)
I think Photoshop's identity is all about moving the cursor and utilizing it.
And for the last decade or so, this has been exactly what we've been doing.
But right now, as in the video, we don't know the exact range and have to either break the brush unnecessarily, or estimate it sensually.
As a professional who uses brushes a lot, I was unable to use any builds after 24.0 until this bug was fixed.
A lot of features have been improved, bugs have been fixed, but the presence of some other bugs has not hindered my work.
But this essentially stops all my workflows before they even start.
