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

Same issue constantly comes up for me even in PS 25.2. The latest verseion that didn't have this issue was 24.1.1.

I tried to delete Keyboard Shortcuts file from PS settings and that solved the issue temporarily, but it came back shortly after.

Perhaps it's time for Adobe to work closely with the people who have the issue and put a real effort into resolving it. I bet there are many more users who suffer from it than just those who posted here. What's the use in having new features if all the new versions of PS are impossible to work in for a year.

Windows 10 Pro 64GB i7 RTX4070Ti + Wacom

@CJButler Thanks for the instrumented build! My system, as I mentioned, spontaneously stopped showing the issue, but an upgrade (I think) has always made it come back, so hopefully I can soon add to the diagnostics for you.

The strange sometimes-bad sometimes-good switching gave me thought that I don't think anyone has mentioned. I have never seen PS suddenly start working properly when it's been bad; and I've never see it suddenly start going wrong once it's been working correctly. An instance of PS (for me) will be always good, or always bad and never flips between the two.

So is it something that's being set up in process initialisation that is causing this? Some microsecond level timing difference changing a sequence? (Sorry for telling you stuff you undoubtedly have thought of - my old developer background here...) 

@Vit Kovalcik Yes, that log file is interesting. I do see earlier mouse-down-mouse-up sequences where the WM_LBUTTONUP is seen by the Tracker code and the gesture is properly terminated. Those earlier sequences are how it is supposed to work, and that's what we see in our testing.

@CJButtler: Thank you, I am glad it is useful. I have a Wacom tablet, but for this test I only used a Logitech mouse.

But just to clarify: The Wacom drivers are installed there and also there are two mice connected each with a different driver.

Hi Vit,

Thanks very much for that log file!

Sure enough, no WM_LBUTTONUP is seen by the Tracker code. We can see the key-up event as you take your hand off the space bar, and then a lot of TrackContinue calls.

I do see a WM_POINTERDOWN followed by WM_LBUTTONDOWN when you initiate the gesture. Are you by chance using a tablet/pen? Just for clarification.

> How does one contact a Community Manager?

Ordinarily I would have said Cory, Caity, or Pete, but I just found out they are being rotated off Community Management duties. I'm not sure who the new community managers are yet. In the meantime, you can send me a direct PM.

I'm mostly interesting in dissecting the last part of the Event Log, something that begins with:

  >>> Starting a Trace for a Mouse Down Event >>>

and ends with 

  ... End Trace for Mouse Down Event. 

@CJButtler: Cool, thank tyou for the descritption of the logging capabilities.

I did as instructed and here is the log:

https://www.pastel.cz/temp/PS_Logs.zip

I can create a new bug if neccessary, but it seems appropriate to post it here.

I tried just to pan around using the Space key + left mouse button. Started event log, use the tool a few times and once it happened (mouse released, but the tool is stuck) I waited a few seconds, canceled the tool by pressing Esc and then headed into menu and stopped logging (using mouse to navigate in the menu). There seemed to be several new logs, so just to be safe I packed all of them, but they seem kinda overlapping. It is probably safe just to examine the last one... I guess.

How does one contact a Community Manager?

>> My work computer does not have any fancy gaming equipment. The mouse I'd been using for the last year comes from the cheapest kit that money can buy (under $20 for the Logitech keyboard/mouse combo). It seems it was more likely to happen when the mouse was moved quickly.

I believe Logitech mice may have a custom device driver. This is what interprets the mouse-hardware and generates events which are handed off to the Windows OS, which in turn, packages it up and hands it off to Photoshop.

If anyone has access to a basic Microsoft USB Optical mouse (About us$10), that uses the Microsoft Driver, and can reproduce the problem, that would be good to know (and will probably exhaust this avenue of investigation)

BUT - if we CAN reproduce with something like a Razer mouse with variable sample rate, that would be extremely helpful, since at that point we would be able pursue debugging and possible workarounds with something where we could verify any changes we make to address the issue.

>> For the uninitiated, what changed between 24.7 and 25.0 that means you no longer see "WM_LBUTTONUP"

OS updates. Driver updates. 1000's of changes to the Photoshop code.

Also: we think this issue has been happening since 22.3, just less frequently and to fewer people.