Photoshop 21.0: Errors when using Knock Out Layers

  • 1
  • Problem
  • Updated 8 months ago
  • Solved
  • (Edited)
When I open a document with a Layer Group set to Knock Out (Shallow in this case), it appears to not be working (i.e., not knocking anything out), but when I simply click on the Layer Group to open Layer Styles, the knock out suddenly appears correctly. However if I then save the doc and reopen it the problem is back. 

Also, I frequently make Knock Out Layer Groups which contains other Knock Outs within them (i.e., punch a hole in a full-canvas Knock Out layer). These do not seem to be working either (at least not in legacy documents), although I've had limited success in rebuilding them from scratch. 

This is on Mac OS 10.14.6 (Mojave).

Thank you
Photo of STEVE SETLIK

STEVE SETLIK

  • 15 Posts
  • 1 Reply Like

Posted 9 months ago

  • 1
Photo of Andrew Sender

Andrew Sender, Employee

  • 133 Posts
  • 59 Reply Likes
Hi Steve,
Thank you for reporting this.  We have done some improvements with blending options.  Can you please try enabling Preferences -> Performance -> Legacy Compositing and let us know if that does or does not resolve the issue.  We appreciate your feedback.  Thanks Steve!

Sincerely,
Andrew
Photo of STEVE SETLIK

STEVE SETLIK

  • 15 Posts
  • 1 Reply Like
Thank you, Andrew. That seems to have fixed the problem. 

So, is this new Knock Out behavior is intentional (meaning will it continue to not allow layer groups to be set to Knock Out) under the new blending options? What are the specific improvements that were done to blending options which I will (apparently) be missing out on?

Thanks again,
Steve 
(Edited)
Photo of Andrew Sender

Andrew Sender, Employee

  • 133 Posts
  • 59 Reply Likes
You're welcome Steve.  No, this is a bug we plan to fix in the upcoming time.  The improvements I am referring to are from our new compositing engine that increase performance.

Andrew
Photo of STEVE SETLIK

STEVE SETLIK

  • 15 Posts
  • 1 Reply Like
Thanks!
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 17097 Posts
  • 2917 Reply Likes
Official Response
This issue should be fixed in the 21.0.2 update that was released yesterday.