Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hey @Pauls, any word on this? I keep having the same issue with this file. Every once in a while it gets corrupted when I update it. I have a few workarounds (saving different versions, etc.) but they aren't ideal Thanks mate,
  2. Hey @Pauls, that upload takes forever and keeps running into an error. Can I WeTransfer it somewhere?
  3. Here is a crash report after I replaced an image, which often corrupts the file. AFPUB Crash Report 1:10:22.txt
  4. Are your returns line breaks or paragraph breaks? You can replace breaks without using Regex by just using the find options.
  5. I can't find where to turn on the "Event Viewer", but I'll let you know what it says when I do. I'll run a test tonight and let you know the results.
  6. @Paul Martin Here is an example: Screen Recording 2022-01-06 at 2.19.42 PM.mov
  7. There isn't an eyedropper function, as far as I know. You have to select the text that is the style you want, then Edit>Copy, then Edit>Paste Style.
  8. So @Dan C, I can 100% confirm that the corruption error occurs when saving immediately after replacing an image within a frame via the "Replace Image" button on the context toolbar. I've replicated this several times, all to either one of two outcomes. Either the file is immediately corrupted, or the "Access to the file location was lost" error appears, after which the file cannot be opened due to corruption.
  9. At this point I'm just logging for posterity. Another strange related behavior: I replaced an image inside a Picture Frame, then saved the file. The saving process was interrupted by the "access to file was lost" message. The document closed. Then I tried to reopen it and I got the message: "This file is open in another application." What the hell?
  10. A small update. I have moved all linked files to the Local Disc, but occasionally the file gets corrupted anyway. So that rules out 'server fluctuation.' Currently I have to save a new version of the file every few edits to protect against this. Another odd happening: copying layers from the main project into a new file sometimes results in both files either "Failing to read file location" or getting corrupted. ____________________ Can I send my project file to a developer to see if they can decipher why this might be happening? I should warn that the file contains some ~1,700 linked images.
  11. @Dan C, I suspect the cause has something to do with linked images that are located on a Network server. If the connection to the server "fluctuates" (if that's the word), I imagine Affinity cannot find the file, then the project gets corrupted. Hope this helps.
  12. @Old Bruce, I should clarify, they aren't Documents, but either .jpgs or .pngs. I am saving them in a subfolder ("Links") on the Local Disc.
  13. iMac (Retina 5K, 27-inch, Late 2014) macOS Big Sur 11.6 (20G165) Processor 3.5 GHz Quad-Core Intel Core i5 Graphics AMD Radeon R9 M290X 2 GB ------------ The corruption has occurred on multiple files (the same project, modified and saved to new versions). As far as I can tell, the corruption occurs either when I am saving the file, or when linking resources through the Resources Manager. The file is somewhat large (228mb), and my computer lags noticeable while working on it. A parallel error, "Access to file was lost", has occurred multiple times as well, however I'm not sure if they are related. Thank you, and let me know if you need any more information.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.