Copy link to clipboard
Copied
I'm trying to edit an old path in an image (path was formerly created). Somehow I cannot amend the path, which means though I can delete old direction points, but I cannot add new points to the path (it will just create single direction points not connected to the path with connection lines). Then if I delete the old path and create a new one, it all of a sudden works. But that would be too elaborately.
1 Correct answer
Maintain a WORK PATH, then working on named Patsh should function as expected.
Explore related tutorials & articles
Copy link to clipboard
Copied
Maintain a WORK PATH, then working on named Patsh should function as expected.
Copy link to clipboard
Copied
Lena, have you installed the 22.3.1 update? That might have fixed some of the path issue some people have been having.
Copy link to clipboard
Copied
I haven’t yet installed the update but in the Bug Report-thread it has been mentioned that the bug has gone unfixed in 22.3.1.
Copy link to clipboard
Copied
And the forum has gone crazy with V22.3.1 GPU issues. I don't think I can remember a response this big before. We should maybe ask those thread starters to tell us what hardware and OS they are using to see if there are commonalities.
Copy link to clipboard
Copied
No, the 22.3.1 update still has the same issue with paths. I dont understand why it is not fixed. Using this feature a lot I find this very annoying.
Copy link to clipboard
Copied
@Trevor.Dennis @c.pfaffenbichler
thanks for the answers, have been looking at it via remote with the Adobe Support. Turns out we had to go back to version 21.2.7 (we had the newest installed). They said that it has to be a problem with our graphic card (which is NVIDIA GeForce GTX 1060, Working with Windows 10), that is not compatible with the newest Photoshop version. Now we cannot upgrade anymore. I think the answer is not so satisfying from the side of Adobe.
Copy link to clipboard
Copied
»They said that it has to be a problem with our graphic card«
As far as the Pen Tool-bug is concerned that would have been a flat-out false statement.
The bug has been achnowledged by Adobe, see
If the representative/s you talked to did not know that you have to decide for yourself if it’s worth the trouble to follow up on that.
Edit: Adobe Support has often been criticized …
Copy link to clipboard
Copied
Yes, thank you again! Interesting that it's acknowledged already...
It took us almost the whole morning and cost us many nerves to get this information from Adobe... But good to know (once again) that we can solve it also by maintaining a work path.
Copy link to clipboard
Copied
You will have to decide for yourself whether you prefer rolling back Photoshop (might be necessary for other, actual GPU-issues) or use the work-around.