picolo

I have had more time look at the issue while processing more files from my recent batch and I think I have a better handle on the matter now. I resized my original file from 300dpi to 96dpi and exported to a jpeg. The "Merged Visible" screen looks very similar to the 96dpi file. So I think what happens is what AF calls the mipmap might be a shrunken file at a smaller dpi/resolution so that layer manipulations will be faster but may looks different from the actual file unless the original is also around 96dpi. Just my observation.

Personally I think the difference from the mipmap to the actual reality when viewed at less than 100% zoom is really too much (see my attachment form prior post). My habit is to zoom out to a full screen view to make a final decision if sharpening has achieved a nice result and now I know that is not indicative of what it actually is. While I understand Affinity's concern about performance, perhaps there should be a setting for users to see the actual result albeit with performance trade-off. At the least, there should be some documentation telling users about this. Strangely, this "issue" is more pronounced with poorer quality pictures, when an accurate sharpened result is more critical. Just my feedback.

If what you say is correct, Affinity should state in their literature that anything less than a 100% zoom does not represent the real result. So is it correct to say the only way to get a full screen view of a sharpen process is to do a Merged Visible and see the results from there?

Is there anywhere on AP documentation that says a live filter needs to be 100% for it to be accurate? Seems like a real flaw since not everything requires such a zoom level to work with and so people may be making adjustments based on a "misleading" view. I also think it's very common to view the overall picture at full screen size which is typically less than 100%. How then are we to actually see the whole picture at once accurately?

Aff respond.afphotoOk here it is.

All this was done before saving as a .afphoto file. Are you asking for the original Raw file?

I have to apologise for posting in the wrong section. I am a Windows user but the issue seems the same. Attached file shows a screen capture of a before and after. I have read through some of the comments regarding this issue so I ensured I tried both the forced pixel and move pixel thing as well as maintain the same DPI of 300 as per my original file. The sequence is as shown: Open file, apply two layers of Unsharp Mask then Merge Visible. I am running V1.8.5 but I have the same problem with the latest 1.9.2 as well. I run the latest version update of Win 10 Pro with AMD 3600 and Nividia 1650 Super.

I am also have this problem with merged layers looking blurred. Has anyone found any reason or rectification for this?

I also experience much of the same as those above. Using Nvidia GTX1650 Super and have plenty of system memory and disc space left. Sometimes, the cursor will be "stuck" and refuse to change when mousing over other icons, but this can be resolved by switching to another (Windows 10) virtual desktop and back. Using a Huion tablet so it may be a problem with the driver but it was a very occasional occurrence many beta iterations ago but seems to be much more often now.

Kept on clicking on link to download like usual but nothing happened until I used the "open in new tab" method. But it's super fast now, like 15 secs.

Did a reinstall and it works ok now.

I keep getting a password error message. Win 10 Pro with Windows Defender Bought from Affinity direct.

It works ok. My mistake.

When exporting to Jpeg, the "Save as" dialog box comes up instead.

Yes this is my experience too. Cheers