Skip to main content
Participant
March 6, 2019
Answered

Strange 1px black stroke when placing objects

  • March 6, 2019
  • 2 replies
  • 918 views

Hello there,

I have a weird problem. When i place objects, the black stroke appears.

I had a similar problem yesterday, but there was a white/semi white stroke around objects and problem was solved when i changed resampling method from Automatic to Bicubic Sharper (Reduction) via Image Size>Resample Method. This time no method helps, anyone imagine what to do? In original file (inside smart object) everything is perfect, no matter how much i resize it inside there is no black stroke, only when i place it somewhere else...

This topic has been closed for replies.
Correct answer c.pfaffenbichler

Then you may want to place them as two linked SO instances with Layer Comps (one for the object, one for the shadow).

The interpolation of the pixel’s color content and the transparency can in my experience produce unwanted results when the transparency combines relatively hard edged areas over partially visible ones.

2 replies

davescm
Community Expert
Community Expert
March 6, 2019

Hi

From your screenshot, the stroke only appears to affect one direction from your objects so I wonder if the artifact is coming from the drop shadow.  Is the stroke still there if you turn the drop shadow off ?

Does Preferences >Performance >Use legacy compositing make a difference?

Dave

Participant
March 6, 2019

Yes the problem is only in shadow area. c.pfaffenbichler was right. When i place them both separately in one file problem is solved

The only problem is, that i have like 500 or 600 objects in one huge file and the preview file would get huge for that much layers (even now it requires 12GB RAM just to open), but it is still way better than using smart objects.

Ant Use Legacy doesn't help.

c.pfaffenbichler
Community Expert
Community Expert
March 6, 2019

Thank you! Works perfectly, never knew this thing. Just duplicate smart object and assign different states, it's perfect, because if i want to edit original, they both lead to the same original file. I wonder how much RAM the main preview container file will eat in this method Will have to experiment.


But be warned: If you do corrections on a new Layer that did not exist when you created the Layer Comps it would not affect the SO instances and you would have to update the Comps in the SO …

And when opening the SO it may display a different state than any of the applied Layer Comps, so that might get a little confusing, especially if multiple people have to work on a file.

The whole thing may not feel very »comfortable« …

c.pfaffenbichler
Community Expert
Community Expert
March 6, 2019

Are object and shadow one image?

Edit: The interpolation of the pixel’s color content and the transparency can in my experience produce unwanted results when the transparency combines relatively hard edged areas over partially visible ones.

Participant
March 6, 2019

Yes, one image. But in smart object they are separate, shadow is extracted.

c.pfaffenbichler
Community Expert
c.pfaffenbichlerCommunity ExpertCorrect answer
Community Expert
March 6, 2019

Then you may want to place them as two linked SO instances with Layer Comps (one for the object, one for the shadow).

The interpolation of the pixel’s color content and the transparency can in my experience produce unwanted results when the transparency combines relatively hard edged areas over partially visible ones.