Pšenda

... screenshot with selected layers/object in Layers panel?

Interestingly, file corruption mostly occurs with external/network/cloud drives, when the connection to the drive can be lost. With the local disk, I only registered it here once - when disk damage was subsequently detected. How about backup/Time machine (or whatever it's called)? How about trying to restore the deleted files - due to the significantly smaller file size, the new one could be placed in a different place on the disk, and the original area would not have to be overwritten yet. P.S. you don't have to pay attention to some users and their constant complaining 🙂

Maybe that's why no one pointed out this bug - version V1.10.6 was "above schedule", and most people at that time were already using V2 🙂 I understand that this is useful for you and some very specific cases, but for common image deformations where the smoothness of the deformation is required, it is really very impractical.

No, the adjustments are made symmetrically - which I think makes sense, because otherwise a completely unnatural distortion of the image is created. I don't know what version you are using, but APhoto V1.10.5.1342 changes the position of both handles, same as V2.

I think that any final look/final zoom is completely irrelevant here. As GarryP writes, the problem is the size of the image, where its constant "centering" in a situation where adjustments are made on the edges of the image would be maddening.

But it doesn't work like that in the Win version.

Hard to advise without a file. Now I don't even know exactly what your problem is. From the first post, I had the impression that the problem is black and white export, but it is inverted than you expected. But now you're talking about color again?

Blend Mode?

Do you use an external drive or cloud folder for your work files?

https://affinity.help/designer2/English.lproj/pages/ObjectControl/selectByAttribute.html

It looks like over-illuminating nearby objects with a flash that tried in vain to illuminate even a very distant background.

V2 Ctrl+C, V1 Ctrl+V. Or V2 export to PDF, V1 Open/import PDF. P.S. Just for interest: How many years and development capacities (which will of course be missing when fixing errors - for example, slowing down the application, and implementing new functions) do you think it will take for this completely new feature, never considered by Serif? Why am I asking? From your request, I got the feeling that you would definitely need this very complicated and therefore very often unsupported feature by Serif and other companies in the next few hours/days.

And what is the resolution? - possibly a Preflight screenshot. Document to review?

You could monitor resource usage in Task Manager (memory, CPU) to see if there is a gradual increase in load. Or if it's not caused by some conflicting application that takes the resources needed for ADe. P.S. recent Win11 updates sometimes cause unwanted performance degradation.

Affinity uses a technique to speed up the display of <100% mipmaps, which causes some display distortion. It is necessary to check the quality of the image and the effect of the filters (for example, sharpening) when displaying 100% and higher.

Therefore, it is advisable to use external specialized search tools (such as Google or others) whose success rate in finding relevant results here on the forum is significantly higher. That's why v_kyr provided examples of searches using an external tool. For better readability of the command, which may also be useful to users in other situations, I repeat it here. https://www.google.com/search?q=File+Browser+for+Affinity+site:forum.affinity.serif.com https://www.google.com/search?q=DAM+site:forum.affinity.serif.com

The standard work with available memory, which is mostly done at the OS level and the application can't even affect it (and doesn't need to), is that unnecessary memory is not freed - it doesn't waste time and energy. It is released only on a new request, when the memory allocation management must be done anyway. In general, the available memory is there to store some data, even if it is not needed right now. In this situation - after closing a large document and holding a large part of memory, try to start some other application with large memory requirements (for example, open a very large document in Word, or an Internet browser with many pages, etc. Even if due to your large memory (32 GB) this can be a bit of a problem as the memory requirements will have to be really high.) Then it will be interesting to see if the allocated/held memory gets freed.

https://www.google.com/search?q=Black+CMYK+site:forum.affinity.serif.com

The fact is that I avoid the Master Page application on already prepared Pages as much as possible, because then there is a need to re-correct the content of the pages. So I assign the Master Page already when creating the Pages.

I don't understand why I would need to display different thumbnail sizes for Pages and Master Pages. I choose the size of the preview according to the need to see and distinguish the content of the page, and this need is the same for both views.

Your image has two pixel layer. This layer is not needed at all (it has no contribution in the final image), so it is possible to delete it (the file is then only 20 MB). Also, you do all the modification destructively (or rasterized at the end), so not only can't you tuned them, but you don't even know what adjustments with what parameters you did on the original image. This is not a good practice - that's why you use the native afphoto file to store "everything" you need.

For these purposes, it is not necessary to resize the source image. Using Export persona, you can export several sub-files with different resolutions and file types from the high-resolution original.

If you select the "Save History with Document" option before saving the file, you could go back.

See Split View: https://affinity.help/designer2/English.lproj/pages/GetStarted/view.html Vector graphics sometimes need to be checked to see how they will look after rasterization - for example, after exporting to a bitmap file (PNG, JPEG). You can do this either for the entire display (View Mode), or partially by dividing it into Vector/Pixel. For example: In vector display, the graphics will "always" look good, but after rasterization (due to the low resolution of the image), the text will not be readable.

https://www.google.com/search?q=wrap+image+around+bottle+site:forum.affinity.serif.com