Jump to content


  • Content count

  • Joined

  • Last visited

  1. @Callum, how can it not be possible? Obviously autosaved, unnamed documents are stored somewhere on the local disk. Even if they are saved only as undo stacks or diffs, since we’re talking about empty files here, it should be comparatively simple to reproduce the same context as a freshly-crashed AD and trigger the auto-recovery screen. But I need to find out where the data is stored, and I’d rather not have to dtrace my way through all of Affinity Designer to find out.
  2. Thanks for the responses. The file opened, but everything was super slow, no matter if I loaded one page or all pages. This was on the most up-to-date trial version. I have since restarted AD, rebooted the computer, and bought the full version and haven’t had the problem occur again.
  3. I was using AD Trial, then bought AD Full but still had work open in the Trial, which then promptly crashed on me a day after the trial expired, taking a bunch of unnamed documents with it. Running the Trial just tells me that it’s expired, then opens the App Store. Running the Full version does not give me an option to recover the crashed (autosaved) documents. Which files do I need to move from where to where to make AD Full see them on startup and offer recovery?
  4. I’m using Affinity Designer and tried importing the Whiteframes file from https://www.google.com/design/spec/resources/layout-templates.html#layout-templates-mobile. It is a ~15 MiB Adobe Illustrator Document. Upon importing that into AD, the program hangs for seconds on end during import and rendering of the document. Eventually, I get a low-res version, then it hangs again until I either Force Quit the app or wait >30s. Moving around in the document is also slow. Brand-new rMBP 13", 16 GiB RAM, OS X 10.10.5.

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | 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.