NotMyFault

This is not fully correct, despite even being stated by moderators in the past. a live PT filter can create everything from scratch. Just include one formula to set alpha to 1. I made numerous files having only one PT filter layer.

It would be better to create a new thread in the questions section of the forum, to keep the tutorial thread focused. Can you provide the link of the video, the time code, a screen recording of what you are doing?

There are 3 adjustments who allow to impact the alpha channel: channel mixer curves levels select on of these, and choose „alpha“ channel. another option is to choose opacity of colors (for fill, stroke, or brush colors), or reduce layer opacity. The info panel (and channels panel) is only available in Photo.

See benchmark for a good indication what to expect. GPU usage is good in general, but only for bitmap operations. There are some gpu models with issues, but yours should be fine.

Maybe layer colors, a new feature in V2 https://affinity.help/designer2/en-US.lproj/pages/Layers/layerColours.html

Here an example of using a parent rectangle, with 2 child nested layers in fixed relation to upper left corner, and only the rectangle reacting to size changes. ScreenRecording_06-28-2025 18-43-20_1.mov

You can create an parent rectangle, add both child elements and adjust the constraint setting to get fixed positions to a chosen corner, and let the inner rectangle resize with the parent.

missed that.

In todays world Search results are user and location based (and ad based). nobody knows what you got as first result.

Can you please upload the example file? constraint's work on parent/child nested shapes, and child nesting inherently leads to clipping the child’s to the parent. it really depends on where exactly (relation of shapes) you add constraints. I must admit that I never used groups and constraints in combination.

The defective curves have a stroke with a pressure profile of 3 nodes. Once I reset this pressure profile, the export is correct. Use this as workaround. I use Publisher on iPad, the same function is available on Designer on Desktop. The issue is clearly a bug in Designer and not your fault. As there are many bugs already logged by Serif covering this symptoms I don’t think your case needs to be raised as new bug.

For filters and adjustments it is more complicated. Some functions are simply not defined outside the normalized 0-1 range. we have multiple stages: all functions must be offered in RGB/32 for color values from 0-1. users should have the choice if/which transfer curve will be used. Currently this requires OCIO workflows and lots of conversion layers, and the availability of presets which do not cover regular HDR photography. A tutorial from James Ritson explains this process, it takes you some time to understand the process, it is focused on blender or HDR movie creation and not on regular HDR photography. i did not extensively research which functions are clipped or simply not working at all. This should be documented by Affinity. Whenever the function is well defined for extended HDR ranges, it should be available. Whenever the function has multiple possible extensions into unbound values, it should offer the choice to users. HDR images from cameras are not totally unbound, but create images with a defined extended brightness ranges. I expect all functions working on SD content should work on HDR content in consistent ways. Clipping should only happen for values exceeding these value ranges.

The shape uses a vector brush, or has a pressure profile assigned. inspect the curve and all stroke settings. https://affinity.help/designer2ipad/en-US.lproj/pages/Panels/strokePanel.html and check the exported file, maybe the strokes got expanded. Unfortunately there are multiple unfixed bugs related to the functionality. Can you upload the file? which tool did you use to create the curves?

This bug has been reported a year ago. To keep everything organized, please report only one issue/bug at a time.

Most probably you have an selection active. Try deselect-all (cmd/ctrl D).

Opening your file on my M1 iPad, I don’t get a black screen, so cannot reproduce. And I don’t see relevant (increased) CA in the area. Boosting shadows naturally amplifies any dolor issues, as shadows are encoded with a low number of bits (even in RAW files), and brightening shadows will increase the difference of colors. I recommend to deactivate the pixel grid as it might give wrong impressions. To spot any purple areas which are the typical result of CA or fringing, I added a live hue filter. Those purple areas are still extremely dark, not noticeable for my eyes and I don’t see the need to correct. Note that when using Develop Persona you can activate CA correction manually. Using Split View I was unable to detect any difference between CA on/off.

+1 Please always search for older bug reports and add your case there if it matches.

The UI is buggy. From memory it may have been reported before, but the broken color chooser is used in many UI elements like filters, vector, text, layer fx etc and every instance seems in need to be reported individually. For me it worked when selecting color from swatch first, then switching to color mode and try again. Sometimes you need several attempts.

Schön das es gelöst ist. Weiter viel Spaß mit Photo.

Welches Werkzeug möchtest du benutzen? Bereich Auswählen (über Farbe der Pixel am Mauszeiger) Auswahlrahen (über Position des Mauszeiges) https://affinity.help/photo2/de.lproj/pages/Selections/selections_create.html Aktuell benutzt du „Bereich Auswählen“, aber für das was du vorhast ist evtl Auswahlrahmen besser.

PS besonders wichtig: bitte habe die Panels Navigator, Ebenen, Kanäle offen in den Screenshots.

Eigentlich hat sich nichts wesentliches geändert von V1 auf V2 für diese Funktion. Bitte nimm das gesamte Fenster der App in den Screenshot, damit wir alle Einstellungen für das Werkzeug sehen können. Ein Video wäre noch besser wo man nachvollziehen kann was Du genau machst. z.B. Hast du evtl. einen Radius > 0 für Abwedeln oder glätten ausgewählt, das erklärt eher den Unterschied. Oder statt subtrahieren einen anderen Modus ausgewählt. wenn möglich, lade bitte die Datei hoch wo das passiert. Ich habe V1 und V2 auf allen Plattformen und würde das gerne nachstellen.

Then we really have to doubt that the entrance statement was correct, and the tech support was competent.

We must distinguish several factors. size of objects, depending on distance: cannot be changed / corrected (in practice) in 2D apps like Affinity, unless you capture a 3D scan of the scene and use other apps for this purpose regular lens distortion: if possible, activate corrections in Camera. Otherwise, use develop persona and lens correction in Photo. This could correct the distorted door frames. fisheye effect for extreme wide lenses: can be somehow reduced, but this will always crop out parts of the image edge. You cannot correct without cropping (or creating transparent edges. You may use AI tools (outside Affinity apps) to generate fill for the transparent areas, or simply use a heavily blurred copy of the image as backfill.

Thanks for your update! Please try the following: export to PNG or TIFF open exported file Visually inspect file to be rendered correctly Print exported file from Affinity Designer If the issue persists, it is definitely not caused by affinity.