FX properties not displaying correct values.

[Bryan Rieger]

I just discovered a very annoying little bug in Designer (it may be in the other apps but I haven't checked).

Apparently you can't trust the values shown in the Highlight and Shadow properties. In the example below it's displaying that the highlight is set to the Add blend mode when in actuality it is set to Colour Dodge. Same with the Shadow property (not shown). It says Colour Burn, but displaying the pop-up shows it to be multiply. 

While I can get the to render the blend mode I want (usually), the values displayed in the properties are always wrong. I've run into a few problems where I've gone around in circles trying to adjust these values, but the rendering never updates. It often requires a few tries to get the blend effect that I want.

[Hangman]

Basically four of the groups are misordered when comparing the Dropdown option with the Highlight option...

Highlight and Shadow Values

Group 2 - Dropdown Option Shown | Highlight Option

Darken - Darken
Multiply - Colour Burn
Colour Burn - Linear Burn
Linear Burn - Darker Colour
Darker Colour - Multiply

Group 3 - Dropdown Option Shown | Highlight Option

Lighten - Lighten
Screen - Colour Dodge
Colour Dodge - Add
Add - Lighter Colour
Lighten Colour - Screen

Group 4 - Dropdown Option Shown | Highlight Option

Overlay - Overlay
Soft Light - Soft Light
Hard Light - Hard Light
Vivid Light - Vivid Light
Linear Light - Pin Light
Pin Light - Linear Light
Hard Mix - Hard Mix

Group 6 - Dropdown Option Shown | Highlight Option

Hue - Hue
Saturation - Saturation
Colour - Luminosity
Luminosity - Colour

[Dan C]

Hi, 

I've confirmed and reported this as a bug.

Lee

[Affinity Info Bot]

The issue "[macOS] Layer FX- Bevel/Emboss default blend modes display the incorrect blend mode" (REF: AF-1381) has been fixed by the developers in internal build "2.4.0.2222".
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.