Florida

Thanks for the larger explanation, it does seem a rather sketchy feature. I need to make images without anti-aliasing because they are used in a generative art process that does not work with anti-aliasing in the images. Currently, there is no app that does that very well, not even Photoshop. If you could set a coverage map for a document and have that be the default for new layers, and for rasterization, that would make my life so much easier.

Every time I draw a shape, I have to change the coverage map to eliminate the anti-aliasing. What I want to do is, before I create any shapes, have it set as the default so it automatically uses the coverage map setting when a new layer is made. Is there any way to do this? You can set it with no layer present, but AP ignores it when making a new layer. The other issue is Rasterize... a layer with a coverage map set to no anti-alias... will add the anti-alias back. Rasterize should not change the current layer at all by adding anti-aliasing. AP2 242 MacOS 14.4.1

Hmm, how did I wind up with an adjustment layer with a mask? Now I see how to make it work normally again, but I wonder how I got here in the first place. Thanks for the help, this is a really confusing feature.

The manual states "Adjustment layers only affect layers which are below them". This is NOT what is happening. It is only applying to the one layer directly below. There is a new button "Edit All Layers," but it does nothing and does not seem to be documented that I can find. This is the little icon on the left. It would seem to imply that this button would affect if the adjustment applies to a single layer or all layers below, but it does not seem to change anything.

But it's only applying to the layer below; previously, adjustments always applied to all layers below. How do I get that behavior back? This basically makes everything I do impossible. Even if I group all the layers below, the adjustment only applies to the first layer in the group. This is either a terrible bug or some feature I cannot find to turn off. Even if I put the adjustment inside the group it only applies to the first layer. If this can't be changed, then I can no longer use AP. Using 2.2.0 on M1 Mac Studio.

Why am I seeing the icon to the left of "White Balance Adjustment". I've never seen this before and there seems no explanation as to what it is (seems to only affect the layer below I think) or how to get rid of it. Normally I expect adjustment layers to affect ALL layers below which is what I want. Not sure how to look this up in a FAQ as I don't know what it is called. I assume I did something to make this appear.

I wonder if Affinity built its own blend methods or if it uses native ones on Mac vs Windows. Apple's Core Image does all the blends that Affinity needs (plus a ton of other image processing features). Photoshop seems to do its own cross-platform thing, as far as I can tell. Using platform libraries could explain slight differences, while writing your own instead could have unique bugs as well.

Maybe they fixed it. Note I found this result on an M1 Ultra on the latest MacOS, so maybe it's a hardware-or-OS-dependent bug. In my test case (a wide variety of red shades) every one matched my result except this 255 vs 0 case.

It won't let me upload for some reason. "Sorry, an unknown server error occurred when uploading this file. (Error code: -200)" However, I compressed the file and it uploaded ok. color dodge bug.zip

I tested some code implementing color blends matching Photoshop and AP I found an inconsistency in AP for Color Dodge. If you have two Fill layers, one pure red (255,0,0) and one black (0,0,0) and use Color Dodge, you get pure red as per the math. If you have two Pixel layers, one pure red (255,0,0) and one black (0,0,0) and use Color Dodge, you get pure black which is wrong. I have a document that shows this issue, but for some reason, the Upload Files fails on the AP document (error 200). Mac OS 13.4.1 (c) (22F770820d) AP 2.1.1 on an M1 Ultra Mac Studio color dodge bug.afphoto

Still broken in 2.1 sadly. I assume its a P4.

9000x9000 or bigger will calculate the size (now with %) but will not show the contents at all. This has been happening for several releases in a row. Plus in the latest 2.1 release there seems to be no way to zoom the preview at all. Several releases ago command+ or - would zoom the preview, then when the preview started having issues with 9000+ previews, you had to tab from the % field; in the new release that no longer works either, so zooming seems removed entirely unless there is some magical key now. I think the previous release stopped at 6000x6000 or so, this one seems to do 8000x8000. This seems like a trivial bug to fix. Most of my images are large and this means I can't preview them. Note that every image type has the same issue, except for GIF which seems to just sit there at 0%.

I saw this frequently on Photo 1 as well, but only after a significant number of operations in the current session. I believe the memory management fragments terribly and takes longer and longer to function. I also have the same hardware but with M1 Ultra. Generally I watch the memory usage and restart if it grows too large.

I previously reported that previews failed to show for anything above 8000+ px or so, so it might be the same issue, and unrelated to anything other than the size of the image.