Affinity Photo: Linked images have low resolution

[chammp]

Today I used linked images (other aphoto files) for the first time in Affinity Photo 2, and I noticed that the linked files are displayed (and also exported!) in a very low resolution. The part on the left of the red line is an linked aphoto image which is actually scaled down in the current document (right side), and one immediately sees the pixelated structure.

I'd be somewhat fine if the exported version (in this example: JPEG 100% quality, no resize) would look good, but take a look at this:

One clearly can see the blurred and even pixelated-and-then-bilinear-filtered nature of the linked file; it's also missing all its grain.

 

When I use the Resource Manager to change the linked file to an embedded one, however, the result immediately (well, that is wrong - after a zoom operation of the viewport) looks nice:

Exporting the file doesn't change anything here, it's also all good.

Now I'd understand that for performance reasons Affinity might decide to display a reduced-resolution image when I work with the file, but when rasterizing the layer, or even exporting I expect the software to use the actual full resolution of the resources. (And an option to switch to high quality linked files would also be nice...)

Any help would be appreciated, thanks,

Markus

 

[stokerg]

HI @chammpand Welcome to the Forums,

Which operating system are you running Affinity on?

Could you attach your afphoto file shown in the screenshots and the linked the afphoto file here or upload it to our Dropbox here and i'll be able to look into this.

[chammp]

Hi, thanks.

I started working on Windows, continued on Mac, and now, after several edits to both files, the problem's suddenly gone. 🤷‍♀️ It feels almost like Photo uses some pre-rendered/flattened version of the linked file and that this flattened version was somehow created using a too low resolution, and editing the source file fixed this (re-flatten or invalidation of that "virtual layer" or whatever, I can only guess).

It fixed itself now, so...