Problem regarding FX Outline Contour Midpoints in Photo 2.3.0

[laskop]

I am editing a document in Designer (2.3.0) with text that has outline FX that I have set to Contour.  When I move the gradient midpoints in Designer, the gradient reacts accordingly but when I switched over to Photo (2.3.0) I revisited the FX and changing the midpoint had absolutely no visual change to the outline contour.  I did a search and could find no information regarding this functionality inconsistency.  I created a new file directly in Photo to narrow down the possibility of an issue with my particular file and it's doing the same thing.  Is this a known issue or did I just find something?

I am on Windows 10 Home. My system specs are Core i7-9700k, EVGA RTX 2080 Super, 32GB of RAM.

[NotMyFault]

Any chance you can upload the file showing the issue?
If Photo renders the same different than Designer, the issue is probably caused by HW acceleration.

What happens if you switch view mode to pixel in Designer?

[laskop]

In Designer, regardless of the mode, the Contour gradient updates correctly when moving midpoints.

I can reproduce the issue in Photo 2 in any document I open, even new ones, so the issue is not with my particular file.  Here is a test file I created.  I moved the midpoint all the way over and it still is at its midpoint on the text.  However, if I open the same file in Designer and move the midpoint, it will work right.

Contour FX Test-no midpoint change.afphoto

[MEB]

Hi @laskop,
Welcome to Affinity Forums
Thanks for your report. I've reproduced this here and I'm logging the issue.

[Affinity Info Bot]

The issue "Outline FX, Fill Style > Contour: changing the Gradient Mid Point does nothing in Affinity Photo" (REF: AF-1636) 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.