Search the Community

The issue "Installing AF Fonts will cause the app to crash, and then crash on launch with no way to Ctrl runup" (REF: AF-2877) has been fixed by the developers in internal build "2.5.0.2430". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

The issue "Fonts installed via Creative Cloud cannot be found" (REF: AF-2909) has been fixed by the developers in internal build "2.5.0.2430". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

The issue "Fonts installed via Creative Cloud cannot be found" (REF: AF-2909) has been fixed by the developers in internal build "2.5.0.2430". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

The issue "Fonts installed via Creative Cloud cannot be found" (REF: AF-2909) has been fixed by the developers in internal build "2.5.0.2430". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

The issue "Variable Font - All axes visible when they shouldn't be" (REF: AF-2910) has been fixed by the developers in internal build "2.5.0.2430". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

The issue "Variable fonts - Axes panel has transparency enabled" (REF: AF-2878) has been fixed by the developers in internal build "2.5.0.2430". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

The issue "Variable fonts - Axes values not updating" (REF: AF-2845) has been fixed by the developers in internal build "2.5.0.2430". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

Toen ik nog met Adobe InDesign werkte, kon ik geheel gratis fonts downloaden bij Adobe. Hierbij was ook het font Sabon LT PRO Roman. Niet te verwarren met Sabon LT STD regular. (Dat is gratis, maar "restricted"; dus niet bruikbaar voor een boekpublicatie. Maar nu is mijn vraag: werken de fonts van Adobe ook in Affinity Publisher? Als ik het font Sabon LT PRO Roman apart moet aanschaffen via een derde partij (MyFonts by Monotype) dan betaal ik daar maar liefst € 65,33 voor. En dat voor maar 1 licentie en voor 1 computer. Wanneer ik die font van Adobe kan gebruiken in Affinity Publisher, dan kan ik mijn geld terugvragen. Ik heb nu nog een lopend Photography subscription bij Adobe voor Photoshop en Lightroom. Dat is wel dubbelop met Affinity Suite, en hoewel ik van zowel Adobe Photoshop als Adobe Lightroom (bijna) geen gebruik meer maak, maar wel de fonts kan downloaden/toevoegen in al mijn projecten, houd ik dit nog even aan. Graag uw advies of ik het Adobe font Sabon LT PRO Roman ook kan gebruiken in Affinity Publisher? Of dat ik dat font toch moet aanschaffen via een derde partij. Wie het weet mag het zeggen. Bij voorbaat mijn hartelijke dank!

Selecting Character > Font Collection > English or the equivalent control in Edit Text Style immediately crashes Affinity. The other collections work fine. I thought this was a new issue in the beta but was surprised to find that it also happened in 2.4.2. The English collection is an automatic language collection. I'm sure I've tested it before and it didn't crash but I recently installed several variable fonts to test them in 2.5 so perhaps that's related. My system is set to English Canada if that makes a difference. Affinity Publisher 2 Affinity Store-2024-05-02-083818.ips Here's my font collection list, it's just the basics, I don't currently have any collections of my own.

Hello and thanks for your response. Evey document does that, even in a new one. Hardware acceleration is disabled because of my older GPU (GCN 1). Edition Windows 10 Home Version 22H2 Installed on ‎4/‎1/‎2024 OS build 19045.4291 Experience Windows Feature Experience Pack 1000.19056.1000.0 The rest of the System: CPU R5 5500 2X 8GB DDR4 2666 RAM Mobo Asus with B450 OS and Apps on M.2 nVme Crucial P3 1TB have a couple more drives but are only for storage and not working any files from there. After I posted this it also started hanging on startup with 20% usage of CPU just to open designer, not to open any file. At first I suspected the high amount of fonts but this lag in tools happens even if I make a box and convert to curves. Also tried with fonts disabled, same lag in opening and while selecting tools in the doc. After the first time it goes away but there is just a bit of activity in the CPU and that's it, no reading from any disk or anything. Also the % of CPU may change, one time I open and it goes 20% and still hangs for 10-20s, the other time it may be at 10%. As I said this was not present since the very last update I got. Since it updated in app I think I have installed the msix version of designer. edit: this is not happening in my home system that is similar, but I don't know right now which windows version it have. It have slower SATA m.2 crucila, slower DDR4 (still 2X 8GB ) but a much more powerfull RX 5500XT 4GB as a GPU. I will also test in my laptop later which have an AMD APU 5425U I think.

I'm unsure whether this is covered under: AF-2910 - Variable Font - All axes visible when they shouldn't be But on Windows with Roboto Flex, the five registered axes are shown in both the context toolbar and the character panel but all thirteen axes are shown in the Text Style Editor...

I hope they’re able to address it soon. For those of us exploring the newly introduced support for variable fonts in the 2.5 beta versions of the Affinity apps, the only way to install them at the moment is via the app settings.

As confirmed previously: Unfortunately Apple are yet to address this issue within iPadOS at this time. In our testing we have found that installing fonts though a third party iPad Font Manager (which usually install fonts as 'Profiles' in iPadOS Settings) does not cause the same slowdown within Affinity's font list. Therefore at this time we recommend uninstalling your fonts from the Affinity app settings directly, then installing them using a third party Font Manager and you should find this does not occur. I hope this clears things up!

Thank you very much for those files (I shouldn't need the highlighted ones either thanks!) - unfortunately everything looks to be normal there and not out of the ordinary, so it certainly seems to me like it could be a font you have installed with Windows. Do you have many fonts installed to your copy of Windows or use a font manager at all? I think the best way to try and find out what potentially could be stopping it is by using Process Monitor to monitor the app's process on launch and then send us the log file that creates. To do this you would first need to download and run Procmon64.exe - this can be found on Microsoft's Process Monitor Page here: https://learn.microsoft.com/en-us/sysinternals/downloads/procmon After you download and run it will start to capture events (of which there are many) so you will want to set up a filter for the app you are using. In my case I created a Filter for the process name of 'publisher.exe', if you're using Designer this will be 'designer.exe' etc. When that filter is set up, just run the application and wait for it to crash in the way you've been seeing. Once it has done that you can disable the Capture using the Start/Stop Capture button to the right of the save icon. After that please save the log file using the 'Events displayed using current filter' option on the save dialog and the PML format. When that has saved could you upload that to us - unfortunately it is relatively large (mine was about 71mb), but hopefully it will be able to give us a little more information to go off. I've made a short video demonstrating those steps below. ProcMon.mp4

The hidden axis flag is not meant to never expose that axis. It is a recommendation based on certain assumptions. Neither of these is true for the parametric axes in Roboto Flex when used in Affinity. Additionally, the 20 pre-defined named instances in Roboto Flex do not even touch the 8 parametric axes at all - all of them remain at the axis default. So basically without being able to see them, they are not used at all. Being able to set the x-height is a very useful variable feature. Being able to set the ascender height is a very useful variable feature. Being able to set the descender depth is a very useful variable feature. These are variable axes that make Roboto Flex an advanced variable font. And makes it very useful to knowledgeable advanced users who know how to use it. Which is what we are asking for - an advanced-user interface. These are advanced axes. Not all users would ever want to change them. But advanced users will welcome the ability to use these axes. Enable knowledgeable advanced users to do advanced stuff. Based on the hints from the Affinity folks here, it sounds like they are working on adding this. Which is welcome news. So it appears they listened to the requests, and everyone just needs to be patient. Side note: Roboto Flex is an OFL font so you can modify it as you wish. And Google Fonts even encourages people to do so when they want some changes. Whether you should be messing with an advance font like that is another issue. Plus after Affinity adds the option to see all the axes, there will be no need.

When we talk about Roboto Flexi 13 different axes, I have hard to believe that the five axes presented can achieve what the eight hidden axes can achieve - I really want the hidden axes IF they can change the fonts looking to be useful, if not, they can be hidden... Downloaded a font yesterday that had 15 axes to play with - everyone of them really nice.

Don't do this, you shouldn't be editing other people's fonts, least of all if you have to do this every time there's a font update. We should provide a technical solution within the software for those who want to see all axes.

Webflow does just that by putting a bullet point style dot against the Variable Font Name and automatically grouping variable fonts so they all appear together in the font list, so you effectively have all static fonts in one section of the list and all variables in their own section which is nice because you have instant access to all your variable fonts without the need to scroll through what can be a long list of fonts trying to locate the variable font and you can instantly identify which fonts are the variable ones… Something similar could be a nice addition to the Affinity apps perhaps 🤔

Some feedback. Is there a way that they can show if a font is variable or static in either the character panel or the font dropdown list? Also, an interesting behavior is that you can have two different fonts, one in the font dropdown list and the other in the context toolbar, which can be different. Because of this issue, I sometimes have difficulty choosing a font. I am curious if that is expected behavior or not.

One of the reasons variable fonts are being adopted for interfaces - the width axis is used to fit varying localized word lenghts into the same field width. Apple System Font variable, Microsoft Segoe UI Variable, Android Roboto Flex variable, etc. And the optical size is automatically adjusted.

Thanks for a detailed view of the problem when unlocking the min/max axes values on Variable Fonts! Make sense… But, in the same time, I’m curious of this results of “mess" - I will take a few favorite fonts and unlock, just for fun… I’m glad that I can run FontCreator on my Macbook Pro M1 - the only font-app I’ve found that can resave font after parameter changes.

Feel free to PM me a copy of the crash report and i can make sure it matches up to mine and @Hangman's I had the other fonts still installed but I've just tried this again from scratch, created a new Font Collection and left Shantell Sans uninstalled and got the crash, so its not related to that font. Guess i was just lucky when it didn't crash before

Yes, for me it still crashes the 2.5 betas, both if I just disable it or if I delete it. I did not test with 2.4. EDIT: I still have 4 other variable fonts installed & enabled: Geologica, Playfair Display, Recursive, & Roboto Flex. Did you test with those 4 enabled?

Probably because some effects don’t work well outside of a particular range of values (in much the same way as some static fonts are unsuitable for use at very small or very large sizes). A font manager deals with font activation. I presume you mean a font editor app. You should be able to tweak pretty much anything in an open source font, but there will usually be good reasons (see above) why the font designer has placed restrictions on the font as originally published.

You find yourself confused because it is inherently confusing! I think it would be wise to avoid having the static and variable versions of a font family installed at the same time, in much the same way as it’s best to avoid having TTF and OTF versions installed concurrently.