passthrough blend mode alters colors

[keiichi77]

Both groups contain one greyscale mask on top of one magenta shape layer
first group set to normal second group set to passthrough blending. where does the yellowish color come from in the second group and where does the grey come from?
it is visible on the picture that above the transparent region the passthrough blending works as intended, but above the white rectangle the math goes erratic.

[- S -]

It's broken and always has been.  I wouldn't hold your breath for a fix.

https://forum.affinity.serif.com/index.php?/topic/164235-masking-a-group-causes-colour-fringes-due-to-passthrough-blending-mode/

Sample file:

Sample.afphoto

 

[Alex_M]

I've had this problem many times and it sucks. 

[Dan C]

Hi @keiichi77,

Thanks for your report!

As mentioned above this issue is currently logged with our development team - I will be sure to 'bump' this now to bring it to their attention once again.

I hope this helps

[FeldrinH]

Is there any way to know how high this issue is on the development team's list of priorities?

For me this is easily among my top 2 issues that make me want to switch back to Photoshop, but for the development team it seems to be a fairly low priority, because I've found posts on this forum from 4 years ago that describe this exact issue and yet it has still not been fixed.

[Meliora spero]

Dev team?

Blend modes need to work. Instead of giving them all unneeded shortcuts, focus on making them work? The attention must come from higher up in the hierarchy - it requires a renewed business prioritization of the error. Changed colors are critically important for design. It should not come as a surprise to anyone. Maybe Canva.

[Dan C]

On 5/11/2024 at 3:30 PM, FeldrinH said:

Is there any way to know how high this issue is on the development team's list of priorities?

Unfortunately our team don't provide a public 'priority' for logged issues, or estimated timescales for bug fixes, our apologies.

I can however confirm that this is reported as a High Impact issue and I have personally brought this to our teams attention once again now, in order to request it is further investigated and resolved in a future build as I certainly understand how frustrating this can be.

I hope this clears things up.

[lepr]

On 5/13/2024 at 10:32 AM, Dan C said:

this is reported as a High Impact issue

If a high impact issue remains unfixed for a decade, there is absolutely zero prospect of a medium impact issue being fixed.