chrisell99
Participant
chrisell99
Participant
Activity
‎Aug 07, 2024
07:27 AM
Well - this would appear to be something my corporate IT dept have messed up. I have one laptop fully loaded up with corporate bloatware, and on this one, the radial blur tool doesn't bring up the UX/dialog when I start the tool. That one is WinX64. My second company laptop is Win11x64 and on there it is also broken. My home machine, which obviously has no corporate bloatware on it, is also Win11x64 and on there it works fine. I'm not even sure how corporate IT software could break such a specific single thing, but there we go. So I guess we can close this or consider it 'solved' in the broader sense.
... View more
‎Aug 06, 2024
08:17 PM
Yeah I tried deleting all my prefs and it didnt make a difference. All the other filters work as I would expext but its just weirdly this one filter fails to bring up the UX for it. Have this behaviour on two different win10x64 machines. Haven't tried my Win11 machine yet.
... View more
‎Aug 06, 2024
01:22 PM
1 Upvote
Since getting the v25.11.0 update (in Windows 10x64), the radial blur filter no longer works. All the other blur filters work as they always have, but the radial blur doesn't bring up a dialog any more.
... View more
‎May 13, 2024
09:56 AM
1 Upvote
I'm on v25.6.0 - 25.7 hasn't shown up for me yet. Here's a screengrab of the prefs screen. I've also attached a TIF file that always causes a .c2paws file to be created.
... View more
‎May 13, 2024
08:02 AM
@CJButler It's not a hinderance to working. It's just a huge PITA that my texture / image folders are now getting littered with these files all over the place when this never used to happen. I'm a neat freak so having these "junk" files suddenly appearing just bothers me. A lot. 🙂 In other words - please fix it - but it's not a super- hyper-critical "this must be done right now" kinda thing 🙂 If @CShubert can hunt this down it would be appreciated.
... View more
‎May 12, 2024
09:21 AM
@CJButler @Caity.psd @CShubert Can I just necro this topic please? I'm still suffering this problem with even the latest builds. Every TIF or JPG file I open now automatically creates .c2paws files in the associated folder, despite all the Photoshop preferences being disabled for content credentials.
... View more
‎Mar 22, 2024
12:32 PM
2 Upvotes
I've been using it for about a day now without any issues (mouse only). I still have some other unrelated issues from other topics, but this one in particular appears to be cured for me now.
... View more
‎Mar 08, 2024
08:42 PM
3 Upvotes
@CJButler thanks for that. That appeals to the inner programmer in me.
... View more
‎Mar 07, 2024
08:12 AM
4 Upvotes
@CJButler seems a couple of beta users are seeing an improvement. For the technically-minded, can you summarise (at a high level) what the code change(s) is that might have cured this?
... View more
‎Mar 06, 2024
06:46 AM
1 Upvote
@CJButler That's good to hear there's progress being made. I'm not on beta but look forward to the next release.
... View more
‎Jan 28, 2024
07:31 AM
4 Upvotes
I would tend to agree with @Jqqerry on this one. I mentioned a couple of posts ago that I did a new install on a fresh out of the box Dell laptop and the problem manifested immediately.
... View more
‎Jan 27, 2024
10:14 AM
4 Upvotes
Super weird - this actually worked. @CJButler I followed the steps @DiodorS outlined but kept copies of my prefs files along the way. I've put a zip file on my shared OneDrive with two prefs files that I can use to repeatedly induce the sticky problem, and cure it. If you use my "prefs good" file, the sticky problem goes away. If you use my "prefs sticky" file, it comes back. I figured this might be of use to you to try to find a difference between these two files that might be the thing that is causing the problem. The OneDrive file is here: PSPrefsForCJButler.zip Hope this helps as it's the first time I've had a concrete works / doesn't work situation, in this case simply by swapping prefs files.
... View more
‎Jan 25, 2024
09:56 AM
Another data point - got a new laptop from my work this week (Dell precision 7780), installed the latest version, problem happened right away. Win10 x64. Problem happens when using either a plugged-in mouse or the built-in trackpad.
... View more
‎Jan 05, 2024
08:04 AM
10 Upvotes
@CJButler @Daniel Presedo I think I might have finally come up with a reproducable clue for you. As this stickiness also happens with the marquee selection tool, I spent some time this morning trying to rigorously figure out exactly what series of events caused the "sticky" to happen. Turns out it's the same for the pan/hand tool but that's harder to reproduce. With the marquee tool, if I do this: Click and hold left mouse. Drag. Stop moving the mouse. Unclick left mouse while the mouse is stationery. Then it never, ever sticks. I get the marquee selection and it works as I'd expect. However, 9 times out of 10, if I do this: Click and hold left mouse. Drag. Unclick while dragging. Then it sticks and the marquee tool follows the mouse until I click the left button again. For the pan/hand tool, it's a similar series of events. If I always let the left mouse button go while the mouse is stationary, then the pan/hand tool works perfectly. (Hold space, click and hold, drag mouse, unclick, let go of space) But again, 9 times out of 10, if I'm click-move-click-move panning, so the mouse is always in motion, it sticks.(hold space, click and hold, drag mouse and while it's moving, unclick to move back and re-click - ie. for panning across large or very zoom-in images) The common event for me is the movement of the mouse. If the mouse is not moving when I let go of the mouse button (unclick), all the tools work exactly as they should. But if the mouse is moving, it starts to get this weird sticky behaviour. I did for a while thing there was a speed element involved and true - at slower mouse speeds it's harder to reproduce - but again - the common thing is mouse movement. Almost like you've got some sort of buffer overflow going on where the mouse movement is overwhelming the buffer with so much data that the button-up event gets missed. Hope this helps? While a definite "not" condition isn't ideal ("it doesn't happen when..."), it might clue you in to where to look in the mouse handler.
... View more
‎Dec 26, 2023
07:10 PM
4 Upvotes
Google it. There are complaints about this all over Reddit, these adobe forums, and other creative and art forums, dpreview, Flickr, stack exchange. It’s really quite prevalent : https://www.google.com/search?q=photoshop+sticky+hand+tool&ie=UTF-8&oe=UTF-8&hl=en-gb
... View more
‎Nov 30, 2023
09:33 AM
@CJButler For the uninitiated, what changed between 24.7 and 25.0 that means you no longer see "WM_LBUTTONUP" ?
... View more
‎Nov 17, 2023
12:15 PM
According to one other topic (https://community.adobe.com/t5/photoshop-ecosystem-bugs/c2paws-file/idi-p/14096168) it's to do with content credentials.
... View more
‎Nov 17, 2023
11:22 AM
1 Upvote
@CJButler any chance we get some eyes on this one? I have c2paws files everywhere now and all the content credentials settings are turned off. See original post. Started in v25.0.0, does not happen in v24.x versions.
... View more
‎Nov 09, 2023
11:25 AM
7 Upvotes
Can confirm - pan, lasso, text (moving), clone, selection and many others - this does affect most tools. It's easiest to reproduce in the pan tool for sure but it does affect every tool with a left-mouse-click to some extent. I even had it stick with the paint tool today. I let go of the left mouse and it just kept painting. I needed to double click it to "unstick" it. Windows 10, v25.0, no wacom tablet (for those who still think this is a wacom issue)
... View more
‎Nov 02, 2023
08:02 PM
6 Upvotes
It’s nothing to do with Wacom or tablets. This happens with the mouse on machines that have never seen a tablet.
... View more
‎Nov 02, 2023
12:47 PM
6 Upvotes
Never had a tablet, so it's not that. Our 60+ office machines are a mix of win10 and win11 and we can reproduce it on all of those, none have a tablet.
... View more
‎Nov 02, 2023
12:23 PM
9 Upvotes
@CJButler I think what's grinding people's gears is that we can all reproduce this easily, every time, in every version since 24.5, on just about every platform. In fact I'd say most of use can't NOT reproduce it. It's difficult to understand why it's so evasive on your end when it's so pervasive on our end. A multitude of different machine specs, with different hardware, in different countries with different users and it's easy to reproduce. Space bar, drag, let go of mouse, let go of space and now you're stuck. For the marquee tool, marquee, click-and-drag, release the mouse, and it's stuck. For the text tool literally left-click and hold, drag the text later, let go of the left mouse and you're stuck. It affects SO many tools. There must have been a checkin between 24.4 and 24.5 that did this. Your subversion or Git checkin notices ought to have something in that timeframe that gives a clue, surely.
... View more
‎Nov 01, 2023
02:45 PM
1 Upvote
@Mark.Dahm Aha - yeah that fixed it. I'd actually been into the performance prefs before and tried disabling "multithreaded compositing" and it made no difference. I didn't go down into the GPU advanced settings. At least I have a workaround now but that's definitely some weirdo bug that could do with fixing. Thanks!
... View more
‎Nov 01, 2023
01:48 PM
1 Upvote
I figured a video is as good as anything - there's audio narration on here explaining it too. @Mark.Dahm
... View more
‎Nov 01, 2023
01:33 PM
1 Upvote
Also it's not limited to dragging layers around - ANYTHING I do on a lower layer causes this. For example if I marquee a section of a lower layer and fill it with a colour, it fills partially white until I either hide and unhide the layer, or do it with the multiply layer turned off.
... View more
‎Nov 01, 2023
01:32 PM
1 Upvote
<edited into above reply>
... View more
‎Nov 01, 2023
01:31 PM
1 Upvote
@davescm was able to replicate it in his later post. I've reverted to v24.5 for the time being as it's the only way I can get work done. It's basically every image I have - I do a lot of videogame work and all my textures are stored as 8bit RGB. They all work great in v24.5 but once I go higher than that, I get this compositing error which makes it all but impossible to use. In v24.5 the document status indicator does say D3D12 It's worth noting that between the start of this thread and now, I've swapped out graphics cards and it still happens. It also happens on the machines in my office across various cards (where we have tens of thousands of textures that are all 8bit RGB). The only way to get rid of it is to revert to v24.5 or earlier versions of Photoshop. Yes - new documents or existing documents. Anything that is an 8bit RGB doc and it does it.
... View more
‎Nov 01, 2023
09:42 AM
1 Upvote
@CShubert <-- tagging also to try to get some attention on this
... View more
‎Nov 01, 2023
09:40 AM
1 Upvote
@CJButler @Caity.psd Can we get some visibility on this issue please? It's making working with 8bit files basically impossible at this point. The problem started in v24.7 and persists in v25.1
... View more
‎Oct 15, 2023
09:33 AM
2 Upvotes
Can confirm we also have flick panning disabled.
... View more