NotMyFault

To reduce the risk, I suggest to: rasterize and trim layers after clipping / masking the relevant part - if only a much smaller part is needed. Check if you have large out-of canvas areas. Try to get rid of them (better avoid creating them in the first place) Be careful with inherent or explicit mask layers. Keep their size in sync with parent layer. To not rotate or stretch them independent from parent. This can happen by move tool, or even inside the layer if you have a selection active and use the move tool to rotate/stretch the selected area. be carefull when having very large layers with a combination of rotating layer, then using brush tools on that layer or a related mask layer. This edit sequence leads to inflated layer size in out-of-canvas areas. I filed multiple bug reports and feature requests to get the Affinty apps behave more user friendly in such situations.

I see some similarities to an older issue „Spooky“ vs your file, a combination of: large canvas many extremely large out of canvas areas, some rotated mask layers scaled or rotated, no longer matching size of parent layer the file seems to be created „very creative“, having many superfluous areas, either hidden layers, masked out, or outside visible canvas, and 1/2 GB file size. It should work in theory without issues, but this edit style has an elevated risk of getting damaged layers at some point as Affinity might run into Memory issues during edits, without clear error message or messages get ignored and the visible only later in the process.

It seems the bottom most pixel layer is corrupted / damaged. It shows black areas in alpha or color channels even when all other layers are deactivated. I would start over again in a new document. you could give it a try and only replace the image / pixel layers with fresh copies, but if one layer is damaged the risk is too high the whole document get damaged: create a new document copy all layers except the damaged one from the old file insert a fresh copy from source file of the damaged layer redo lost editing steps

Sorry to spoil the fun, but the videos show only content created by non-Affinity apps. All post in the forum should focus on activities in Affinity apps. And adding a simple levels adjustment or similar in Photo is to little to make it relevant.

Im a bit confused by the post. In my experiments, you can fill a empty pixel layer with transparent canvas in Designer using fill tool in Pixel Persona. So why add a fill layer? Do you use a Pen to start the fill? This is extremely unreliable as in 99% Affinity app wrongly detect a very small pen stroke instead of single touch. The stroke will change whatever slider has focus, often radius or tolerance in case of fill tool, but it will not fill. This is reported as bug, but unfixed.

Just found a good article explaining this in epic detail, including how to reliably choose the actual app version (e.g. beta or retail, V1 or V2): https://eclecticlight.co/2024/04/10/how-macos-opens-a-file-in-the-correct-app/

If you want to crop a layer in Photo: use a rectangle shape to define the crop area, either as mask (nested) or clipping path (used as parent). You can use this layers, it is non-destructive If you want do destructively remove the cropped area, rasterize and trim layer. It will bake in the current document DPI, too.

Thanks for the additional clarification. I will check again tomorrow, PC is in sleep mode already.

When you cycle the selection box it will 100% produce the symptoms you described. The anchor points will reset to 0degree even if layer is rotated, just press the . Key again, it will cycle. If nothing happens it was not cycled. Otherwise the layer selection box handles and rotation value in transform panel will change.

And during my tries the export UI rounds up, too. So please give the full example.

Screenshots of the exact settings you made would really help. I dont know what you mean by "resize tool". The UI allows to enter own size, and you can lock/unlock apsect ratio, and it may depend on the actual size before and the scaling factor.

We really need a file where this occours. Cannot reproduce from scratch. Whicht settings do you have active for the move tool (e.g. transfor seperately)? Did you cycle bounding box (by accidentially press period key ".")? This can cause the behavior if box is rotated 180 degree and bounding box is cycled.

ok, I used the place tool, you used the rectangular image frame. With image frame and only after adding an image, issue is reproducible on Mac and Win.

The file that was created during the screen recording, ideally saved with history. Your App settings might differ in relevant aspects from my settings, and the file hopefully has all settings used "baked in", even if not visible in recording.

Cannot reproduce. May depend on UI settings (number of pixel). For me if i use Document->Setup and reuce 111px to 111px / 2 the new size is exactly 55.5px. Yes, you can have documents with fractional pixel size. Activating rulers confirms this. If you export to a pixel format, Affinity must round to full px. So no bug (for export) in my view, maybe an diffrent UI issue, but only if yot set decimal digits to 0 (which is default). Unfortunately even switching to pixel view mode cuts off 1/2 px.

Cannot reproduce ond Mac and Win. Can you upload the actual file?

Welcome to the forum, @Hindsight. The task you are facing is not easy to achieve, and you already hit several limitations of Affinity software which require workarounds. In case you have a live stack group, opacity / layer transparency does work differently, becoming binary on/off. So you need to remove all layers from the stack first if you want to work with layer transparency. This is an intended functionality (which i personally don‘t like). For such extreme variations of lightness the HDR persona comes to its limits. Remember that is primarily intended to reduce strong contrasts and map all color values into the SDR (standard dynamic range). First you really work with source files of 16 or 32 bit color depth. Then stack the images and stay in RGB/32 color depth for all editing (except exporting, see below), and enable „ICC managed“ in 32-bit preview. It you’ll really help if you have a HDR capable GPU and display (supporting e.g. 1000nits max brightness and EDR/HDR with 32 bit input signals). You might need to hand-select the best fitting source files (and exclude some who spoil the result). Sometimes you may get better result manually adjusting the brightness with help of curves, levels, or other adjustments. If you want to finally export to jpeg (for social media), you then need a second HDR processing to reduce the dynamic range to 8 bit. There were some issues exporting directly from RGB/32 to RGB/8, so i prefer to save a copy of the file, do the final work ind tone map persona to reduce DR to SDR. Save again a copy, then open that file, convert dolor format to RGB/16 or RGB/8, and export the JPG (or JPGXL etc). It takes a lot of practice and expermientation to achieve good results.

It is actually clipped by the artboard, and this is core functionality that child layers get clipped to the parent layer. No bug.

The layer thumbnail look strange (full white). Is this a regular bitmap image with 100% opacity? Which color format, RGB or GREY?

Fascinating 🧐 Any chance you can upload the actual file?

See And

Use stroke alignment „center“ instead of „outside“.

I can’t imagine this can be done in any Affinity app currently. i would probably try to export as SVG and use any suitable script languages or text editor to change the color codes in a fixed place of that file and save the modified copy of the file under the name of the color. You may create a vector layer and suitable blend mode (like color).

The easiest way to rotate the content inside a document for export is: add an artboard. All content is automatically moved inside Rotate the artboard (move tool / transform panel) Export the artboard only (not full document). The artboard should be active layer, and change in export UI form „whole document“ to „Artboard“