Cursor disappears when use brush or cloenstamp things.
- February 26, 2023
- 14 replies
- 2809 views
Please watch my attached video first.
Issue:
- Photoshop version: 24.1~24.2(In video, PS version is 24.2)
- OS: Window10
Steps to reproduce:
- ... Painting with Brush, Healingbrush, CloneStamp, MixerBrush
Expected result: Nothing should happen, That should just see the cursor, including the brush, as it is, just like we were trying to do.
Actual result: The cursor edges of tools like brushes disappear, and you see the Windows 10 default arrow shape.
I've tried to record this bug every time, but the bug doesn't reproduce well when I start recording, and other communities like reddit have reported videos with similar behavior.
But today, while testing 24.2 (of course, there was nothing about this in the revision history, but just in case), I was recording. And I recorded a moment.
This bug is very frequent when it happens, and very infrequent when it doesn't.
In severe cases, it keeps happening every time I stroke the brush. I haven't tested this on Windows 11.
There are definitely bugs in Photoshop 24.1 and later, and for me, 24.0 was fine, but some users have reported that they had to roll back to 2022 for the bug to go away.
And it happens regardless of the image size and bit depth. And I don't use a mouse much, so I don't know, but for now I'm using a Wacom Intuos Medium Pro.
But it doesn't seem to have anything to do with Wacom. I tried installing different Wacom drivers, but the only thing that fixed the problem was rolling back the Photoshop version. I think something has been broken since 24.1, and I'm guessing it's this new brush cursor thickness customization option-beta that was added in 24.1 that is causing the problem.
This is not a catastrophic bug that will crash Photoshop or wipe out all your work.
But for retouchers like me, or artists who do a lot of drawing, it's a very annoying and inefficient bug.
I thought this would be fixed in 24.2 as a matter of course, but I'm disappointed that it isn't.
Hopefully, it will be fixed in the next version as a hotfix patch.
Thank you.
----
Btw,
I posted about this once before and it got merged into another thread, but I'm posting a new one because I don't know of anyone with better documentation of the issue and recording of the bug except for a few people.
