cailca Posted February 21, 2021 Share Posted February 21, 2021 Hi, I have an afdesign file I have been working on in designer for a couple of weeks. I have not opened it for 4-5 days and just gone to open it. Unfortunately every time I try to open, it comes up as corrupted and insists it is closed down. I have tried software and hardware reset and even a copy of the file, to no avail. I understand from other threads I have found, that this might be recoverable if sent to the developers, and was looking for an avenue to access this option please? I am working on a surface Pro 4 and the file is being worked on from an expansion Micro SD card I have been using for some years now. Other files from this location are working fine still. Marvel_Art_Deco_Prints.afdesign Quote Link to comment Share on other sites More sharing options...
Old Bruce Posted February 21, 2021 Share Posted February 21, 2021 33 minutes ago, cailca said: the file is being worked on from an expansion Micro SD card I have been using for some years now. Other files from this location are working fine still. I think this may be the source of the corruption. I would suggest transferring the other files to some other disk. There are a couple of fonts listed as missing, but I doubt that is the problem. Also I have never seen this warning before. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
GaryLearnTech Posted February 21, 2021 Share Posted February 21, 2021 Curiously, the text in the alert running under Big Sur is slightly different: Poking deeper, it looks as if the error refers to a file called "pistolet-lebedeva-14-kalashnikov-concern-pl-14-lebedev-pistol.jpg", which is stored in the "Black widow" folder on your d: drive. Perhaps that's the file that is actually corrupt? Check that one out in isolation. Perhaps it's been renamed or moved? If it's corrupt, can you replace it? I don't know how tightly these things are linked inside the parent file, but perhaps any similar jpg - with an identical name - at the path location might save your project, with just a little reworking of the pistol element. Quote —— Gary —— Photo/Designer/Publisher: Affinity Store, v2.5.n release (and, since I have the space, the last v1 versions too). Mac mini (M1, 2020), 16GB/2TB, macOS Sonoma iPad Pro (M4) 13", 1TB, Apple Pencil Pro, iPadOS 17.6.1 MacBook Pro (Intel), macOS Sonoma Windows 10 via VMware Fusion Link to comment Share on other sites More sharing options...
carl123 Posted February 22, 2021 Share Posted February 22, 2021 See if the attached recovered file opens for you (I assume you are using version 1.9 and not 1.8) When I have more time, I may try to narrow down exactly what was wrong 17 hours ago, cailca said: the file is being worked on from an expansion Micro SD card STOP THAT NOW Only work on files that are on your internal drive to avoid file corruption - you can archive files to other drives after you are done working on them Stupid forum software is not allowing me to attach a file (error 200) So, I have posted a Wetransfer link instead - you can download the file from there for up to 7 days from now WeTransfer link removed - see next post Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
carl123 Posted February 22, 2021 Share Posted February 22, 2021 Ok, here is a deeper diagnosed file (ignore the reference to a WeTransfer link above) The Daub Paper 05 layer was causing problems, deleting just that layer seems to fix the file File attached marvel-recovered.afdesign cailca 1 Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
cailca Posted February 23, 2021 Author Share Posted February 23, 2021 On 2/22/2021 at 10:29 AM, carl123 said: Ok, here is a deeper diagnosed file (ignore the reference to a WeTransfer link above) The Daub Paper 05 layer was causing problems, deleting just that layer seems to fix the file File attached marvel-recovered.afdesign 69.2 MB · 2 downloads Thanks very much for all suggestions, but this has done the trick, ty very much. I will adopt the working practice you suggested about file storage also. Out of interest how did you access the file to delete that layer? I could not do anything with it due to the immediate close prompt. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.