AlanH

Thanks all for your suggestions: First of all, today both PCs are behaving with the file that caused an immediate crash on font select. I have no idea why. Machines' update history shows no quality (KB) updates since 14 Dec, i.e. before I last posted here. @carl123 OK, I have switched that to 'off' on both machines, but as noted above, the file is now working OK on both platforms. @blackstone I suspect that would have been the case on mine if the 'bad' file had not started behaving. @SrPx Both my installations have SSDs as their system drives with OS and all fonts on board. Graphics drivers are kept up to date, and the two platforms have different GPU cards (NVIDIA and AMD). I will run SFC and DISM when I have time. For the time being, I will monitor the situation for font crashes. I have no idea why the machines have both started behaving....

I think it must relate to the .NET configuration of particular computers...

And the same with my Win11 machine. See examples of both in attached video... PUB2FONTSELCRASH.mp4

This had been fixed by the later versions of Suite v1, but reappeared yesterday on my Win 10 machine in Publisher v2.0.3 (but I assume Designer/Photo will do the same.) The v1 update removal list is no longer relevant, so what do we do now for v2 on Win 10? The only KB updates I have installed at present are: 5012170, 4598481,4593175,4586864,4577266,5003791,5000736,4562830 Suite apps are not usable at the moment due to this! Cheers, Alan

OK thanks, Callum - I have raised it as a feature request. Alan

I raised this as a question, but as it seems the function is not available, I propose it here as a new function: Request Please allow configurable filenames for image file exports, ideally using wildcards. At a minimum, it would be useful to have files named <Publisher Filename>_<Section (name or number)>_<In-section page number> instead of just <Publisher Filename>_<Global page number> as at present. Rationale (one example) I use Affinity Publisher to create graphic overlay screens for use with my video editor software, Vegas Pro. After any change to the Publisher file, I export all its pages as PNG files, over-writing all previously exported files. As the PNG files are explicitly referenced in Vegas, they update automatically on the project timeline. This is a particularly convenient solution for last-minute global changes to text, fonts, logos etc. For ease of use, I group sets of similar pages using Publisher's "Sections" function, with meaningful section names (e.g. TITLES, CREDITS, LOGOS, SUBTITLES etc.), restarting page numbering for each section. As it stands, Publisher simply exports all images with filenames <Publisher Filename>_<global page number>.PNG Having PNG (or other graphic) files export with names constructed from the Section name and in-section page numbers would enable me to add pages to individual sections without disturbing existing file names (which, as mentioned above, are hard-referenced in the video editor.)

It would be useful for work on large documents if the page thumbnails could be (optionally?) labelled with Section Name and Section Page No. rather than the global page number. Section numbers (e.g. Section3, Page 5) would be acceptable if the section names were too long to fit.

I have just found this topic while preparing to make the same suggestion. Dark Mode is much more relaxing to work in, so would it not be possible to replace that barely-discernable grey border on the active thumbnail with, say, a bright yellow one? Like Eusebius, I also struggle to identify active pages in documents with near-identical pages.

Question Can Publisher export PNG (or other graphic) files with names constructed from the Section name and in-section page numbers? Background I'm using Affinity Publisher on PC to create graphic overlay screens for use with my video editor software, Vegas Pro. After any change to the Publisher file, I export all its pages as PNG files, over-writing all previously exported files. As the PNG files are explicitly referenced in Vegas, they update automatically on the project timeline. This is a particularly convenient solution for last-minute global changes to text, fonts, logos etc. For ease of use, I group sets of similar pages using Publisher's "Sections" function, with meaningful section names (e.g. TITLES, CREDITS, LOGOS, SUBTITLES etc.), restarting page numbering for each section. As it stands, Publisher simply exports all images with filenames <Publisher Filename>_<global page number>.PNG Having PNG (or other graphic) files export with names constructed from the Section name and in-section page numbers would enable me to add pages to individual sections without disturbing existing file names (which, as mentioned above, are hard-referenced in the video editor.) If there's a way to do this, I've not found it yet. And yes, I know I could manage each Section as a separate Publisher document, but that defeats the object of having a common workspace for graphical assets, and means more project files to manage. I could also do this with Designer (and I used to), but as page counts grew to over 100, Publisher with its Master pages seems the much better option. Regards, Alan

Thanks, Callum!

Affinity Publisher 1.10.4.1198 on Windows 11 (for my sins)... Select a plain coloured rectangle in a Master page in Publisher, then select Photo persona. Immediate crash when Perlin Noise Filter selected. Standalone Photo (same version/platform) does not crash with the same function. Cheers, Alan

After years of sloppy practice, I have finally got into the habit of naming my drawing element and group layers as I create them. When I Ctrl-G to create a new group, would it be possible to have the newly-created group label open with the cursor ready to give it a name? The return button could simply be hit without typing anything if no label was required. This might encourage routine group naming. Sorry if it turns out this option already exists!

@Jon PThanks, I will do that pro tem. Have a good Christmas! (finally figured how to do that "mention" thing!)

Something springs to mind - this problem seems to have arisen since I purchased the Christi's Comix Toolbox brushes set and installed them across the Affinity suite. Any possible connection?

Hi @Jon P - Thanks for the suggestions. I have had a go at them this evening: a) I downloaded the beta version and using the same document, I could not get it to lock up while scrolling fonts - admittedly exercising it only for a few minutes, but that's much longer than the current active version. In case my computer had suddenly got better, I went back and re-checked the current version, and it still locked up in about half a dozen font select scrolls. That may be a good sign, but why would the Beta behave differently? b) Re. the Crash Reports, the only place with an Affinity folder is Roaming, i.e. C:\Users\Alan\AppData\Roaming\Affinity\Publisher\1.0\CrashReports but the \reports folder under that is empty. I think Publisher is locking so hard that it cannot actually 'crash' i.e. close down, so no crash report is being written when I finally get fed up with waiting (up to several minutes) and terminate it via Task manager. c) Re. fonts, I have limited experience with fonts beyond installing and removing them via the c:\windows\fonts folder. Two observations: 1. When I select them all and try to zip them, 7-zip tells me there are duplicate file names and refuses to work. I read somewhere on the web that the 'real' font files are in c:\Windows\SxS\ and when I search the massive list of folders under that for *.ttf, I do see most fonts appearing twice and some three or four times. It's a mystery to me, I'm afraid. 2. I have tried to remove all unnecessary fonts as part of this exercise, but find some will not respond to the Remove option, and stay in greyed-out form. So the Beta seems to be better, but maybe my current font situation is not 'textbook' and needs some rationalising, but that's outside my skill-set at the moment! Regards, Alan

This has started happening to me over the last couple of weeks on all 3 Affinity apps, on both my PCs. All Affinity apps freeze solid when I attempt to select a new font for text in the document. I first noticed it in Designer, as I use it all the time, but the same is true in Publisher and Photo. It seems marginally worse in Publisher, which is why I'm reporting it here. This problem has been reported multiple times in the Affinity Forum over the lifetime of the Affinity products (often regarding Asian fonts, which is not the case for me), but no solid fix seems to be evident, and the threads just seem to peter out. I have reduced the number of fonts on my Office machine as far as possible, and am down to barely more than the system fonts, and I have never had font problems before - I am not a 'font hoarder'! This fault seems to have appeared since I upgraded to a 4K monitor about 3 months ago. One of the reports indicated a link with 4K monitors on the Mac bug-reporting thread, but the suggested fix (settings for memory usage?) wasn't applicable to the PC. When the program locks up/freezes, it does so pretty hard, and requires several attempts to kill it via Task Manager. When it's frozen, Task Manager reports it as using 930MB RAM and 33.3% CPU (the latter looks like a pre-set limit). (update 16 Dec) This happens even with screen resolution set down to 1920x1080. Appears to happen when scrolling swiftly up or down through font list with text selected - doesn't seem to happen if stepping down a font at a time (but that's a very slow way of finding fonts...) My machines are reasonably spec'd with fully updated OS & drivers, so I wouldn't think there is a hardware or OS issue: Office PC: Win10 Home on i7-930 with 8GB RAM and 2GB video card Video Edit PC: Win10 Pro on i7-6700 with 32GB RAM and 8GB video card. Does anyone know how to fix this? Regards, Alan

Many thanks to all who have responded so quickly (maybe we're all spending more time in front of our computers at the moment!) GarryP - thanks - I'm familiar with flood fill, but in this case, I'm doing a freehand layer below the black artwork. (Cool graphic!) Old Bruce - thanks - that was what I had set and it still wasn't working for me... Walt - thanks - that sorted it! I guess I didn't understand what 'wet edges' meant in AP. So: With wet edges ON, then each new stroke starts off at ~25% opacity and subsequent overlapping ones add another 25%, until it reaches full target colour. With wet edges OFF, it just paints solid colour at the target level, as you describe - and as I was looking for. I have seen 'wet edges' in other painting apps, but it behaved much differently there, i.e. like a dynamic watercolour bleed, which made more sense to me descriptively. It looks like I had fallen foul of nomenclature - always a problem when switching from one maker's app to another. Hooray - problem solved - thanks once again, all! Alan

I am trying to make AP my sole image editing tool, but yet again I am failing to achieve something that Paintshop Pro 9 (yes it still works in Windows 10) does natively. All I want to do is a "painting-by-numbers" style fill with a completely flat brush, under a scanned ink drawing - with no buildup from stroke to stroke; just set a target colour and go. Is that called a 'wash'? How do I achieve this with AP? Despite its myriad of brush adjustments, I can't find a single one of them that suppresses the colour buildup. There is discussion about something like this problem in another thread, but it gets into all manner of esoteric settings, comparisons with Photoshop and suggestions of yet more third party apps, none of which helps me achieve this simple task in AP. So am I just using the wrong painting tool, or am I failing to understand something fundamental in the AP approach? It's quite possible I have missed something in the help file and/or tutorial videos, and if I have, please forgive me and point me to the relevant reference! Cheers, Alan

Thanks - phew!

I did a Blurb trade paperback quite successfully a while ago, but using their own software. I'm now keen to do some books using Publisher, and thought I'd got the hang of their specs, but this thread has made me wary! As far as I could make out from the Blub specs (and as implied in the quote above), the cover and the body of the book are two completely distinct PDFs that are uploaded as separate files, so there should be no need to struggle to produce them from a common Publisher document, or to stitch two PDF files together before uploading. So am I missing something here?

Hi I had brought this up in a Designer forum, but nothing happened. It matters even more in Publisher, hence this request. I am being required to submit a PDF for web viewing (iTunes Digital Booklet) that has its Initial View options set for Full Screen. Although I can set other initial view options (zoom, facing pages etc.) in my third party reader, it seems that the Full Screen option is elusive. I cannot find any freeware app that will set Initial View to Full Screen, and It seems wasteful to buy a full-blown copy of Acrobat just to do that one thing. Please could you add a full set of Initial View options to the PDF export dialogue. It would be a valuable - and logical - addition to the program. Thanks, Alan

Many thanks for that, Tantedante - I spotted it earlier - that's fixed it - phew! I guess it'll become a formal release pretty soon. Alan

This is a real problem for me. I create multiple (30 or more) title boards as artboards on a common Designer document for my video productions, and export them to individually named jpegs in one fell swoop using slices in the Export persona. I now have to export each board singly (manually renaming each one) direct from the Designer persona. This is painful. Copying content into a new document as recommended above does not change the problem. All the documents I have created so far trigger this bug. (edit after downgrading) I have just downgraded to 1.7.1.404 (you have to uninstall 1.7.2 first). The file created in 1.7.2 crashes 1.7.1. BUT if I now make a new document and copy the artboards from the new version and save that, I can get into Export>Slices. So it looks like there's something in the 1.7.2 container that causes the crash, not the 1.7.2 program environment or the file's artwork content. Please advise me where to find the 1.7.3 beta when it is released - if it fixes this bug. Thanks - Alan

It would be useful to be able to set the Initial View options for PDF exports from Designer (and other Affinity apps). I prefer to give people files that open in Single Page/Fit Page view, which is seldom the reader default. Cheers!

Thanks, I'll put in a feature request!