edw3cats Posted April 2, 2024 Posted April 2, 2024 (edit) Affinity Designer 2.4.1 Replicate: 1. On an existing document with existing Image Placement Policy as Embed 2. Place image and .afdesign embeds in document, save (and close maybe) 3. Open file 4. Change File > Document Setup > Image Placement Policy to Prefer Linked 5. Save document, will cause save error (not crash) 6. Change Image Placement Policy back to Prefer Embed 7. Save document, will cause save error. Document can no longer be saved. (Edit) Close document, and reopen losing any changes made, document can be saved from that save point, but not once Image Placement Policy has been changed.
Hangman Posted April 3, 2024 Posted April 3, 2024 I'm not seeing this on macOS so it's possibly a Windows-specific issue... Where are your files located... internal Hard Drive, external Hard Drive or in the Cloud? Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
Ron P. Posted April 3, 2024 Posted April 3, 2024 I can't replicate this using Windows.. Hangman 1 Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win11 Home Version:24H2, Build: 26100.1742: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD; Wacom Intuos 3 PTZ-431W
edw3cats Posted April 3, 2024 Author Posted April 3, 2024 3 minutes ago, Ron P. said: I can't replicate this using Windows.. Yeah actually I can't replicate it either, I thought maybe the embedded images in the file system were moved or deleted, I just tried creating a new file and deleting the image. Saving is fine. Now I remember the file was originally Affinity Designer version 1 that was converted to version 2 upon opening. In that case that would be a very edge case situation.
Dan C Posted April 5, 2024 Posted April 5, 2024 Thanks for your report @edw3cats! I've tried replicating this using all V2 documents, and a V1 document converted for use in V2 and I'm equally unable to reproduce this at this time. It's certainly possible that this is an edge case relating to your original file and should hopefully not occur again - but if you do find a consistent workflow to trigger this issue, please do let us know
Recommended Posts