0125 Posted May 28 Share Posted May 28 I just installed Affinity 2.5.0 suite across all applications yesterday. It broke all font associations for text inside groups/symbols and a fallback font (Verdana?) was applied. Once I click inside the text element it still shows the name of the correct font (it simply renders a different font). When I reassign the correct font, it is updated for all occurrences of the same group/symbol. This happened for Publisher and Designer for all files, I didn't check Photo. UPDATE: rolling back to 2.4.2 makes this issue go away (no permanent harm done). I've also read in a different post that version 2.5.2 will solve font-related issues. I recommend to just wait and sit it out for everybody experiencing the same problem. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted May 28 Share Posted May 28 Was there a specific font that you had problems with? Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
0125 Posted May 28 Author Share Posted May 28 Hi Walt, thanks for your reply. It definitely didn't affect all fonts but I couldn't tell the criteria. I assumed that it to do with being inside a grouping or symbol. But not sure. Searching on the forum, I found 3-5 topics related to 2.5.0 and fonts so I guess it has to do with the introduction of variable font support. For now, I'm fine. I reverted back to 2.4.2 and everything works perfectly again. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted May 28 Share Posted May 28 OK; thanks for checking. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted May 30 Staff Share Posted May 30 The issue "2.5.x Windows users missing fonts after updating" (REF: AF-3196) has been fixed by the developers in internal build "2.5.2.2483". 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. Quote Link to comment Share on other sites More sharing options...
0125 Posted July 1 Author Share Posted July 1 I just installed Affinity Publisher version 2.5.3 and problem persists. I reinstalled 2.4.2. - all fine! Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted July 1 Share Posted July 1 10 minutes ago, 0125 said: I just installed Affinity Publisher version 2.5.3 and problem persists. I reinstalled 2.4.2. - all fine! It would still help to know a specific font you're having trouble with, I think. Also, please note the instructions in the post by @Affinity Info Bot above to tag the Bot if you still have problems. I've done that now, so the Affinity team will know. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
0125 Posted July 1 Author Share Posted July 1 The font in question is Go Melon ttf. walt.farrell 1 Quote Link to comment Share on other sites More sharing options...
TravisL Posted July 2 Share Posted July 2 I had some fonts break on the most recent update as well (I haven't tried rolling back yet). The font in question is League Gothic. It's a client project so I'm just focused on a single letter. A zoomed in letter with what appears in the Font panel at the top The zoomed in letter (restored font style) once the only available named weight is selected. Notice Variable appears selectable and can be selected to change the weight through that menu (which isn't how the original font style was set up). Another font family in the same file which has no Variable font version hasn't broken. So TLDR: To me it looks like variable fonts have font weights detached if they were previously selected as something else. The ideal behaviour should be it keeps the selected weight whatever it was and not break the font style. I don't want to go through my files and fix them so I'd appreciate if the program could remember what my font styles were. Quote Link to comment Share on other sites More sharing options...
kenmcd Posted July 2 Share Posted July 2 On 7/1/2024 at 5:39 AM, 0125 said: The font in question is Go Melon ttf. This appears to be another example of the same issue (already posted). This font has two incorrect name field which Affinity now may be depending on since the update to support variable fonts. Full Font Name is wrong - missing the style. PostScript Name is wrong - includes spaces and is missing the style. There have been other posts with the same font issues. 0125 1 Quote Link to comment Share on other sites More sharing options...
kenmcd Posted July 2 Share Posted July 2 6 hours ago, TravisL said: To me it looks like variable fonts have font weights detached if they were previously selected as something else. The ideal behaviour should be it keeps the selected weight whatever it was and not break the font style. I don't want to go through my files and fix them so I'd appreciate if the program could remember what my font styles were. This is a different issue (and also posted by others). Affinity does not connect the static font style selection to the variable font named Instance. So if a user updates the fonts from static to a variable the style selection is lost. Google Fonts names their static and variable fonts so they are interchangeable. Which also means you cannot have both the static and variable fonts installed at the same time. Browsers can recognize the static and variable fonts (which are named the same) interchangeably. Affinity should be able to do the same. GF does this so when a font family is upgraded from static to variable no websites are broken. The fonts all still work. Affinity should be able to do the same with Affinity documents. walt.farrell and 0125 2 Quote Link to comment Share on other sites More sharing options...
0125 Posted July 3 Author Share Posted July 3 16 hours ago, kenmcd said: This appears to be another example of the same issue (already posted). This font has two incorrect name field which Affinity now may be depending on since the update to support variable fonts. Full Font Name is wrong - missing the style. PostScript Name is wrong - includes spaces and is missing the style. There have been other posts with the same font issues. So, this might be a really dumb question, but what does that mean for me: Is there anything Affinity can do to fix it for all fonts, or do I have to wait until font designers update their font files? Quote Link to comment Share on other sites More sharing options...
Dan C Posted July 3 Share Posted July 3 @0125 I've downloaded the Go Melon font from DaFont and installed this on both Windows and macOS. As kenmcd mentions above, this font fails validation due to the name table structure/usability: However on both platforms in Affinity 2.5.3, the font appears listed as 'Go Melon', as I'd expect. Are you using Affinity with Windows, or macOS where this problem occurs? Are you using a different version of the font file that shows this issue in the apps for you? Many thanks in advance! 0125 1 Quote Link to comment Share on other sites More sharing options...
Dan C Posted July 3 Share Posted July 3 @TravisL as kenmcd mentions above, this is a known and logged issue with our development team which can occur either with documents that used variable fonts previous to 2.5.x, or if you install a variable font to replace a previous static font on your system. Therefore I am updating and 'bumping' this report with our dev team, to bring it to their attention once again. I hope this helps! TravisL and 0125 2 Quote Link to comment Share on other sites More sharing options...
kenmcd Posted July 3 Share Posted July 3 11 hours ago, 0125 said: Is there anything Affinity can do to fix it for all fonts Yes. They can do a better job of matching the fonts. There are many fields inside the fonts which would tell you this is Go Melon Regular. NameID1 is Go Melon NameID2 is Regular The OS/2 weight setting is 400 - that tells us it is a regular weight. There are other flags which are set which tells us this is regular. If it is an OTF font, there are name fields and flags in the CFF table. There is a "preponderance of evidence" that this is the right font. So if one name is not 100% - there are lots of other things to look at. So even though the Full Font Name is not "correct," and the PostScript Name is not "correct" - we can still figure-out this is Go Melon Regular. The applications should be able to do this too. (note: it is kinda obvious that ID does this - quite awhile back a user posted three fonts that worked in ID, but not in Affinity - I was amazed at how bad they were, and they still were identified and worked in ID). 0125 1 Quote Link to comment Share on other sites More sharing options...
0125 Posted July 3 Author Share Posted July 3 (edited) I'm using Windows. I don't which version of the font I was using. This is what happened when I upgraded from 2.4.2 to 2.5.3: I just reinstalled the ttf from dafont and it renders as it should now for newly typed text, but not for updated files. Yes, it would be great if the software would be more forgiving with bad fonts. Great suggestion. Edited July 3 by 0125 I was wrong, still not working correctly. Quote Link to comment Share on other sites More sharing options...
kenmcd Posted July 3 Share Posted July 3 55 minutes ago, 0125 said: I just reinstalled the ttf from dafont and it renders as it should now for newly typed text, but not for updated files. That is what I would expect, until Affinity can make the font matching better. 55 minutes ago, 0125 said: I was wrong, still not working correctly. What is not working? I just installed the OTF font, and applied it to some text, and exported to PDF. New or manually updated style should be working. I can see the Font Style field is blank, not selected, in the image above. So manually re-selecting that should work. Just the automatically updating older docs is going to be an issue. I can make you a fixed version with a new name. 0125 1 Quote Link to comment Share on other sites More sharing options...
TravisL Posted July 4 Share Posted July 4 A way of managing this in addition to a more flexible tool for detecting variable versus True Type fonts is to have a dialogue that pops up like Font Manager with a notice that "Some fonts are missing" then you can update them in one place rather than many places (in styles manually). Something similar to what Adobe does when it detects there are missing fonts. The variable/True Type font icon could help picking new fonts as well if there's a way to tell what similarly named fonts installed are static versus variable. 0125 1 Quote Link to comment Share on other sites More sharing options...
0125 Posted July 4 Author Share Posted July 4 Exactly, automatically updating older docs is an issue. Quote Link to comment Share on other sites More sharing options...
Alfred Posted July 4 Share Posted July 4 23 hours ago, 0125 said: Is there anything Affinity can do to fix it for all fonts 11 hours ago, kenmcd said: Yes. They can do a better job of matching the fonts. The OP reported that reverting to version 2.4.2 made the problem disappear, which suggests the app was previously doing a better job of matching the fonts. Quote Alfred Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen) Link to comment Share on other sites More sharing options...
Dan C Posted July 4 Share Posted July 4 13 hours ago, 0125 said: This is what happened when I upgraded from 2.4.2 to 2.5.3: I just reinstalled the ttf from dafont and it renders as it should now for newly typed text, but not for updated files. Thanks for providing that for me! You should find that selecting the Font Style in 2.5.x after opening your documents should correctly update and apply this font - but this is essentially the same issue as TravisL has shown above, which is logged with our development team to be addressed - our apologies for any inconveniences due to this in the meantime. 1 hour ago, Alfred said: The OP reported that reverting to version 2.4.2 made the problem disappear, which suggests the app was previously doing a better job of matching the fonts. As I understand it, version 2.4.2 (and previous) did not support variable fonts, therefore this could not have occurred as the app had no requirements to match fonts - simply the static version was used, where present. 0125 1 Quote Link to comment Share on other sites More sharing options...
Alfred Posted July 4 Share Posted July 4 25 minutes ago, Dan C said: As I understand it, version 2.4.2 (and previous) did not support variable fonts, therefore this could not have occurred as the app had no requirements to match fonts - simply the static version was used, where present. Isn’t Go Melon only available as a static font? I’m afraid TravisL’s posts about League Gothic have blurred the discussion a little. Dan C and 0125 1 1 Quote Alfred Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen) Link to comment Share on other sites More sharing options...
Dan C Posted July 4 Share Posted July 4 10 minutes ago, Alfred said: Isn’t Go Melon only available as a static font? I wasn't aware of this - thanks for clarifying! I can confirm that with only a static TTF version of this font installed, documents created prior to 2.5.x will open with the font 'Missing', and the Font Style not selected: (2.1.1 Designer) (2.5.3 Publisher) This certainly is a different issue from the Static / Variable bug mentioned previously - my apologies! I'm checking with our team now to confirm if this is already logged, and if not will be sure to report it separately to our devs 0125 and Alfred 2 Quote Link to comment Share on other sites More sharing options...
TravisL Posted July 5 Share Posted July 5 14 hours ago, Alfred said: Isn’t Go Melon only available as a static font? I’m afraid TravisL’s posts about League Gothic have blurred the discussion a little. Sorry, didn't mean to confuse things! I saw a similar font breaking problem so assumed they were related. Alfred 1 Quote Link to comment Share on other sites More sharing options...
0125 Posted September 19 Author Share Posted September 19 Does anybody know in which version this issue will be fixed? I just tried out 2.5.5 and font matching still seems to be broken... 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.