JazzTwitJohn

I’m still seeing this bug on the very latest Windows AD2 Beta. Has this been acknowledged as a bug? Are there another threads about this problem? I have a compound within a symbol. I add a new shape and it defaults to Add boolean. I change it to Subtract within one symbol and it does not change to Subtract in the others.

My mistake, the Beta has fixed this problem. Ignore my above post.

@Serif Info Bot I have a similar bug and it is not fixed by using the Beta build "2.1.0.1714". I am using text NOT converted to curves and trying XOR it with a background of rectangles in a Compound. I made a compound of black rectangles as background XOR'd with black text. It works fine in AD v1 but in latest v2 and latest v2 Beta it does not work. In v2, the output display is just glitchy (see attached image) and as I move the text around, the software crashes. In the v2 Beta, the resulting boolean output is just blank. I have attached the source file. XOR2.afdesign

Not allowing save as v1 format does seem like an omission that will hamper the Affinity community working with each other.

I've been following this thread. I have a computer science background, I know what anti-aliasing is from a university course back in 1986. I've been using AD for about a year. I am using symbols to make my vector design symmetrical at the point of reflection. It works beautifully, except that at the join there is a fine line appears between the two reflected clipping rectangles. The rectangles are perfectly placed, using snapping, so it looks like anti-aliasing. I go to the layer options Cog and force anti-aliasing OFF and the line on the screen disappears. But then I can no longer export as PNG without horrible pixelated curves. If I leave it ON or set to Inherit, the fine line appears in the exported PNG. Is there a fix?