bladele Posted March 21, 2022 Share Posted March 21, 2022 I have never had an issue with the program before. My computer is an M1 Mac mini running MacOS 12.3 and the file I am working with has multiple artboards that would usually export to a pdf with multiple pages. These are my settins and I have attached the file below. When I select export the window closes but nothing happens. I have done a complete shut down and restart but nothing I am doing is working. Please help. . StayFoggy_logos.afdesign Quote Link to comment Share on other sites More sharing options...
LondonSquirrel Posted March 21, 2022 Share Posted March 21, 2022 I think you may have hit upon a bug. If you remove this item (just delete it) the file exports. But I don't know why it breaks. If I copy it to a new document, that will also not export. Instead it locks up AD such that I have to kill the process (can't quit). Why is it a bug (in my view)? A curve should not cause a lock up like this. bladele 1 Quote Link to comment Share on other sites More sharing options...
Pšenda Posted March 21, 2022 Share Posted March 21, 2022 (edited) 1 hour ago, LondonSquirrel said: Instead it locks up AD such that I have to kill the process (can't quit). Interestingly, the application will not be completely blocked, but some functions will be retained - for example, group collapse / expand, double click to layer thumbnail, tool selection, close file, ... P.S. The fact is that this layer/curve has an insane number of nodes. Edited March 21, 2022 by Pšenda Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.3.1.2217 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.2506. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.2506. 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 More sharing options...
LondonSquirrel Posted March 21, 2022 Share Posted March 21, 2022 8 minutes ago, Pšenda said: Interestingly, the application will not be completely blocked, but some functions will be retained - for example, group collapse / expand, double click to layer thumbnail, tool selection, close file, ... Yes I noticed that some things work - I spent a few minutes experimenting. It also locks up 1 CPU at 100% (give or take 2%) during the export stage. Quote Link to comment Share on other sites More sharing options...
Staff Callum Posted March 22, 2022 Staff Share Posted March 22, 2022 I'd imagine this is being caused by the large number of nodes in the curve I'm not sure if this is something we can really fix however I have logged this with our developers to be investigated as the app should just lock up like this. Thanks C Quote Please tag me using @ in your reply so I can be sure to respond ASAP. Link to comment Share on other sites More sharing options...
LondonSquirrel Posted March 22, 2022 Share Posted March 22, 2022 25 minutes ago, Callum said: the large number of nodes in the curve That would be my guess (and @Pšenda also mentioned the same). I would still class this as a bug, because AD should not be able to display/create/import (however this curve got there) something on screen but then not be able to export it. If it is a limitation which won't be fixed, that's fine. In which case it should be mentioned as a limitation somewhere. I wonder how many nodes there are here... Quote Link to comment Share on other sites More sharing options...
Pšenda Posted March 22, 2022 Share Posted March 22, 2022 4 hours ago, LondonSquirrel said: I wonder how many nodes there are here... It would also be interesting to see how these curves were created. Certain parts are perfectly fine, and then it suddenly goes crazy. This could be particularly interesting for the OP to know how to create these "cleaner" (without balast nodes) curves so that they can then be exported without any problems. Unfortunately, Affinity does not yet allow you to optimize the curves to get rid of redundant nodes - this would be a very nice and beneficial feature. Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.3.1.2217 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.2506. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.2506. 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 More sharing options...
R C-R Posted March 22, 2022 Share Posted March 22, 2022 9 hours ago, Callum said: I'd imagine this is being caused by the large number of nodes in the curve... There is something that AD definitely does not like about that curve! I tried copying it to the clipboard, using Layer > Geometry > Separate Curves to see what the individual curves looked like. It did that without delay or hanging but when I tried to save it to the desktop it would not actually save it, even though I could give it a name, click Save & return to the edit window. Weirder still, "Save" continued to be an option (not greyed out) in the AD File menu, it remained labeled as "untitled" in the toolbar, & when I tried to quit AD, it kept asking if I wanted to save it. I eventually had to force quit AD to get things back to normal. Quote All 3 1.10.8, & all 3 V23.0 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 Affinity Photo 1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
LondonSquirrel Posted March 23, 2022 Share Posted March 23, 2022 Curves 1,2,3,4, and 5 can be exported. Curve 6 seems to be the problem. I can save that to a new afdesign file. After several minutes of 100% cpu load on one core I can export this to an eps file. I'll take a look tomorrow at this file out of curiosity. It's attached if you want to take a look in the mean time. Of course, I am aware this is not the whole file. But this is the part which seems to have the problem. broken-file-curve6.eps 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.