Copy link to clipboard
Copied
Windows 10. Updated Nvidia graphics card. Beta 24.6.0
Start with LR classic and PS beta closed.
Open LR classic.
Edit a PSD from LR to PS. Select edit original (previously edited photo with layers for further editing)
Using a brush or lasso tool lines are created that shoot off to the left corner of the screen. This is using a mouse and intermittently when using a wacom pen. The problem with the mouse seems constant. If PS is opened before LR Classic the brush (so far) seems to act normally.
Also it is impossible to select the help menu when this is happening. Selecting help results in the Plugin menu as soon as you try to make a selecteion. Selection Window give you the view menu.
Copy link to clipboard
Copied
Hi @Sandy694
Go to Preferences > Technology Previews... and enable āOlder GPU mode (pre 2016)ā - Restart Photoshop. Does the problem persist?
Copy link to clipboard
Copied
Copy link to clipboard
Copied
LR 13.0.1 & PS 25.2. The problem is still NOT fixed. PS must be opened BEFORE sending an image from LR to PS for editing or PS is unusable due to the jumping cursor!
Copy link to clipboard
Copied
Unfortunately the problem persists.
Opened the beta. Change the graphic setting as instructed. Closed beta. Opened LR classic. Opened previously created PSD from LR to PS beta which reopened the PS beta. Problem not resolved.
Changed the beta setting back to it being unchecked. Closed and reopened beta, then opened LR classic. Opened/transferred/edited the same PSD file in PS beta which reopened the beta version. Problem NOT there. No jumping brush or selection.
I really think there is something with the way LR classic is opening and sending a file to the beta version that is causing this. Both LR and beta have been updated via the CC app.
I'm using a NVIDIA GeForce RTX 3080 Ti. There was an updated studio driver since this problem started, but it did not fix the described bug.
Thanks
Copy link to clipboard
Copied
OOPS.... made a mistake in the previous post and I can't edit it!
"Changed the beta setting back to it being unchecked. Closed and reopened beta, then opened LR classic. Opened/transferred/edited the same PSD file in PS beta which reopened the beta version. Problem NOT there. No jumping brush or selection." INCORRECT. It did not reopen the beta version as it was already open. That is the difference between having the problem or no problem. Sorry for the confusion.
Copy link to clipboard
Copied
FWIIW the problem is still there!
Copy link to clipboard
Copied
THE PROBLEM IS STILL HERE WITH THE RELEASE VERSION 25 OF PS!!!!!!!!!!!!! YES I AM FRUSTRATED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Copy link to clipboard
Copied
This is sill not fixed in LR 13.1 and PS 25! PS MUST be open before you try to send a photo from LR to PS.
Copy link to clipboard
Copied
Sandy, are you saying that the brush stroke is offset from the cursor, or that the stroke moves to the bottom left with no input from you?
How many screens are you using?
If more than one, do you have the Wacom tablet calibrated to cover both/all, or just the main screen?
Have you Googled and found other people with a similar issue? If yes, can you post the links please?
I assume your system is fairly new if you are using an RTX3080 Ti. That shouldn't qualify as an 'Older GPU' either, but Cory did not know what GPU you had when he suggested using that setting.
Do you have the beta version installed, and if yes, is the issue present when using it? A lot of display related issues seem to be fixed when using Disable Native Canvas. That option was removed from the previous full release version, but it is back in 25.2 so worth a try.
Which API do you use with the tablet? (Windows Ink, or Win Tab)
One last thing you could try is Lazy Nezumi Pro. It fixes things like the shoelace artifacts and has a zillion hand presets. It has a trial period that should be long enough to evaluate its effectiveness.
Copy link to clipboard
Copied
Thanks for the response.
Some further elaboration. This is very similar to a problem that existed about 3? years ago (https://community.adobe.com/t5/photoshop-ecosystem-discussions/photoshop-cc-21-1-0-cursor-jumping-aw...). It was eventually fixed, but came back during the betas for generative fill (see my first post in this thread.) The only improvement I noted during subsequent beta releases was that I didn't have to open PS before opening LR, but I did have to make sure PS was open before transferring an image to PS for editing. If I opened PS from LR via "edit in" PS was unusable. The cursor acts the same with both Logitech mouse and Wacom intuos5 tablet pen.
Basically drawing a straight line with a brush or lasso tool results in multiple scribbled lines to the left. Clicking on a menu dropdown gives me the menu item 1 to 2 menus to the left. See the images below.
Window 10 with all updates (except the "previews")
The mouse isLogitechh blue tooth. The Wacom tablet is wired (USB). Windows ink is disabled in the Wacom pen settings. I'm using Wacom software that I think has been updated at least twice since this started. Current version 3.8.10.59.
When I had this problem 3? years ago I was using an oldergraphicss card that has since died.
I just tried disabling native canvas. No joy.
I've never heard of Nezumi. I never use smoothing. Back when it came out it made my system horribly slow and was never something I felt useful. Smoothing is set to 0 for albrusheshs. I will think about that suggestion.
I hope this makes sense.
Copy link to clipboard
Copied
No change with LRc 13.1 & PS 25.3.1
Copy link to clipboard
Copied
If anyone cares this is still broken in the LR 13.1 and PS 25.4.0. And now brushes are broken too!
Opening a file from LR to PS, drawing is fine. Start masking, the brush has no visible line until after the pen OR mouse is released. From then on the brush will not draw normally even when not in masking mode.
If the same file is opened directly into PS (not from LR) the brush/pencils behave normally.
Copy link to clipboard
Copied
I did find the problem with the brushes (it was a plugin), but removing plugins did not help the original problem noted in the first message.