Search the Community

I just like to report an event which may point to a problem in Affinity Publisher version 1.8.5. My environment: Windows 10 Version 2004 (Build 19041.450), 16GByte RAM Affinity Publisher version 1.8.5, afpub-document 136 pages, more than 200 images, size 54 Mbyte I have been working for weeks with this document without any problems. Today I have had a strange occurrence which happened the first time after I had updated Publisher to version 1.8.5. Five images, not embeddet but linked, lost their resolution and changed to a very coarse pixeled structure. This looks similar to the way picures gradually get more and more detailed when the document ist loading. This process sometimes takes a seconnd or two, but then the image is perfect. In this case, however, the process of refinement does not take place. When I exported the document to a PDF-file the resolution of the pictures remained the same – unusable. I replaced all these images with the "replace picture" function, using exactly the same path as before, and they appeared correct again. Then I exported the document to a PDF-X/1-a/2003 CYMK file. After that I noticed some other pictures had been altered in the same way as described above. Again I corrected all images by replacing them with the same image file and exported this again to a PDF file. This time no more images where messed up and I could not reproduce this problem In addition I feel that loading of images seems to take very much longer than it used to do in Publisher version 1.8.4. With kind Regards, Worker Update August, 28th 2020: Today I did some more testing on this problem. It seems to me that intermittently Affinity Publisher, while loading this document, gets stuck in bringing some of the images to their full resolution. In the past I never had this problem. It may be pure coincidence but these events only happen since I have updated to Publisher version 1.8.5 yesterday. This document has more than 200 images on 136 pages. I found that when I close Publisher without changing anything and then reopen it, sometimes all images are displayed correctly, sometimes one or more other images are corrupted in the way shown in the example above. For me this is an annoying problem because after opening the document I need to check all images for their correct resolution. If I miss one, it will also be shown corrupted in the exported PDF-file. Since I can really not see what I could be doing wrong in this case, I need urgently some help on this problem. Thank you very much for any hints or help, Worker

I've created a DIN A4 booklet about 80 pages. Before the last two updates the app works good and fast. Now when I open my file, the memory and CPU explode and the app or the whole computer works really slow. After a few minutes the CPU works normaly but the Memory is still high used. Sometimes the tool crashes when loading the file. Is that a known problem? Any Tips for a short-term solution?

Hello Serif, I'm working on layout magazine. At first time when I created the layout it is still fine but it getting slowly when i keep increase the pages and import images to document. The problem I meet is Affinity Publisher software work slowly, sometimes freeze, and slow loading when saving and exporting. Maybe you can check the file that I attached below. Hardware I use: Macbook Pro Mid 2012, Intel Core i5, Ram 4GB, using Wacom pen tablet. Thank You Master_Layout_Book_ANGIN_revisi.afpub

I think maybe someone should look at my very large document. I have noticed, since the final version of AFPUB (and not before), that there is a huge delay in opening the document and getting it ready to actually edit. First there is just the loading percentage - that takes about 2-3 minutes or so. Then, if I try to open the Resource Manager right after the document is loaded, there is a 45 second delay while that populates with items. Then comes the silent delay. That goes through some 4-5 minutes or so of who knows? I can try to "do" something like show the text flow. That shows up about 2 minutes later, then I click a text box and nothing - it doesn't get selected. Waiting another 3-4 minutes, finally that text box gets highlighted. Similar delays happen when trying to select other objects to edit. All the while, I'm watching the "Force Quit" list and the Activity Monitor list and AFPUB goes into and out of "Not Responding" status about 2 times during the l-o-n-g wait and also showing %CPU upwards of 450 and back down to nominal 20-60%. It's AFPUB 1.7.1, OS X 10.13.6. computer memory 48GB, AFPUB using 23.74GB or so, plenty of local disk space 570GB available out of 1TB. This problem is repeatable, just have to close the document and open it again to see the delays. Eventually, some 5 or so minutes later - AFPUB finally gives me control. But the "not responding" status is worrisome and may indicate something that's not quite right. Let me know if I should upload the file - I think you may find some interesting "stuff" going on in the background. Thanks!

Affinity staring getting sluggish yesterday when selecting text or element boxes. The time between selection and activation can be 2 or 3 seconds. It just showed up with no reason. Nothing new was added to the system (which is all SSD). Rebooting provides no relief. The Affinity file size is only 241 mb so that shouldn't be a problem. I also have open MS Word (copy and pasting to Affinity). I occasionally open Photoshop CC 2019 and ON1 to work on a photo to be placed but they are closed when the processing is done and I have been doing this for the last 10 days without any negative effect. Memory use according to Task Manager seems fine (8 gb on system). I really like Affinity and I'm testing it by complying a 100 page cookbook for someone. Final size is an estimated 110 pages and I'm about half-way so more potential sluggishness is a concern. Anyone else seeing this?

since the update, every time a file i was previously working on (300+ page graphic novel) the program gets extremely sluggish, freezes, fails to respond and has crashed twice. i always end up having to end it through task manager as it begins to slow the rest of my computer. i have space on memory and plenty of processing power. and the file/program was working perfectly well before the update.