P: Completely broken Hand tool (PS24.5) Hand Tool Sticking, sticky, not seeing mouse-up

Here are my findings:

This issue DOESN'T HAPPEN if I check "Use Windows Ink" in Wacom Tablet Properties in Control Panels and also I need to NOT have PSUserConfig.txt with line "UseSystemStylus 0" in it. (Though there is some completely separate flickering bug I am still ivestigating... not sure if it is related to this setting) The PSUserConfig.txt is probably all right already and doesn't even exist for most users, since it would have to be previously manually created and edited by them - I think Photoshop itself will not create this file.

In all three other combinations of those two settings the issue happens, i.e. all four combinations are YES/NO Windows Ink and YES/NO UseSystemStylus.

It is not related to keyboard. To reproduce it is enough to switch to Zoom or Hand tool, then don't touch the keyboard at all and just use the tool using the tablet (furiously clicking and dragging randomly 🙂 ). In about 15 % of time the tablet release is ignored and the tool is still active and zooming or panning even if I am hovering way above the surface.

My specs: Win10 x64 and Intuos 4 PTK-640, which is older version equivalent to current Intuos Pro line. The latest tablet drivers are therefore from 2020. Other specs if that matters: Intel i7-12700, 64 GB RAM, Nvidia 3080 with latest Nvidia Studio Drivers.

@CJButler  There are also a lot of people reporting on macOS in this thread that I've created now. They're experiencing.... Ofcourse I'm WindowOS user.

And to many people who reported on my thread together, thank you.
I know you guys are not angry.
But we think it's enough to make the expression more soft or just convey the information we need.
The thread I've created has been my own reproduction of this bug, getting sympathy and votes from many people and incorporating many other threads into this thread.
How to recreate this and the causes I think have already been left in this thread several times, and I've emailed Adobe employees a lot of things.

Like the beginning of this thread, until the end of the thread (the moment when the bug is Fixed), we only want to talk about this issue.

@ericman2323 thank you so much!

That is exactly, what I am trying to say.

A unified way to gather all of the needed information, condensing it to the similarities and finally fixing the bug.

I am not a native english speaker, so I have to try my best to make myself clear, with some help from an online translator, but not too much. 😉 

Hm... so what's your complain?

Consider me disrespectful?

As I mentioned:

I appreciate your commitment!

And I don't see any hate speech coming from me.

But you have to allow me to vent my anger, which isn't only mine, but of many many users, who read this thread every day, to check, if there are any useful news about it.

Consider me not being supportive?

How more supportive can I (or many others) be, than straining my/our brain(s), to find/suggest helpful things for you guys, to get the bug fixed?

Please explain further what part of the guidelines you exactly want me to read.

I will do.

@Goyko 

I recommend you read the community guidelines.

>>> CJButler what about Goyko survey idea?

>> In my judgement, not a good use of my investigative energies. I don't think there is much if anything in those system reports that will help get to the root of this particular problem. We've already seen the problem on very vanilla systems, and I have not seen anything remarkable in the system reports that I have looked at.

You completely got me wrong!
I suggested a SURVEY, specialized for that bug.
Ask people all possible details about their system, especially about their software environment about things, the photoshop system info doesn't give you.
AND get their photoshop system info!
Collect everything that can help isolate the similarities/commonalities.
Software is binary... works or doesn't work.
If Adobe can create such a great software, they for sure should be able to debug their own stuff!

>>> I guess what's even more aggravating than devteam not being able to fix it quickly (or at all) is the fact that in the meantime there are new features implemented that for many of us are to be seldomly used, but hand tool, bread and butter of our daily work is broken.

>> I and others are working the problem.

Obviously not hard enough! 😕😕
Stop wining about not being able to find and fix the bug, while at the same not even taking suggestions from the community into consideration.
A thing btw, WE are not supposed to have to, because WE are the PAYING customers, not your team members.
I consider this behaviour quite ignorant and meanwhile it drives me mad!

This is a major bug, existing since many many versions of photoshop.
So stop finding excuses for not being able to find and fix it, while at the same time wiping everything off the table, that we try to provide for a solution!

>> A few bits of information that might help frame things:

Photoshop has a large engineering organization. More than 100 engineers contributing to various facets of the product. (...)
Allocation of resources across the Photoshop product is done by the engineering management team. That's not me.

As much as I appreciate your commitment:
What are YOU doing here then? 

Communicating with us users, smoothing things over, keeping us calm and putting us off?
Get someone up here, who CAN provide help with communicating to the community providing REAL help, to isolate and fix the problem!

>> I don't know if it's a bug that only happens to some windowOS users, but people who use macOS also go through this...

I don't know either. The vast majority of fail cases seem to be Windows 10, so that's where we are focusing our energies. We've never seen it at Adobe on Windows 11 or Mac OS.

>> CJButler what about Goyko survey idea?

In my judgement, not a good use of my investigative energies. I don't think there is much if anything in those system reports that will help get to the root of this particular problem. We've already seen the problem on very vanilla systems, and I have not seen anything remarkable in the system reports that I have looked at.

>> I guess what's even more aggravating than devteam not being able to fix it quickly (or at all) is the fact that in the meantime there are new features implemented that for many of us are to be seldomly used, but hand tool, bread and butter of our daily work is broken.

I and others are working the problem.

A few bits of information that might help frame things:

• Photoshop has a large engineering organization. More than 100 engineers contributing to various facets of the product.
• The engineering skill set is not fungible; that is a given engineer is not equally skilled at solving problems in all parts of the code base.
• The people who can help with this particular problem are aware of it and are supporting the investigations.
• Other engineers continue to deliver features which are supported by their specific skill sets. And to be very clear, the feature work I was previously assigned to work on is not getting attention from me right now; so that implied trade-off you are asking for has happened.
• Allocation of resources across the Photoshop product is done by the engineering management team. That's not me.

>> And to sum it up maybe we are frustrated also because it's not the only bug that plagues your software. random clipboard problems between your apps...

Separate issue. I hope it's logged. Do you know if it is being tracked? I don't.

>> Illustrator's inability to refresh layer thumbnails properly.

And... completely separate product. And team. I can't help there. Same with InDesign.

The Adobe Community Managers can be your advocate with the Product Management Team (those are the folks that prioritize work by engineering). Product Managers are also on these forums. They do post (just not in this thread so far). Please make your case with them.

I can honestly understand that this is fixed update late. I don't know the programming, but I don't think it will be easy. A few years ago, bugs that had been reported for a long time also needed a lot of time to be fixed.

But I understand the delay in updates, but I don't understand that new releases keep being updated without this being fixed.
I'm not sure about the other bugs. But this bug is as unpleasant as people who actually use Photoshop want to press ALT+F4 right away. Over and over again.......

I don't think there's anything I can do in Photoshop to avoid this bug. Just press t and enter text?

For instance, this was also a serious bug that I reported a year ago or two years ago. It destroyed the image in real time without saving it, and some users even destroyed their own family photos. beyond repair.

So Adobe confirms it and the release is forever removed from the official release. You can't download it again.
Like that I think there's no point in a new release as long as this bug exists. I don't know if it's a bug that only happens to some windowOS users, but people who use macOS also go through this...