Autosave recovery files ignored on startup, Publisher 2.50/2.5.2 Beta

[Louisk]

I'm experiencing multiple daily crashes as outlined in this forum post

Alongside this, my autosave containing unsaved work is not being loaded after the crash, and is instead deleted when the original file is opened. I copied the .autosave file to avoid it being deleted and the work lost, but Affinity is not loading it.

This reproduces each time I try to load the autosave, including when killing the Publisher process with unsaved changes to try to induce a file recovery.

Windows 10, OpenCL is off.

[walt.farrell]

15 minutes ago, Louisk said:

This reproduces each time I try to load the autosave,

Are you getting the prompt that an Autosave file exists, and then telling the application to use it?

Or are you trying to Open the Autosave file manually (which is not something that you should generally do)?

[Louisk]

Two things I guess - the app crashes, and each time it crashes, no autosave prompt appears despite an autosave file existing.

Secondly, I copied the .autosave file after losing work, and the original file it was saved in relation to hasn't changed, but nothing I do can make Affinity try to load the .autosave file

[walt.farrell]

Thanks.

Just to make sure you're expecting the right behavior: For a named file that has been previously saved, you won't get the prompt to use the Autosave file until you specifically try to re-Open the original file.

If you re-Open the original file, and don't get the prompt, that might indicate that the Autosave file you see isn't for that file.

You can try renaming the Autosave file so it has a file extension of .afpub, and then see if you can Open it manually. Sometimes (though rarely) that will work.

[Louisk]

Thanks, yeah, I have indeed been trying to re-open the original file. The autosave is def for that file as I've only been working on one file this week.

I tried the renaming route, though the autosave is only 230 MB compared to 700+ for the original - it complains "the file is a linked file, but the parent couldn't be found". The original hasn't been changed since this autosave was created, and if I edit the .autosave file with Notepad++ I see it gives a file path directly and correctly to my original file. 

Anyone know if there are known issues working with Onedrive? That's the only confounding factor I can think of.

[walt.farrell]

9 minutes ago, Louisk said:

Anyone know if there are known issues working with Onedrive?

There are issues working with any Cloud service, and sometimes with USB or network-attached drives.

The best recommendation is to work with files saved on local, internal disks.

But if you're going to work with OneDrive, I would configure it to keep all your Affinity files available for offline use, so they remain completely on your machine.