Please help me recover this file...

[SXL]

Hi please could you help me recover this important file...

I use Google Drive synced to my PC.

Affinity Designer Version 1.10.6.1665

Device name    DESKTOP-D9HP9OM
Processor    Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz   3.00 GHz
Installed RAM    32.0 GB
Device ID    37911F74-9FF0-4A57-9556-2BD4A6C55E79
Product ID    00330-71346-35407-AAOEM
System type    64-bit operating system, x64-based processor
Pen and touch    No pen or touch input is available for this display

Edition    Windows 11 Pro
Version    22H2
Installed on    ‎05/‎10/‎2022
OS build    22621.963
Experience    Windows Feature Experience Pack 1000.22638.1000.0

 

Lumiere&Co_Link_Hub_SXL.afdesign

[Michail]

6 hours ago, SXL said:

I use Google Drive synced to my PC.
Affinity Designer Version 1.10.6.1665

Welcome here to the forums 

There are reports that V2 files can no longer be opened if they are on a network drive. However, I know of no reports that this is also the case with V1 files.

[SXL]

Thank you

Its a first time occurrence. Hopefully there is a resolution.

[R C-R]

2 hours ago, Michail said:

There are reports that V2 files can no longer be opened if they are on a network drive. However, I know of no reports that this is also the case with V1 files.

But there are many reports of files being corrupted if they are opened from non-local drives & some reports that this also can happen with local folders synced to Google Drive & other cloud servers.

[Dan C]

Hi SXL, 

If you still require it we can take a look at the file, though we can't guarantee any timescale or success.

https://www.dropbox.com/request/2pof9OH6hUf2sBC5YMMU

Lee

[SXL]

Hi Lee, could we please try that again? Might it a be a version specific issue?

[Dan C]

Hi SXL, 

As mentioned above, The file has been passed to the devs, but we can't guarantee any timescale or success on file recovery i'm afraid.

Lee

[SXL]

Ah okay great, Thank you Lee. Appreciate your time.

[Dan C]

I've chased this up for you and unfortunately this file is corrupted beyond recovery.

We advise not working from files stored on Google Drive as the live syncing can cause issues like this unfortunately.

We are currently working on new ways to deal with this issue so it may be worth signing up to the beta here to follow this progress:

https://affinity.serif.com/en-gb/affinity-beta-program/

Lee

[Bad_Wolf]

I use Scirra Construct 3 (C3), where my live project files are saved in the cloud on Google Drive. C3 works entirely in the browser. However, the project you are working on is stored in memory.

Because I store my files with Google Drive, I use the following method:

1. You copy your Affinity file from the cloud to your local hard drive.
2. Open the local file with your Affinity application of choice.
3. You work and make modifications to that local file.
4. You save it to your local hard drive.
5. Close the document in your Affinity application.
6. You copy your local file to the cloud (Google Drive, Dropbox).

I think it is safe, and document corruption should not occur. The method described above differs from working directly from the cloud, which is always wrong because of network errors. I never had any file corruption problems with the way I used above. Also, in C3, I never lost any project, but as Lee mentioned, the project is saved to the cloud, and the project you are working on is stored in memory.

My knowledge about this subject is limited. Can I ask if the above method is safe, or is storing the backup files on an external SSD better?

Thank you for your help which I appreciate.

Chris

[SXL]

Hi guys, thank you for trying. Its never happened before so it's just unfortunate, I thought it might have to do with version control. Again thank you for trying. Appreciate your time.