Search the Community

Windows 11 Pro 22H2, Ryzen 7 3700X with NVIDIA GeForce RTX 2060 Super New issues 2.2: Project file sometimes silently fails to save latest session changes (do not know how to reproduce). Other people now reporting same problem on Facebook. Project file can be missing hours of work when re-opened. Running a macro instantly crashes the application (crash report uploaded, 100% reproducible). Application does not crash when applying macro actions manually. Macros created in 2.1. Blemish Removal tool when used to dab away dust spots slows down with each successive use, until eventually the application becomes unresponsive for long periods of time. Application does not crash (so far), eventually recovers, but I have always given up when the unresponsive periods become intolerable (30s to 1 min), never pushed it further (frequently reproduceable). Merge Visible sometimes produces a result that has somewhat shifted levels/color (not easily reproduceable). Workaround is to break up merge into batches of fewer layers and then merge the results. Issues 2.2 (carried over from 2.0/2.1): Blur Brush region of influence does not preview blur effect, it previews like an erase tool (reveals layer underneath or transparency grey squares) (100% reproducible). Blur Brush tool is often reluctant to make any changes or makes some small amount of change and then becomes unable to make any more changes (even at 100%) (frequently reproducible). Grid cannot be turned on (100% reproducible). Makes it difficult to snap objects. Amending a TIFF file and saving it directly (without export) severely corrupts metadata (Subject, Tags, Comments). Comments and Subject are completely replaced by seemingly random bursts of Chinese characters, long hierarchical tags and large lists of tags are truncated even though they have not exceeded any limits imposed by File Explorer or dedicated tagging applications (100% reproducible). Application repeatedly displays a reminder dialog to turn on crash reporting when launched. Apart from settings choices being repeatedly questioned, the reminder dialog frequently interrupts train of thought. If it only comes up after a failure, then this suggests there are frequent silent failures happening in the background going unnoticed.

Hey all, today I noticed this strange behaviour that I have never seen before when merging layers. I was wondering if anyone could explain this to me. I usually merge layers so that I get an exact replica of what was visible in the layers palette at that moment – taking into account transparency (or lack of it, in this case). For some reason, Merge Visible (⌥+⇧+⌘+E) above a solid layer (pixel or fill) with an Add Noise filter layer on top of it results in a layer that suddenly shows transparent areas/single pixels. I don't get it. There's no transparency before merging, at least not that I know of. Even stranger: Grouping the filter layer with the Add Noise filter layer gives a similar result – suddenly there's transparency, because the group blend mode is automatically set to »Passthrough«. Try grouping the Add Noise filter layer with the Fill Layer below it in the attached file or »Merge Visible« and hide the layers beneath it. Ideas anyone? 🤔 Merge_Visible_Transparency.mp4 Merge_Visible_Transparency.afphoto

Hello Legands, New to using Affinity Photo and have run into an issue when trying to Merge Visible layers of vector images. When i perform this action Affinity Photo seems to automatically convert the image to pixels and cause the image to become pixelated. Is this a known issue and is there a fix to prevent this from happening. I use affinity for screen printing designs so pixelation is not my friend. Thanks for any help/ advice.

I recently bought a new notebook, since the integrated graphics card of my old one was quite weak for Affinity Photo. (New Notebook: Lenovo IdeaPad 5 Pro 16ARH7, RTX 3050 Ti, AMD Ryzen 7 6800HS Creator Edition) After applying a few adjustment-layers followed by either merging visible layers or directly exporting the file as JPG, there will be a bunch of artifacts introduced. "Hardware-accelerated GPU scheduling" is turned off on Windows, as mentioned in this article. Same issue occurs on Windows 10 and 11, tested it on two different SSDs. The problem occurs not only on this very image, but when applying several adjustment-layers in general. So far, I couldn't narrow it down to one specific adjustment-layer. I never had such issues on the old device. Windows is up-to-date, notebook-drivers are up-to-date and graphics-drivers for the dedicated Nvidia as well as integrated Radeon card are updated as well. I also made sure that Affinity Photo only runs on the dedicated card for better performance. Affinity Photo Version: 1.10.5.1342 (Downloaded via Windows Store). If I missed any details, feel free to ask. Any tips and hints are highly appreciated! Thank you! DSC02209.afphoto

In Photo there's an option to merge down or merge visible for pixel layers: In Designer, there isn't: So Please add the merge down and merge visible options for pixel layers in the Photo persona for Affinity Designer. So we can merge pixel layers without two step workarounds.

I bought a gaming laptop with an Nvidia gpu to speed up my affinity work. Unfortunately it is Windows 11. My affinity version is 1.10.5.1342. When I do a Layer->Merge Visible, I get artifacts created like this: This renders my use of the new laptop for processing useless. Please help.

Hi, i would expect all tools working in RGB32 / HDR mode to deliver 32 bit color results, or at least 16 bit. It seems merge visible reduces to 8-bit color depth, which is not expected. When using RGB32 with a HDR capable display, i can positively check that 10 bit (1024) grey values are displayed. Have a look zommend in to 800% or more. Look in the area bewteen gradient and black rectangle, left from red box, between "unlimited" and "256". The gradient has 4 vertical areas: top: original below: 3 posterized boxes to 256/128/64 levels to make simulated / real banding visible. However, when you "merge visible", the merged pixel layer is ditherd and reduced to 8 bit color depth. To reproduce, you need a "real" HDR 10-bit capable display (real 10-bit, 8+2 with dithering may show wrong results). In perfomance settings, dither gradient must be un-checked. 10 bit before merge: 8 bit after merge visible: levels.afphoto

I’m doing chapters of Affinity Photo Workbook on my PC. I tried this on a personal file on iPad Pro and Merge Visible isn’t reduciing file size. I still see all the layers below the new merged layer.. I recreated the file and I checked the size by going to export before and after merging and the file size is the same. I thought it would be smaller? Is there another way to check file size? I didn’t see it in the metadata studio.

Using the Layers -> Merge Visible command, AP creates a new layer without removing the existing ones. I expect all visible layers to be merged into a one layer and then the individual visible layers be deleted. This is how basically every other application works. Is this the expected behaviour? (Merge Down works as I expect: combines two layers into one, so that only one remains.)