Neal W Posted September 5 Share Posted September 5 Currently encountering an issue with Affinity Designer where after embedding an .eps file or an .afdesign file into a document, an error stating "Could not save. Access to file has been lost." pops up when I attempt to save the document using "Ctrl+s". After this, I can no longer save the file and lose any progress since the last save. It tends not to happen if I save immediately after embedding a document, but if I embed, then edit anything before saving, the issue will often occur. Details: - Using Affinity Designer 2.5.3 - Windows 11 - Using a Lenovo laptop with a AMD Ryzen 7 5800H CPU and an RTX 3060 GPU Quote Link to comment Share on other sites More sharing options...
Staff stokerg Posted September 10 Staff Share Posted September 10 Hi @Neal Wand Welcome to the Forums, This isn't something i can replicate. Does this happen if you start a New Document, embed an afdesign or EPS file and try to save it or does it only happen when editing a Saved afdesign file and embedding files into it? If when trying editing an already saved afdesign file, where is that saved file stored? Quote Link to comment Share on other sites More sharing options...
Neal W Posted September 10 Author Share Posted September 10 Hi stokerg, Thanks for the reply. As a note, I've also experienced this with the most recent Designer version (2.5.5.2636). There's nothing particularly unique about where the .afdesign files are saved; they're either in a subfolder on the Desktop or a subfolder of Documents (neither location uses any special security permissions). Embedded files within the same folder or in a separate folder from the .afdesign file have managed to trigger this error. In attempting to replicate the error, I came up with an example that seems to be repeatable. I attached two files, one named test.afdesign and one named syringe.afdesign. test.afdesign was originally made in Designer V2. syringe.afdesign was made in Designer V1 and re-saved in V2. Place both files in the same directory, then open test. Using 'Place', import syringe and attempt to save immediately or attempt to save after some change. In either case, you should get the error that I previously described. The issue seems to be, to some extent, tied to files initially created in V1 or to V2 files containing elements that were initially made in a V1 file; when importing files of such nature into an existing V2 file, the error seems to trigger. Syringe.afdesign Test.afdesign Quote Link to comment Share on other sites More sharing options...
Hangman Posted September 12 Share Posted September 12 Hi @Neal W, I've tested your files on both Windows and Mac following your steps and haven't been able to replicate the "Could not save. Access to file has been lost." error message... Quote Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861 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 Link to comment Share on other sites More sharing options...
walt.farrell Posted September 12 Share Posted September 12 On 9/10/2024 at 5:07 PM, Neal W said: they're either in a subfolder on the Desktop or a subfolder of Documents (neither location uses any special security permissions). Do you have OneDrive or Google Drive or pCloud or any other cloud service configured to manage those folders? They are typically managed by OneDrive on Windows by default, for example. And if they are managed by a cloud service, is the service configured to migrate everything off or to leave everything "available offline"? Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
Neal W Posted September 12 Author Share Posted September 12 Thanks for the responses. To Walt's question, these files aren't managed by any cloud services. And to Hangman's response, I'm wondering then if it might be something that got messed up with my downloads of the software specifically. I might try re-installing, but this has been happening for all versions of Designer 2 I've had thus far. walt.farrell 1 Quote Link to comment Share on other sites More sharing options...
hunter_sk Posted September 12 Share Posted September 12 Tried, and saved the Test.afdesign file with embeded Syringe.afdesign file with no problem. Quote Link to comment Share on other sites More sharing options...
kenmcd Posted September 12 Share Posted September 12 On 9/5/2024 at 7:16 AM, Neal W said: Using Affinity Designer 2.5.3 What format did you install, and/or from where? From a store? Or from the downloadable file? What version of Windows 11? Are you an admin user? This sounds like one of those annoying issues from using sandboxed store apps. Quote Link to comment Share on other sites More sharing options...
Neal W Posted September 12 Author Share Posted September 12 Currently on Windows 11 Home (Version: 23H2 OS Build: 22631.4037), and I am an admin user. This occurred when using Designer 2, downloaded from the Affinity website, either as MSIX or as MSI/exe. kenmcd 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.