PHOTOSHOP CC 2015 - Locked Smart Layers don't update across artboards - instead they create new instances!

  • 1
  • Problem
  • Updated 3 years ago
  • (Edited)
Found a very frustrating and time consuming bug in PS CC 2015 today.

I have an embedded smart layer which is the background I'm using over 8 different Art-boards in the same file.
I'm using a smart layer so that if I want to change the background I change it once and it updates in all art-boards... simple stuff

The problem is when editing each art-board I need to lock the background layer so I don't move it whilst selecting other things. This is fine until I made a change to the smart-object background, expecting to see it update across all art-boards, when it only updated on a couple of them.

Checking each art-board layer stack carefully, I noticed that the ones who's backgrounds didn't update happened to be locked, so I unlocked them and saved the embedded smart layer again expecting that it was just a refreshing bug.

It turns out that the locked layers have each created their own instances of the smart layer!
If I unlock then double click to edit one of the layers that was locked during a change to the smart-layer, it now has an incremented PSB file "smartlayer(1).psb".

This is terrible, It turns out I've been destroying links to smart-layers all over because of this bug, accidentally making new instances of smart-layers every time I make an edit and have layers locked.
Needless to say this is also expanding the filesize each time.

Hopefully other people have noticed this bug so that adobe can get a fix out asap, I can't imagine any reason why you'd need this as a feature??

Anyone else found this, Anyone from Adobe confirm they've heard of this?

Thanks is Advance


  • 1 Post
  • 0 Reply Likes
  • frustrated

Posted 3 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 823 Reply Likes
I haven't heard of this before, but have asked some folks on the team to investigate.
Photo of eartho


  • 866 Posts
  • 243 Reply Likes
what happens when you use a linked smart object instead of an embedded one?