Affinity 1.7.3 File Corruption PLEASE HELP!

[ltew]

Hello,

 

I have been using Affinity Photo editing software for the visual promo of my upcoming EP. I am working from a 5 yr old Macbook Pro, editing files that I store on an external portable hard drive. Last night I was working on the album cover and during my editing, my laptop gave me a warning that the storage on it was full. Because of this, Affinity was running slow so I cleared out some space on my laptop and things began running smoothly again. I completed my work for the night, saved the file (I did not export this new version), exited the program, and ejected my external drive. 

 

This morning I woke up and opened affinity without plugging my hard drive in (I usually plug it in first and then open the program so that way it opens the last file I was working on immediately). 

Initially, Affinity opened a random old file I was working on without the drive so I plugged it in and pretty sure I opened the album cover file via the "Recently Opened" tab and my image showed up like I've never seen it before [see screenshot] 

 

I was really freaked out so I immediately restarted my computer, but while closing out my programs I accidentally saved this new glitched out version. Once I restarted my laptop and the program I opened it up and it was still the same.

 As you can see in the screenshot I attached, there is a percentage (27.6%) at the top of the frame. You can also see that the layers I've created in this photo are not properly loading. 

Is this because there is a glitch in the process of opening this file? If this is what my file looks like now, can I revert to a past version/open a recovery file? I'm not sure how relevant all this information is to my situation, but I thought I should include everything that may be a contributing factor.

 

I appreciate ur help in advance and really hope we can figure this out.

[Chris B]

Hey ltew, welcome to the Affinity Forums.

Sorry to hear this. I've made you a private Dropbox folder so you can send me the file so we can look into this for you. Only QA and Development can see the folder and will be removed once investigated.

It might be worth you toggling Metal compute to see if anything changes (Preferences > Performance). Do the glitches move around at different zoom levels?

[ltew]

7 hours ago, Chris B said:

Hey ltew, welcome to the Affinity Forums.

Sorry to hear this. I've made you a private Dropbox folder so you can send me the file so we can look into this for you. Only QA and Development can see the folder and will be removed once investigated.

It might be worth you toggling Metal compute to see if anything changes (Preferences > Performance). Do the glitches move around at different zoom levels?

Hello,

Thank you so much for your help! I uploaded the afphoto file (as well as what the image looks like when its exported as a jpg) to the dropbox you linked. 

Tried toggling the Metal compute and unfortunately nothing changed

 The glitches don't necessarily move around when I zoom, but they do temporarily disappear and reappear within the span of 1-2 seconds

[Chris B]

Hey ltew,

Thanks for uploading the files. 

I've just spent a bit of time deleting, exporting and generally poking this file but nothing is jumping out. It is broken on Windows and macOS with and without metal. I can't seen to find any NaN pixels so I'm not sure what has happened. 

I have escalated this to the development team to see if it can be fixed or at least find out what has happened.

[ltew]

2 hours ago, Chris B said:

Hey ltew,

Thanks for uploading the files. 

I've just spent a bit of time deleting, exporting and generally poking this file but nothing is jumping out. It is broken on Windows and macOS with and without metal. I can't seen to find any NaN pixels so I'm not sure what has happened. 

I have escalated this to the development team to see if it can be fixed or at least find out what has happened.

Chris,

Damn that is really a shame! I really appreciate u taking the time to help, lets hope the development team has some insights on this 😅 Will any updates they have be posted on this thread?

[Chris B]

Hey ltew,

Thanks for the file.

Unfortunately the file is not recoverable. One of the developers has attempted to debug it and we cannot find the corruption. If perhaps you have a slightly older backup of the file, it might help us further.

I'm not entirely sure how this has happened either.

I tried copy/pasting the layers to a new doc and got different results. See link:
https://www.dropbox.com/s/8sv1yj0u2gqaxpr/ltew.afphoto?dl=0

[Chris B]

Yes if I hear anything I will update you. There are hopefully some improvements going into the next big update to help us either prevent or diagnose this.

Occasionally we see corruption like this but it's so rare and nobody internally has ever been able to reproduce it. 

[ltew]

3 hours ago, Chris B said:

Hey ltew,

Thanks for the file.

Unfortunately the file is not recoverable. One of the developers has attempted to debug it and we cannot find the corruption. If perhaps you have a slightly older backup of the file, it might help us further.

I'm not entirely sure how this has happened either.

I tried copy/pasting the layers to a new doc and got different results. See link:
https://www.dropbox.com/s/8sv1yj0u2gqaxpr/ltew.afphoto?dl=0

Just added 3 older .afphoto files from the same project, let me know if that brings any new information or if I can provide you with any other files/info/etc.

In the mean time I think the best way for me to reconstruct this image is through layering different exports of these older versions. I know I'm losing some resolution through this process, so if you know of any smarter, less destructive ways of going about this I am all ears 😊👂

 

[Chris B]

Thanks ltew,

I've asked the developer who assisted me earlier if the older files would help. Just waiting to hear back

Are the older exports JPEG or PNG? 

[ltew]

1 hour ago, Chris B said:

Thanks ltew,

I've asked the developer who assisted me earlier if the older files would help. Just waiting to hear back

Are the older exports JPEG or PNG? 

Thank you! the older exports of this project have all been jpg

[Chris B]

I've passed the additional files over to development. We're going to see if there was any corruption in the older files to see if we can find the cause.