Jump to content

Recommended Posts

Posted

I have come to edit a file today and I can no longer save anything. This is very concerning as I have been working on a project for several weeks and is ready to deliver to a client.

I also tried creating a new file and still have the same problem. I am worried about opening my file now incase I have corrupted/lost all my work.

Running designer V2 Latest version

Mac OS 11.4 Bug Sur

Screenshot (attached below) tells me to report to development team [m07]

 

affinity file.jpg

  • 2 weeks later...
  • Staff
Posted

Hi @Klairand Welcome to the Forums,

Could you upload your main file to our Dropbox here and i'll see if i get the same error when saving it.  If you can give me as much information about your workflow leading up to that error, that would be very helpful and i'll pass it on to the Developers.

With the new file you created, was that just a blank document?

Posted

Why does Affinity continue having issues using cloud, network or USB drives? This is certainly not a cutting edge feature like the new, super-duper important AI object selection feature…

Every other app can handle working with non-local files. This issue has been reported for YEARS! Do you guys plan on fixing this or is playing Russian Roulette a “feature” of the Affinity Suite? If so it could be listed as a gamified feature:

“Included with the of the purchase the Affinity Suite is a bonus, adrenaline-pumping feature, RRS: Russian Roulette Save! Will your files be saved properly? No one really knows?! Find out every time you reopen your file!”

Nothing elicits trust while working with “professional” software as much as not knowing whether files will be corrupted when Saving based upon the files’ location…. 

Incoming useless PR statement: ”We have logged the issue with development”

FOR HOW MANY YEARS DO PEOPLE HAVE TO LOSE HOURS AND HOURS OF WORK BECAUSE OF A STUPID BUG LIKE THIS? HOW ABOUT YOU STOP ADDING NEWFANGLED FEATURES AND FiX THE BASICS, LIKE RELIABLY SAVING A FILE?! 🤦‍♂️ 

2021 16” Macbook Pro w/ M1 Max 10c cpu /24c gpu, 32 GB RAM, 1TB SSD, macOS Sequoia 15.1

2018 11" iPad Pro w/ A12X cpu/gpu, 256 GB, iPadOS 18.1

Posted
3 hours ago, stokerg said:

Hi @Klairand Welcome to the Forums,

Could you upload your main file to our Dropbox here and i'll see if i get the same error when saving it.  If you can give me as much information about your workflow leading up to that error, that would be very helpful and i'll pass it on to the Developers.

With the new file you created, was that just a blank document?

I have added the file to the dropbox. In regards to workflow I don't recall what I was doing at the time of the error, aside from making minor changes/edits as the file was almost complete. The file was being saved locally on my mac hard drive and not the cloud or external device. The file itself works on the ipad version, I've been using Affinity on my iPad since v1 (and now v2) to create vector illustrations without issue, and decided to trial the desktop version to give me more flexibility. I've been using the desktop version for around a month and in that time I frequently got the 'open recovery file' bug and I have had one file become corrupted. I had been working on this particular file for a few weeks without issue until this error occurred.

For this error, I cannot save any current files, neither can I save any newly created files, I have tried both blank documents and ones with simple elements and neither will save. They will however, export to other file types, just will not save as an .afdesign file. I have uninstalled and re-installed the program but the problem still persists.

I am running an older mac with OS Big Sur, 2017 quad core i5 16 GB 2400 MHz DDR4 which your site states will support the software, but perhaps it is becoming obsolete with current updates? Only developers can tell me if that is the case. Like I say, there was nothing to pinpoint any action to cause the error, no crashes, no (known)changes to my computer setup.

Posted

Here to report I'm having the same issue (Different message than OP though). If I try to save the file with a new name, I then seem to get corrupt files. I get a message that talks about legacy compatibility (and can't open the file). Also on Mac OS Sonoma 14.3 Running Designer v2.5.6.

Screenshot 2024-12-10 at 8.55.33 AM.png

Screenshot 2024-12-10 at 9.12.21 AM.png

Screenshot 2024-12-10 at 9.12.27 AM.png

Apple M1 MacbookPro, Mac OS Sonoma 14.3

Posted
2 hours ago, toddlauzon said:

Here to report I'm having the same issue (Different message than OP though). If I try to save the file with a new name, I then seem to get corrupt files. I get a message that talks about legacy compatibility (and can't open the file). Also on Mac OS Sonoma 14.3 Running Designer v2.5.6.

Serif recommends saving to a folder on your internal drive that is not synced to iCloud. But you might also find that turning off Metal reduces this problem to once in a blue moon. Go to Settings > Performance and turn Hardware Acceleration off and set Display to OpenGL.

Personally, I've turned Metal off but continue to use iCloud and it's rare to have a save failure. The problem won't entirely go away but it will be reduced to a minor annoyance.

Posted
2 hours ago, MikeTO said:

Serif recommends saving to a folder on your internal drive that is not synced to iCloud. But you might also find that turning off Metal reduces this problem to once in a blue moon. Go to Settings > Performance and turn Hardware Acceleration off and set Display to OpenGL.

Personally, I've turned Metal off but continue to use iCloud and it's rare to have a save failure. The problem won't entirely go away but it will be reduced to a minor annoyance.

Thanks Mike! I was actually asking myself if saving to a cloud service would be an issue. Turning off Metal, right away! 

Apple M1 MacbookPro, Mac OS Sonoma 14.3

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.