Robert P

I'm sure that there are a lot of ways to get round the problem, and my way of exporting to a pdf file and printing from there works for me. I just think that the Affinity team should be addressing this bug a bit more quickly!

You misunderstand what I am saying. The point I am making is that the black lines appear when I try to print from the afdesigner file. The only way that I can print without the unwanted black lines is by exporting the file to PDF and then printing. Why should I have to do that? I should be able to print directly from Designer itself without going to that trouble

This has happened since Designer V2 was released. There are constantly artifacts appearing in printing - generally lines denoting some of the borders of groups. You can see from the attached file artifacts.pdfartifacts.pdf that there are two black lines appear in the print and they should not be there. The only way that I can avoid the problem is by exporting the file to pdf and printing from there. The attached file Lizzie2023 is what it should look like. I am using Designer 2.1.1 on fully up to date Windows 11 and I have tried GPU acceleration both on and off. I have to say that I am getting a bit sick of the fact that this fault has still not been address despite the fact that I reported it way back at the start of V2! I certainly won't be upgrading the other two programs in the suite! Lizzie 2023.afdesign artifacts.pdf

Just tried that. The problem is still there. RAM usage can increase by the size of the file, merely by scrolling through the book! It really is a disaster! I won't be upgrading.

In Publisher V1 I know that there was a fault where the program kept grabbing more and more RAM and the only solution was to close the app and reopen it on a very regular and frequent basis. Has this problem been resolved with V2?

I must be getting old! You are right, it is an update to V1. I'll go back to sleep

yes

Every time I load Publisher1 I get a notification that an update to v2 is available. I know there is! How do I stop it????

I created a file which had a small amount of text to which I applied a warp. Everything looked fine on the screen but when I came to print the file, the text was printed without the warp being applied. In the end I had to export the file as a pdf and print it, which worked perfectly. The file is attached. Using very latest build Windows 11 2023.afdesign

Yes, I have found that if I export the whole document to pdf it will print properly with the the warp. But why should I have to do that?

I designed an item and applied a perspective warp to a text layer. Everything worked well on the screen but, when I tried to print the document, both the print preview and the actual print discarded the warp. I tried putting all the layers into a single group, but that didn't work. In the end, all I could do was to export the warp layer into a jpg file, paste it into the document and hide the original layer. Has anyone else found this? I don't see much point in having the warp feature if it cannot be printed. I have attached screenprints of the afdesign file and the print preview afdesign file.docx print preview.docx

Make sure the controller is set to velocity or pressure in the toolbar. For some daft reason it defaults to None

I have created two identical books, one with photos linked and one with photos embedded. You will see from the attached spreadsheet that in both cases the RAM usage rises by much more than the file size of each photo added and that the embedded file rises even faster. After the Master template is set up, the RAM usage is 603MB, but by the time I add 10 photos amounting to only 182MB over 10 pages RAM usage goes up to 2115MB in the linked file and 2964MB in the embedded book. The saved file sizes are only 2.6MB and 238MB respectively, so RAM usage is about 10 times the file size. The really odd thing, though, is that when I restart the program and reopen each file the RAM usage is 2199MB in the linked file (more than the size at closing) but only 638MB in the embedded file. In addition, the linked file takes an eternity to open, whereas the embedded file opens very quickly. During the testing I closed the program completely before working with the other book. If I merely close one book with the program staying open and open the other book, not all of the RAM is released from the first book. For instance, if I close the linked book and then open the embedded book, the RAM usage sits at 1242MB - almost double the usage if I restart the program and then open the file. There is obviously a lot of memory wastage. Until there is a fix I shall embed all photos and regularly close and restart the program. RAM usage.xlsx

I am having the same problem on a Windows machine. I have about 20 pages with a total of maybe 30 photos, all linked, and the RAM being used is about 6GB. Each photo is about 16MB, but as they are linked, I would have thought RAM usage would be less. Is Publisher perhaps loading the linked photos into RAM at full resolution? I might try making the same book with the photos embedded to see what difference it makes

I'm having the same That is the problem I am having. The virtual keyboard pops up if I try to change font, or a dimension in brushes or page size. I have disabled Windows Ink in either the Wacom setting specifically for Designer and/or in Designer preferences and the keyboard seems to stop popping up, however dynamics in pixel brush disappear. I had exactly the same problem in Photo, but that has gone away by disabling Windows Ink in Photo preferences but leaving it enabled in Wacom specific settings for Photo, and I still have dynamics in the brush