TwoKoalas

That's interesting, thanks for testing! What if I rasterize the entire page before printing from the print settings? Is there any downside doing that? I understand that it should give me exactly what I'm seeing on the screen since it's done by the Affinity engine.

Thanks Dan, I uploaded a new example that definitely prints with the error.

Hi Dan, thanks for the help and thank you very much for looking thoroughly into this. I hope you guys can track down the issue and get it sorted out in the future version!

Hi Dan, Thanks for the tips! I noticed that my prepared example doesn't show the issue. Could you please send me a link where I can upload another one that's tested? I did some tests over here and Clip Transparency doesn't do anything, but Rasterize Entire Page gets rid of the black stroke.

Hi, I consistently encounter this print error when I try to print something that had a vector brush stroke. It creates a half black rectangle stroke around the actual brush stroke. It happened with other strokes/documents as well. They only way to print this correctly is to export it to PNG and then print that. Printer: Canon TS 6350 Print settings default (no bleed/printer marks), apart from printer manages color I've attached a .afdesign file with the section that displays this error Print error.afdesign

NVIDIA GPU driver is the latest: 516.94 WHQL Using a Mouse as input device. Creating a new layer outside of the group speeds up the first stroke. It only becomes increasingly slower if I create a VERY long stroke. Creating a new layer inside the group makes no difference. The stroke is slow as in the video. Here are my settings. Didn't spot major differences with OpenCL on or off. Might be slightly slower with OpenCL off.

Hi Dan C. I've attached the .afdesign file. Hope this helps! Slow first brush evaluation.afdesign

Hi Renx-78. That looks similar to what I experience on the slow stroke. The longer you draw, the slower it becomes. This might be a slightly different issue than the first vs second stroke evaluation depending on layer/stack location. As a wild guess, I believe some optimizations should be possible on the stroke vs stack evaluation/updates code.

Thanks for checking this David. I know the values are not the same, but close. It's something I extrapolated and prepared from a real file I was working on. In any case, I don't see why it should create such a hard transition at the transparency point. Maybe it's an alpha pre-multiplication issue.

Thanks for checking this passing it to the team LeeThorpe! Same here, undoing more times doesn't restore the set FX parameters.

On export to PNG or TIF I'm noticing a solid transition line between two overlapping layers that's not visible in the viewport. This starts appearing when exporting with bicubic or higher. This can be fixed if I manually rasterize the layers before export. I thought of filing this because might expose some error under the hood. Bicubic: Bilinear export resampling error.afphoto

I have an embedded image layer with layer FX. When, by mistake, clicking with brush stroke, the layer is rasterized by the Assistant. Then, undoing the unwanted action, the layer FX parameters are not restored to the original values. 2022_09_09_1514_Photo.mp4

Thank you for trying to fix it! I will check it out! Was the fix done by recreating the shapes/stack, or is there some setting I did wrong?

The nested sub shapes have gaussian blur applied. Note that no effects are applied above the inserted/drawn shape. I stripped down the scene and I did the same test as the original post. Having the top shape selected and painting outside of the group, the first stroke is very slow and the second is much faster. Painting inside the group it behaves slowly with every stroke. 2022_09_09_1513_Designer.mp4

That's interesting, thanks for the explanation and for logging it! On a related question, I'm experiencing slowdowns by disabling all adjustment layers and painting inside a simple shape down in the stack. The speed is not recovering on the second stroke, like it did in the first example. I'm not very familiar with Designer and vector brushes, but Is this expected behavior? 2022_09_09_1512_Designer.mp4