dolunaykiz

I created a macro to replicate what CTRL+SHIFT+J would do in Photoshop. That is, it is supposed to duplicate the first layer, fill that original one with white, then duplicate copy again. What I should end up with is a white bottom layer and then two identical layers with the actual picture content on top of it. Because all filters in Affinity Photo are destructive, this saves me the time to duplicate the original layer manually. And it worked until yesterday. Now, when I run the macro, it keeps the original layer and fills the other two with white. This only happens on some images, and there is no rhyme or reason why.

Thanks for the input. None of the Nik Collection should crash anything IMHO. We've already been through it.

Nik Collection just prompted me to install an upgrade to version 2.3.0.0. I am on Affinity Photo 1.7.3 and I want to avoid another disaster like what we experienced about a year ago with Nik just bombing on Affinity Photo. That was only changed when the finger pointing and shoulder shrugging caused a user community sh*t storm. However, I don't have time for the same thing this time around. Can anybody tell me if this is compatible BEFORE I install the upgrade, please? If it is not compatible, when can we expect it to be? Thanks. PS. I am on Mac OS Catalina.

DxO, first paid version. Right now I don't have the funds to buy the 2.0, and frankly, I shouldn't need to.

Update: it just started happening again. I've been processing a few photos in a row, and the preview comes up blank. I mean, WHAT?

PS. This seems to come and go. Right now it seems to work again?

I am using Affinity Photo, latest version, on a Mac. As unsatisfactory as things have been, the latest fix seemed to make Nik usable again on Affinity. Until just now, when all of a sudden - and mind you, nothing had changed in my setup from one moment to the next, other than me opening another file - Color Efex and Silver Efex came up with basically empty previews. As in, you see just a B&W raster screen, that is it. I mean, can we make this a stable thing here, people? When it crapped up last time, we got some BS about how Photo wasn't meant to support PS plugins (which is why there's a plugins folder etc.?!?!), and I understand we can't just wave a magic wand over some things. But I mean, COME ON, PEOPLE!!!

OMG, this has got to be the stupidest thing. When you copy adjustment layers from another document, unlike photoshop the layer is the dimension of that first document. It doesn't adjust to where it's dragged, no matter what you fill it with. That should DEFINITELY be fixed. Jeezes.

I know how to use layer masks. I know what to do w/ them. It seems that Affinity Photo doesn't. If I paint w/ black on a layer mask I expect the photo to show a result in the viewer, but it doesn't. Or it only does on parts of it and on the others it's as I'd never painted on them.

and BTW, i just experienced the same thing again. this time on an adjustment layer with only one mask. i could paint on one side of the mask and it would register, but not on the other. this is not normal behavior.

I'm currently on the Beta version of Photo owing to the Nik Filter issues this resolves. However, the issue I am seeing should have nothing to do with that, it occurs on both versions. I recorded a macro when I first got on Affinity Photo which selects the background layer, duplicates it, fills the original layer with white, and as a last step renames the copied layer "Layer 1". All of a sudden every once in a while, the only thing I get is a blank layer filled with black on top of the background layer called "Layer 1". It's hit and miss. Sometimes it works, sometimes it doesn't.

I should have phrased it better. The issue occurred when I put a mask on an actual layer and painted on it. Nothing happened.

It's like, you paint on the mask, and nothing happens. I mean, WTH?

This is a bug regarding adjustment layers. So I have a picture open and I make a brightness adjustment. Apart from the fact that the layer mask isn't automatically added to the adjustment layer, like in PS - but I can live w/ that - when I do make adjustments, they are not reflected in the file. Like I paint on the layer mask I just manually added in black or white, and it's like I never did anything. This isn't just an issue w/ the new beta, it's been an issue. Is this a memory problem? What is going on here?

Second that. Viveza still shows the washed-out colors, but I can live w/ that. Thanks!!