Placed (linked) files are pixelated when AP re-opened

[Jamesx1]

The linked/placed files have an OK status, and display perfectly well. However, if I stop working in Affinity Photo and close it, next time I open it, I have to replace the linked file with the same file to get it to display properly. This is because the linked/placed files are heavily pixelated upon re-opening, until I link/replace it again. It is of course annoying to re-link all my files every time I start work.

I have a powerful new PC, W11, with resources excess to requirements (i7 14gen, 64 gb RAM, 16GG Nvidia GPU etc).

The files I am linking are other Affinity Photo files that contains a photo with RAW Layer (embedded) so it can be developed as needed.

It happens whether there are multiple linked files, or just one or two.

I would love to get this solved, as I am always re-linking/replacing the same files.

No errors are displayed.

I assume this is a bug. Everything works as expected with the linked files, except displaying properly upon re-opening the file from which they are linked. Any help is appreciated.

[carl123]

40 minutes ago, Jamesx1 said:

next time I open it, I have to replace the linked file with the same file to get it to display properly.

I can confirm the issue in the current release (and the beta)

Rather than relinking the file I can get it to update by selecting the linked layer with the Move Tool, clicking Edit Document then just closing the linked document that opens (which is a bit quicker than relinking it)

This problem sounds familiar so it may have been logged already

If not, I'm sure it will be once the support staff get around to this thread

[Jamesx1]

11 hours ago, carl123 said:

Rather than relinking the file I can get it to update by selecting the linked layer with the Move Tool, clicking Edit Document then just closing the linked document that opens (which is a bit quicker than relinking it)

Thanks for the tip, really appreciate it. Definitely faster.

[Lee D]

@Jamesx1 As @carl123 suggests this sounds familiar but I can't find the exact issue logged on our system. So I've created a new report for it, just in case. 

[Latens]

Perhaps one should ask first where the files are stored, not?
Since the affinities don't work well with external storage devices and even less with cloud services.
 

[carl123]

Just now, Circulus said:

Perhaps one should ask first where the files are stored, not?

All my testing/work is always done on local drives. Also, never use synced services

[Latens]

4 minutes ago, carl123 said:

All my testing/work is always done on local drives. Also, never use synced services

Perhaps the OP has a different answer.
But it may also be an energy saving feature on the ssd/hdd itself that may cause this.
It just seems that linkage within the affinities is not up to par.

[Jamesx1]

6 hours ago, Circulus said:

Perhaps the OP has a different answer.
But it may also be an energy saving feature on the ssd/hdd itself that may cause this.
It just seems that linkage within the affinities is not up to par.

I've been using OneDrive for the files involved. Prior to posting about this bug I also had the thought that is was a sync complication, so I changed to local storage, and the problem remained. So I went back to OneDrive so I have backups at all time. In short, storage location doesn't matter according to my testing.  

[Jamesx1]

Update:

If the linked file is already open in AP when I open the file that links to it, the issue doesn't occur. This may be a clue as to the nature of the bug.

Also, the simpler method of loading the pixelated linked file (clicking to edit it then closing it - which works for the same reason referenced in my opening sentence above) doesn't seem to work when the same file is duplicated (i.e. there are multiple instances of the same linked file). To load all of the instance, I still need to go to the Resource Manager and replace the linked file with the same one again.

[Jamesx1]

Unfortunately the Affinity 2.6 update hasn't fixed this issue.