Grayscale export no longer transparent - Affinity Photo 2.1.0

[AnD4D]

I've needed to export some pngs both in colour and grayscale.

I found that I was able to do this simply by changing the pixel format to grayscale 8-bit.

This has been working fine for a long time. However, I recently updated Affinity Photo, and now each time I change the profile, it becomes no longer transparent.

Then, when I switch it back to Use Document Format, it still isn't transparent. In order to get it back, I have to revert the preset back to PNG.

Is this a bug, or working as intended? Honestly, I prefer it the original way.

Is there a faster way of exporting a transparent grayscale that I'm missing?

[AnD4D]

Note how the edges are black. I can see a transparent icon in the matte section, but clicking it seemingly does nothing.

[Pšenda]

23 minutes ago, AnD4D said:

Is there a faster way of exporting a transparent grayscale that I'm missing?

Export persona? Two setup (color + grayscale) for one Slice.
 

Edited June 1 by Pšenda

[AnD4D]

5 minutes ago, Pšenda said:

Export persona? Two setup (color + grayscale) for one Slice.
 

That's great. Thank you. Strangely enough, if I change the setting here, it still exports with transparent enabled, so I assume a bug is preventing me from doing my previous method.

[NathanC]

Hi @AnD4D welcome to the forums,

45 minutes ago, AnD4D said:

Then, when I switch it back to Use Document Format, it still isn't transparent. In order to get it back, I have to revert the preset back to PNG.

Is this a bug, or working as intended? Honestly, I prefer it the original way.

This is a known bug currently logged with the developers in 2.1, I've bumped this thread with your report, there is a workaround available for this without having to resort to the default presets, I've linked a post below which details a workaround by using the swatches no fill/transparency option.

 

[Serif Info Bot]

The issue "PNG with Selection Only shows white background after toggling Embed ICC profiles" (REF: AFP-6164) has been fixed by the developers in internal build "2.1.1.1847".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

[Serif Info Bot]

 Build 2.1.1 (build 1847) is now available as a Customer Beta

We would appreciate you trying the beta build for yourself to check that the fix listed by Serif Info Bot above has been fixed for you. If it has NOT been fixed please post into the announcement post rather than here.