Jump to content
You must now use your email address to sign in [click for more info] ×

Affinity Designer needs to fix it's autorecovery and autosaving


Recommended Posts

I feel like Affinity really needs to improve their auto-recovery and autosaving into their programs. I can rely on almost every other program to open up a file after a crash or recover lost work but not Affinity designer. Application or computer crash after you haven't saved in a while? welp, that's 3 hours of work you can't get back. I've had multiple instances where either the app or my computer has crashed and there isn't even a hint at some kind of 'application didn't close properly would you like to open this back up'  it's just straight into the opening screen like nothing happened. Now don't get me wrong I love Affinity's software I think it's miles ahead of the competition, but even Adobe with their poor optimization and buggy apps can figure out how to autosave and recover lost work if something goes wrong. This needs to be fixed, is anyone else experiencing this?

Link to comment
Share on other sites

24 minutes ago, odoug04 said:

Application or computer crash after you haven't saved in a while? well, that's 3 hours of work you can't get back.

Not doing a "save" in 3 hours of work is a fault of the user not the programmers.

27 minutes ago, odoug04 said:

 This needs to be fixed, is anyone else experiencing this? 

No, not if they understand the need to periodically save their work and not rely on some computer code to get them out of trouble when they fail to do so. 

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

20 minutes ago, carl123 said:

Not doing a "save" in 3 hours of work is a fault of the user not the programmers.

No, not if they understand the need to periodically save their work and not rely on some computer code to get them out of trouble when they fail to do so. 

I understand that people should not rely on safety systems like this and I was merely just giving an example however that's a bit like saying cars shouldn't have reverse sensors because drivers know they're not supposed to crash into things.

Link to comment
Share on other sites

4 minutes ago, odoug04 said:

however that's a bit like saying cars shouldn't have reverse sensors because drivers know they're not supposed to crash into things. 

Cars have airbags to protect you in the event of a crash but only a fool would not try to avoid a crash in the first place

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

1 hour ago, carl123 said:

Cars have airbags to protect you in the event of a crash but only a fool would not try to avoid a crash in the first place

only trying to point out that I think Affinity designer has faulty 'seatbelts' and it would save a lot of headaches if they were fixed 

Link to comment
Share on other sites

5 hours ago, odoug04 said:

is anyone else experiencing this?

No, since I started working on the PC (about 30 years) I have created a reflex - squeezing Ctrl + S on every occasion.

Affinity has no "autosave" mechanism, it only has autorecovery. This saves only the increment that was created/done from the saved file, compared to saving the entire work. The autorecovery file therefore requires a complete previous saved file, which can sometimes be a problem (if it be stored for example on an external / network drive). 

I think that Autosave function would be useful.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

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.