DJ

3 Messages

 • 

144 Points

Wed, Mar 10, 2021 10:43 AM

Photoshop 22.3.0: Pen Tool Not Working as it should

I have just updated Photoshop to v22.3 (10 March 2021). When I try to use the Pen Tool it puts the nodes in but doesn't create a linking line. I have closed everything and re-started my PC but the error still there. I've been trying to find a way to report this to Adobe but this is the only feedback area I can find. I have been using Photoshop for over 20 years and using the Pen Tool all that time. I need to complete a job but I'm now stuck as I need this tool.

Can I uninstall this update?

Anyone else having this problem?

Do Adobe monitor this feed?

Responses

3 Messages

 • 

82 Points

15 d ago

I've lost time and money because of this bug. I've had it with Adobe. It's not worth the $50/month. I can get better reliability from old copies on CD. 

12 Messages

 • 

170 Points

I agree..... lost time and money as well

4 Messages

 • 

98 Points

14 d ago

I've been having major issues with the Pen tool, creating paths, dragging control points, etc. using PS in conjunction with Wacom Intuos Pro tablet. 

This is my work desktop that runs Windows 10. Issues started happening this year.

-My Wacom tablet pen when pressed creates a white ring on screen...super glitchy

-I'm unable to select multiple points and drag them with tablet pen. Instead, have to use the arrow keys to move a group of points.

-Can't create a closed path to use vector mask

This is driving me absolutely insane.

It's preventing me from getting my work done efficiently.

Adobe, WTF?

Champion

 • 

1.8K Messages

 • 

26.6K Points

-Can't create a closed path to use vector mask

Did you maintain a Work Path while working on the Vector Mask? 

Could you post screenshots including the pertinent Panels? 

4 Messages

 • 

98 Points

What’s the best way to create a new Work Path? It used to not be necessary for this basic operation/task. I would just create a new path with pen tool and then use vector mask on corresponding layer.

Any insight as to why Wacom pen tool creates a white ring on screen when pressed? I may have to call my IT dept for new Comp or just request a Mac.

23 Messages

 • 

394 Points

To create a work path, just click in the image with the pen tool while no paths are selected. As for the white ring, that is a Windows setting:

REMOVE WINDOWS' CIRCLE "PEN & TOUCH" FEATURE

4 Messages

 • 

98 Points

Thank you SO much! That feature was killing my vibe. 

And yes, I hope these 'coming soon' issues are addressed. 

1 Message

 • 

60 Points

14 d ago

Copy / Paste the existing path and work on the new one

12 Messages

 • 

170 Points

That's the first thing I tried and it does not work..... had to go back to the previous version and all ok

Champion

 • 

1.8K Messages

 • 

26.6K Points

And again … 

Maintain a Work Path. 

Then working on named Paths should function as expected. 

12 Messages

 • 

170 Points

As long as you are working on the path...no problems, but once you close the path and wan to make changes by deleting a node and reconnection.... does not work

23 Messages

 • 

394 Points

Oddly enough, you do not work on the work path! Create a work path, and just leave it in the list of paths. Create as many new paths as you like while leaving the work path alone, and the other paths behave normally.

Champion

 • 

1.8K Messages

 • 

26.6K Points

As long as you are working on the path...no problems, but once you close the path and wan to make changes by deleting a node and reconnection.... does not work

Have you actually read the instruction? 

Because so far it seems every time someone claimed the work-around did not work they were wrong and just did not maintain a Work Path. 

So please post screenshots including the Paths Panel to verify your claim. 

12 Messages

 • 

170 Points

I've been a beta tester since PS 1..... I think I know what I'm doing

Champion

 • 

1.8K Messages

 • 

26.6K Points

Then please post the screenshots that illustrate that the issue occurs on your computer despite the presence of a Work Path. 

10 Messages

 • 

172 Points

Here's the screenshot

Champion

 • 

1.8K Messages

 • 

26.6K Points

Feel free to report my posts (»Flag as inappropriate«) if you think they violate Forum Guidelines or plain proper conduct, otherwise please focus on the bug and the work-around being discussed here. 

Does the work-around work for you or not? 

edited 

(edited)

12 Messages

 • 

170 Points

Sorry.... did not mean to be condescending
Here are the snapshots...
To be a little clearer. We do a lot of fashion imaging and have to correct parts of the garment to match colour perfectly. The first path around the whole garment from start to finish works with no problem. However, when you want to use part of the existing path and modify just parts of let's say the collar, duplicating the path and deleting parts of the path and rejoining does not function. Reinstalling previous version of PS 22.2 works perfectly allowing you to join the two nodes. As you can see with the snapshot.... the latest version does not allow to rejoin the path.
Ver 22.2 does. Hope this is clearer.

 

Champion

 • 

1.8K Messages

 • 

26.6K Points

I can’t see the Paths Panel in the screenshots. 

Is there Work Path (an unnamed default Path) aside from the Path you work on? 

And the condescension-accusation was directed toward me if I am not mistaken. 

118 Messages

 • 

2K Points

I misunderstood the workaround as well at first. :)

Try this:

Make sure no paths are active/ highlighted in the paths panel.

Pick the pen tool. Put a path node anywhere (outside the canvas is good). This should create a 'work path'.

Now choose the path you want to edit, and editing should be possible.

(edited)

Pixel pusher

12 Messages

 • 

170 Points

Thanks... I had gone to the previous version of PS and your suggestion works great.
I update to the latest version of PS and let you know.

Are you using the latest?

1 Message

 • 

62 Points

14 d ago

Anyone know if Adobe is addressing this issue?

23 Messages

 • 

394 Points

In a post I made about guides lagging when dragged, an Adobe employee responded it would be fixed in an update coming soon, so I'm hoping the path issues are addressed as well. As to what *coming soon* actually means, we shall see.

Champion

 • 

1.8K Messages

 • 

26.6K Points

At the top of the page there is an »acknowledged« mark. 

8 Messages

 • 

168 Points

13 d ago

I guess the PS development will fix everything in the next release v23

2 Messages

 • 

102 Points

12 d ago

Ctrl+H is my workaround.  Slows me down a lot.

Adobe engineers, we are losing money we use to pay YOUR subscription.  Why took so long (more than a month) to fix this?  Instead on bloating the software with help features.  You should focus on stability and fast bug solving.

31 Messages

 • 

606 Points

Yes! Absolutely. 

They keep putting new features in, destroying what was there before and what was considered reliable.

Like "frames". I mean: what? There are groups, layers, masks, why would you now need frames, too? Just an example… But the path tool, yea we can live without that. 

31 Messages

 • 

606 Points

10 d ago

Hi, I’ve got the same problem. Please give us a fix!

Champion

 • 

1.8K Messages

 • 

26.6K Points

The work-around has been explained again and again. 

For the actual fix we will have to wait … 

10 Messages

 • 

172 Points

Listen here Christoph. There are so many people and businesses that rely on the tools that they are PAYING FOR to work properly. Why should WE have to wait. That's like saying we have to wait months for McDonalds' to give me the fries I paid for. Do you work for Adobe or something?

Champion

 • 

1.8K Messages

 • 

26.6K Points

• Obviously I do not work for adobe. 

• Obviously we have to wait for, at least, the next Photoshop update. (edit: or roll back the Photoshop version)

With any luck the bug will be fixed there but there are no guarantees about that.

Bug-fixing in a program of the »size« of Photoshop cannot realistically be expected to happen instantaneously. 

And the Adobe employees who might actually know about the time-frame for any specific fixes are not at liberty to make announcements/promises to us here. 

(edited)

2 Messages

 • 

82 Points

@christoph_pfaffenbichler it should've been tested before rolling it out. there shouldn't have to be complicated incoherent work-arounds. stop bootlicking for a company that doesn't give a rats crusty butthole about you.

also, its not very obvious you DONT work for adobe when u defend everything they do. you're paying for a service, they aren't providing it. its as simple as that

(edited)

3 Messages

 • 

82 Points

Agreed with @borky that the testing, automated or not - at the very least should be catching and flagging (subsequently preventing a release) ALL nuanced use cases of each tool that has existed within the IDE as of two previous versions. That is the least I expect for having paid out $50/m since 2012.

Which btw, comes out just shy of...

$5,000 !!

22 Messages

 • 

354 Points

It took my breath away to read your cumulative calculation. Me too!

23 Messages

 • 

394 Points

The workaround is in no way complicated or time-consuming. It's one more click of the pen tool to create a work path. 

4 Messages

 • 

104 Points

Kerry, if you keep it as a work path you can't save it as a clipping path (which you need for importing eps images into other programmes) and re-work it after that. You have to copy the path again and create another work path and make sure it's in the exact correct place again.... It's ridiculous!

MG

23 Messages

 • 

394 Points

No, you are misunderstanding the workaround. You merely need to have a work path present in the path palette, you do not need to create all your paths as work paths. Click in the image with the pen tool to create a work path. Now create as many new paths as your heart desires and work on them as you would normally. There is no copying, pasting, or duplicating required. 

4 Messages

 • 

104 Points

But in order to make the clipping path I have to SAVE it first ... I can't make a clipping path from the work path, it has to be 'named'...

MG

4 Messages

 • 

104 Points

Ahhhh ... yes, I can just keep a work path separately and the named/saved path works as it should. Thank you!!

MG

Champion

 • 

1.8K Messages

 • 

26.6K Points

@borky 

also, its not very obvious you DONT work for adobe when u defend everything they do. you're paying for a service, they aren't providing it. its as simple as that

Am I marked as an Adobe Employee on this Forum? No? Then I am obviously not an Adobe employee. 

And are you deliberately angling for a Forum-ban with language like

stop bootlicking for a company that doesn't give a rats crusty butthole about you.

118 Messages

 • 

2K Points

Ah. Thanks to kerrymaxwell for clarifying the workaround. This helps.

Mainly because the issue is not fixed in the latest update (22.3.1 on OSX)…

(edited)

Pixel pusher

3 Messages

 • 

82 Points

@kerrymaxwell

The workaround is in no way complicated or time-consuming. It's one more click of the pen tool to create a work path. 

I think the majority of the frustration coming from participants in this particular thread is not coming from the hassle of an additional click of the pen tool in order to create a work path as you've otherwise pointed out is not complicated or time-consuming. In my case, the frustration was and still is the fact that I spent hours trying to figure out why my muscle memory with the tool was failing me.

Once a user has learned by habit how to accomplish a series of tasks and can do so without thinking - a certain amount of trust is then baked into every user session thereafter. Although it may be a trivial thing to you or an Adobe programmer to add or remove a click to tools or workflows here or there - it is by far a short sighted perspective and lacks the professional user empathy we pay for.

We expect our payments to Adobe and their programmers to be of fair enough trade in value for maintaining a consistent bug free software environment. The payments are made with an expectation, agreement and condition that we're able to use the software as experienced at purchase time - and not on the condition or promise from Adobe that they would eventually deliver bugs into tool functionality that initially existed as bug free, and or introduce useless new features that inherently crowd the essential toolset and introduce inconvenient marketing noise into application startup with every new update. I can understand over-hating or over-doing the complaining if this were open-sourceware or freeware but it is not that. Not that at all.

If you're paying for CC and you're not frustrated with the state of affairs in updates and bugs by now - perhaps this 'unknown' additional click in creating a work path with the pen tool gets you thinking about the value exchanged for your monthly payment to Adobe.

10 Messages

 • 

150 Points

Agreed. I've used Photoshop since the beginning. It is really dismaying to see Adobe dropping the ball on established workflows. This is just one of many, many issues. I would guess Adobe is eying new lucrative markets rather than older customers. A lot of my customers have fitted out their marketing staff with the Creative Suite, and newer features and marketing certainly seem to be selling the idea that anyone can be a creative expert with a couple of clicks. Even at this one company Adobe now has at least 10 subscriptions vs one designer. Not hard to see where the money trail leads. Likewise products like Dimensions which is eating into the 3D side of my business. Of course when you are as deep in the Adobe fold as some of us long term users it can be more difficult to migrate to other tools. But every time they break another workflow they make it easier. Now I'll just get back to renaming all my Jpegs and PNGs that have "copy" tacked on the end.

118 Messages

 • 

2K Points

Agree. I've been using PS since PS 4.0

PS CC 2021 crashed on me three times this week alone, that was enough for me.

Now I've (again) gone back to using PS CC 2019, since that's the only version on my system that more or less works as it should and is stable.

I'd very happily fork over a few hundred $ to Adobe, if that provided me with a perpetual licence for a stable, bug free version of PS. So I could use that for a few years to get more work done with less frustration and less 'updates'.

If I didn't work in an industry that expects me to use PS, I'd been looking at other software by now (but obviously, 25+ years of experience with software also has you kinda 'locked in').

Pixel pusher

12 Messages

 • 

170 Points

As well, I've been using PS since the very beginning, and it seems that they are just rolling out updates and not checking what they have broken...... really sloppy!

22 Messages

 • 

354 Points

10 d ago

I was a Beta Tester for Photoshop 1.0, and a few subsequent iterations. As my workload grew, it was no longer worth the time/effort to test buggy software. But beta testers at the time were sternly warned to keep up with bug reporting, etc. 

What I find regrettable now, is that there doesn't seem to be a good bug reporting pipeline to Adobe for general users. The greater the sampling, the more likely that an aggregate number of users will discover a bug that a much smaller group of registered beta testers might miss. Especially as working users are running the app through a wide range of real life operations on a daily basis. I get the feeling that no one is listening. 

I do see a parallel with software and civil infrastructure: Politicians prefer to create something shiny & new, rather that repair a crumbling bridge. So fixing the persistent bugs seasoned users highlight, may not attract new users the way a shiny new feature does (even if it doesn't work very well).

Adobe, if you ARE listening, please consider supporting a venue where experienced users can document bugs & offer feature requests. Yes, there will be a lot to sift through, but at the bottom may be plenty of gold.

2 Messages

 • 

70 Points

Hi Guys I have just updated to the new update 22.3.1. thought they might have sorted the bug out.

Guess what! the pen tool is still not working. Come on Adobe get it sorted!

Champion

 • 

1.8K Messages

 • 

26.6K Points

I haven’t updated yet, so thanks for the heads-up. 

Yeah, it is disappointing that the bug was not fixed with the very next dot-release after being introduced. 

4 Messages

 • 

90 Points

Thanks for taking one for the team K8T.

I appreciate the time you all put into figuring out the work-around but I'm still going to hold on 22.2 until they get it right. 

Champion

 • 

1.7K Messages

 • 

29.2K Points

9 d ago

OMFG. New patch released today. 

Paths are still BROKEN.

Adobe, this is a tool used by countless professionals across multiple industries and we depend on the Paths working as expected. For this to be broken for more than a week is unacceptable. To be broken for what will eventually be months, is unimaginable.

Have you forgotten who your market is?

4 Messages

 • 

98 Points

Dear Adobe, 'Thumbs Down/dislike'

10 Messages

 • 

184 Points

Woow... that's disappointing.

Thank you for telling us. I will skipp this update to.

1 Message

 • 

60 Points

9 d ago

has this issue been addressed in v22.3.1?

118 Messages

 • 

2K Points

Sadly, no. Still need the workaround mentioned above.

Pixel pusher

4 Messages

 • 

100 Points

9 d ago

Oui, toujours le même problème après les 2 mises à jours de Adobe disponibles aujourd'hui.

Personnellement je mémorise mon tracé seulement quand il est terminé.

Le problème ne se produit pas sur un tracé de travail.

12 Messages

 • 

170 Points

8 d ago

Same problem..... and this is very important.... I use this option continually

12 Messages

 • 

170 Points

8 d ago

I'm having the same issue.... this is really import for my work

23 Messages

 • 

394 Points

Create a work path by clicking in the image with the pen tool with no paths selected, and leave it in the path list. You can then create new paths and work on them normally, and the connecting path between points will show. 

4 Messages

 • 

94 Points

7 d ago

WORK AROUND:

Make sure you have no paths selected in the paths palette and start drawing. The pen tool will create a "work path" automatically and you will see bezier curves and lines as expected. If you first create a path using the [+] path tool you will see only points with no lines and doesn't appear to function at all with selections etc.

12 Messages

 • 

170 Points

Thanks
I'll give it a shot.... right now I have down graded PS and it works perfectly!

4 Messages

 • 

94 Points

Something I just noticed is that if you go back into a completed and re-named path, it will show the bug again. So I guess the moral of the story is either back-date to earlier version of PS until this bug is fixed OR make sure your path is 100% complete and needs no further edits before you re-name it.

12 Messages

 • 

170 Points

Thanks again...much appreciated

23 Messages

 • 

394 Points

No, you can still work on named paths, as long as there is a work path present. Create a work path, and leave it in the path list, then you can create a many new paths as you like and work on them normally. There is no need to revert to an earlier version.

(edited)

4 Messages

 • 

94 Points

Thanks, @kerrymaxwell that WAS the tip of the day.

8 Messages

 • 

302 Points

6 d ago

Since at least the last couple of versions of PS CC macOS (currently 22.3.1), the pen tool has been unable to draw paths on a labelled Path layer.

In the Paths panel, if you use the 'New Path' button [+] to create a new path (Path 1) and attempt to draw a path into it, the pen tool will only place points; nothing is connected. Pathfinder operations (merge, intersect etc) are also not working.

Pen tool only creates points in named path (Path 1)

If using the Pen Tool without first creating a new path, the default Work Path is created and this still functions normally. If the Work Path is converted into a named path, then the same problem occurs again - nothing new can be added as the pen tool will only place points.

Pen tool will create connected path only on 'Work Path'
Note: This comment was created from a merged conversation originally titled Pen tool broken - will not work on named paths, only 'Work Path'

Champion

 • 

1.8K Messages

 • 

26.6K Points

And again: 

Maintain a Work Path, then you can work on named Paths as expected.