cellnoise functions not working (PT Filter)

[NotMyFault]

None of the cellnoise functions work in V2.3 on Mac

 

https://affinity.help/photo2/English.lproj/pages/Filters/filter_proceduraltexture.html

Voronoi Noise
cellnoise	cellnoise(S x, S y) cellnoise(S x, S y, S spread)
cellnoise2	cellnoise2(S x, S y, I degree)
cellnoisedist	cellnoisedist(S x, S y) cellnoisedist(S x, S y, S spread)
cellnoiseedge	cellnoiseedge(S x, S y, S sz, S softness)

Tried to reproduce cellnoisedge from the tutorial:

No matter what parameters you specify, the output of these PT functions is always 0.

 

[Ldina]

@NotMyFault

It took me a while and some experimentation, but I finally got the "cellnoiseedge" function to work with Procedural Textures. I am also on a Mac.

I watched the same video you did. For whatever reason, I had to add an extra Parameter (labeled "h"). It doesn't DO anything, but if I remove it, the formula doesn't  work and I get the same result as you did. It needs to be there. It's a totally mystery to me because I didn't have an "h" parameter in the equation! 

I edited the formula a little, added some descriptions to the parameters, etc. FWIW..

[NotMyFault]

4 hours ago, Ldina said:

For whatever reason, I had to add an extra Parameter (labeled "h"). It doesn't DO anything, but if I remove it, the formula doesn't  work and I get the same result as you did.

Thank you so much for sharing. That is insane. The input variable h is not even used in the formula, and normally h is a reserved name (giving the height of the document) that is not even allowed to be used as name according to Affinity doc (like x and y).

good as workaround, but even more confirms this is a bug.

and yeah, this is one of my major complaints: for several functions from PT filter, the number and/or type of parameters, or the suitable value ranges are not (correctly or fully) documented. It make a hell of difference if you need to use 0-1 (like bounded color values), small integers, positive / negative values etc. this must be documented.

[Dan C]

Thanks for your report @NotMyFault!

I can confirm this issue was found and reported internally - as it seems to only affect the Metal rendering pipeline on macOS.

This has since been marked as fixed in the latest 2.4.0.2222 beta version, so I'd recommend trying again in this version, or waiting for it to be released to retail