Skip to main content
Participant
March 10, 2021
Answered

P: Pen Tool Not Working as it should

  • March 10, 2021
  • 338 replies
  • 23209 views

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?

Correct answer nikunj.m

Hi,

 

We're happy to announce the release of Photoshop 22.4 which should include the fix for this issue. To update Photoshop to the latest version, you can check: https://helpx.adobe.com/creative-cloud/help/creative-cloud-updates.html

 

For information on other issues fixed with this update, please check: https://helpx.adobe.com/photoshop/kb/fixed-issues.html

 

Regards,

Nikunj

338 replies

Inspiring
March 16, 2021

WTF has happen to the path tool?!?!?! I can't work on any named path, it just draws individual nodes!! What an absolute joke!!! When will Photoshop start testing the release properly before releasing them, this impacts workflow massively!!

Participating Frequently
March 15, 2021

Thanks, just adding more info if required. Rolled back to 22.2.

All the best!

c.pfaffenbichler
Community Expert
Community Expert
March 15, 2021

The issue has been acknowledged; until a fix is released you can either use the work-around or roll back Photoshop. 

Participating Frequently
March 15, 2021

I have the same issue here for Photoshop CC 22.3.0, rubber band option and connecting lines not showing as before on Mac 10.15.7 Catalina. Advanced Graphics Processor Settings on Drawing Mode.

Inspiring
March 15, 2021

Same problem here. This is costing me time and money. Grr

Thanks for the workaround suggestions.

Dominik Sourcé
Inspiring
March 13, 2021

The proposed workaround does indeed work perfectly fine. And to be honest it's even a rather easy workaround. Nonetheless I do want to emphasize that the number of severe bugs is growing and growing. And paths are one of THE most essential tools in Photoshop. So this annoys a lot of us many times a day. Please fix this within days or weeks not months.

Known Participant
March 13, 2021

Yes, it's true, you can lose settings by rolling back.

I forgot to backup my PS settings in one of my rollbacks and had to drag them from Time Machine so no big deal but it's good to have a little folder with them where the settings are always there waiting for the next rollback. Not just the workspace, but actions and other presets got screwy. You can get them back from your backup drive if you have one.

c.pfaffenbichler
Community Expert
Community Expert
March 13, 2021

First off: For me the work-around (maintaining a Work Path while working on named Paths) works just fine. 

Secondly: If you re-install the older version make sure to back-up all your customised presets first. I think I have read from people who lost their settings when rolling back the Photoshop version. 

Inspiring
March 13, 2021

I also stumbled across the problem today. From now on I will ignore any Adobe updates. It can't be that with every update the programm has new bug. I don't understand why this is not tested properly internally. Now I seriously have to uninstall my Photoshop and install an old version? 
Please, before you release the next update, test it. What I also don't find cool is that I now have to set up a test machine for every update in order to avoid such problems in production. Think about when this happens in an agency with many computers. The whole department is paralysed for some time.

Please excuse me for writing in such a testy manner, but I had the problem once before that the path tool did not work properly and Photoshop always crashed and it cost me some nerves until the problem was solved. I am just tense!

c.pfaffenbichler
Community Expert
Community Expert
March 13, 2021

Have you tried the work-around of maintaining a Work Path while working on named Paths?