NotMyFault

Genauer: gelöst ist (nur) das Farben auf Gruppen angewendet für Vector/pixel Layer unterschiedliche Ergebnisse liefern. Adjustmenst in CMYK ist eher grundsätzlicher Natur, bzw. Unzureichende Dokumentation und Anleitung.

Ich hab das Problem gar nicht selbst! Ein notwendiger trigger ist wohl Apple Display (MacBook), ich habe einen MacMini mit LG Display und ganz anderen Farbprofilen (Spider Kalibriert oder DCI-P3 Standard).

Das ist zum Glück gelöst in V2.3

Das wäre es wert in die FAQ Liste zu kommen. Falls die Moderatoren nicht darauf ansprechen: Tutorial, damit man es bei neuen fällen schnell als Referenz findet.

Another workaround: use transform tool to temporary rotate layer to intended degree (center anchor point) apply gradient fill by gradient fill tools, using constraints modifyer key Reset layer rotation to 0

Windows preview app does not support color profiles correctly. The file uses GREY/8. if you want to see it correctly with those app, export with sRGB profile.

yes, simply open it

No. There are only „potentially lost“ if you don’t use the method described above, and export the file. Affinity stated consistently it does work as designed. This thread is a feature request, and it will become more likely to getting implemented if more users add their vote and provide arguments how this would improve their workflows and why workarounds are not sufficient.

You need to recover RGB channels by the method described here: only 2 steps, can be recorded as macro and assigned a keyboard shortcut.

Can you please provide a screen recording, full window covered including the layer panel visible? I cannot reproduce

Reminds me of this (unfixed) issue:

I would object in this case. a symbol allows only one single child object when creating it (otherwise multiple symbols will be created, one per selected layer), so I mostly group layers first to be able to create a symbol. It makes no sense to call it symbol group if it is not grouping at all.

Once a made a file containing all filter (From Photo) for usage in Designer. Seems I need to repeat the process and include all adjustment layers. Some filters depend on color mode, e.g. Procedural Texture, so you need one per color format.

Seems solved in V2.3 thank you Serif team.

Both statements are true: by default the UI shows „none“ as gradient type you can simply start dragging a linear gradient without choosing a type before. The type is set automatically to linear.

This is totally off topic to this thread and should be moved to feature requests / feedback

Similar to vector layers and other layer types who show blend mode passtrough. There are more bugs related to symbols mixed up with groups when used with constraint groups. Symbols have special abilities which normal groups don’t have. Why are only symbols misinterpreted, but vector layers not?

Thank you for the workaround, never the less this should be fixed.

Can confirm this bug on iPad. instead of blend range, you may use gamma slider. Effect vanishes for default gamma 2.2 but becomes effective for any other value. please keep in mind that sliders for numeric have another bug. For many you can mircro-adjust the value to a bit higher / lower, but the displayed value remains unchanged. So you often have 3 numeric values all giving the same UI value, e.g. color or opacity sliders.

Works for me on iPad. The command uses letter O (shift-cmd-O), not digit zero. But all shortcuts depend on language settings and may do not work if non-English keyboards are used. Happens to me with German keyboard, especially when modifier keys are used for letters which require a modifier key to reach in my non-en keyboard layout like []

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.

Selection from Layer, Shift-cmd-O should work.

I spent countless hours to work with PT filter, apply image, equations filter etc. Really nice in principle, but so many shortcomings, bugs, lack of documentation. Even after specifically requesting documentation the answer was "this is a standard library we use" without any further details (which library, where to find more documentation). I searched more and found loose relation to OpenGL and other GPU APIs.

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.

Some of the functions are simply broken and do not work at all, or documentation is simply wrong about number / type of parameters. despite the procedural texture is listed as filter, it is actually less powerful and more an adjustment. For Vornoi functionality, you would need a blur functionality: calculate an average color over multiple x/y positions. This is not possible in PT filter. You can only access the actual x/y position but no color values from neighboring pixels. PS: just raised this one.