Just downloaded Photoshop 2024 today. When entering the Liquify filter, the mouse moves on its own, jumping all over the place. This makes the Liquify filter unusable. Anyone else seeing this?
Hi @Larry275412117uv5@default5846juwjnlhp Go to Photoshop Help Menu/System Info and copy/paste details in a reply. Post only once as the system takes time to process the large amount of data.
I turned off all hot corners under system preferences: desktop & dock: hot corners. The mouse still occasionally bounces once or twice, but for me this seems to have solved it.
/t5/photoshop-ecosystem-bugs/photoshop-2024-liquify-filter-mouse-moves-on-its-own-mac-14-1/idc-p/14125703#M92424Oct 01, 2023
Oct 01, 2023
Copy link to clipboard
Copied
Thanks guys for the information above to solve the mouse move on it own, but the problem stay remain the same and it get worst, so i may re install the 2024 version patch 24 back, as it seen is more stable then this patch 24.5 version, and i hope it works.
/t5/photoshop-ecosystem-bugs/photoshop-2024-liquify-filter-mouse-moves-on-its-own-mac-14-1/idc-p/14145034#M93109Oct 09, 2023
Oct 09, 2023
Copy link to clipboard
Copied
Also having this problem since I updated to 2024, did not yet find a solution. Anyone als did? It can't be Stage Manager on my PC, as this is not selected in the system preferences.
/t5/photoshop-ecosystem-bugs/photoshop-2024-liquify-filter-mouse-moves-on-its-own-mac-14-1/idc-p/14145929#M93141Oct 10, 2023
Oct 10, 2023
Copy link to clipboard
Copied
Please can Someone from adobe take a look at this, Its absolutley horific... Once it starts moving by itself You almost have to force quit photoshop to get out or it moves for several minutes. I started saving my work before I liquify, and just force quit when it starts moving... Removing the pen and using liquify with the mouse seems to help a little but really cramps my workflow.
/t5/photoshop-ecosystem-bugs/photoshop-2024-liquify-filter-mouse-moves-on-its-own-mac-14-1/idc-p/14165857#M93628Oct 17, 2023
Oct 17, 2023
Copy link to clipboard
Copied
Adobe continues to remain mostly silent on this. The only saving grace for me is that I had not yet deleted my Photoshop 2023. Any time I need to use Liquify, I have to quit 2024 and open my file in version 2023.
/t5/photoshop-ecosystem-bugs/photoshop-2024-liquify-filter-mouse-moves-on-its-own-mac-14-1/idc-p/14166261#M93643Oct 17, 2023
Oct 17, 2023
Copy link to clipboard
Copied
Hello Larry275412117uv5 Please open the settings of Photoshop > Technology previews and enable the option "Deactivate Native Canvas". Reopen the Photoshop app. It should work.
/t5/photoshop-ecosystem-bugs/photoshop-2024-liquify-filter-mouse-moves-on-its-own-mac-14-1/idc-p/14180422#M94016Oct 23, 2023
Oct 23, 2023
Copy link to clipboard
Copied
OK, so I spoke to Adobe directly and heres the nitty gritty of our discontent:
It is not the software but the driver for the graphics card that APPLE needs to work with the manufactureres to conjure up a new one that matches the OS and the new version of the Adobe software.
Adobe made it clear that our ponderously annoying situation has been shared with the graphics card manufacturers and now it is up to them to work together and create a working patch for an upcoming software update.
/t5/photoshop-ecosystem-bugs/photoshop-2024-liquify-filter-mouse-moves-on-its-own-mac-14-1/idc-p/14180969#M94023Oct 23, 2023
Oct 23, 2023
Copy link to clipboard
Copied
One more point:
Adobe requested and suggested that in Creative Cloud, you can download the last, best version of Photoshop and with both on your computer, use the new and the old, as you wish, until new graphics card drivers can be developed by the manufacturers and included in a future OS update.
/t5/photoshop-ecosystem-bugs/photoshop-2024-liquify-filter-mouse-moves-on-its-own-mac-14-1/idc-p/14206533#M95178Nov 03, 2023
Nov 03, 2023
Copy link to clipboard
Copied
It would be useful to know what Mac OS version you guys are using?
OK, I found another thread on the issue, and they are thinking it is to do with the Mac video card driver. The last post in that thread (as I type this) is from 26th October, and there was no fix at that time.