nwhit

HOORAY!!! I ended up renaming my 1.9.3, then downloaded a fresh version from the Affinity Store instead of updating. That seems to have fixed the issue. Working now!!! Not sure why the update messed things up, but at least it's now working!

Interesting note: I have OS12 installed on a Parallels VM along with my regular apps. I upgraded that copy of APhoto from 1.9.3 to 1.10.0 and Eye Candy works on that version. (Note: Affinity apps work (mostly) in the new Parallels v 16.5.1.) Very strange. On my normal OS11 installation, EC worked fine in 1.9.3 and all previous versions (from the Affinity Store), and worked fine on all the 1.9.4 and 1.10 betas. Still does. And restoring APh 1.9.3 from a backup, EC still works fine. Not sure what the issue might be. Was looking forward to the improvements in APub and APh in 1.10, so a bit discouraged right now.

Just tried the 1.10.0 final and EC has stopped working. Not only is the preview totally unusable, but the final end-product doesn't work. Oddly, it worked fine in 1.9.3 and all the betas including (as per the pics) the final RC2 1.10 beta. Screen shots of 1.9.3, 1.10 RC2 beta and 1.10.0 final. All Affinity Store versions. Metal on OS11.5.1. Had to downgrade back to 1.9.3 since I use EC for client work.

...and on 11.4

Still have the Font Menu corruption problem with this RC, same as with the other 2 apps.

The font menu corruption problem is still in this RC.

This is still an issue in the latest beta/RC 1.10.0.1115. This was not an issue prior to my upgrade to v1.9.x and/or Big Sur. Previously I used Font Book collections routinely without an issue.

In all 3 of the Affinity betas, if you select any Font Book collection, it shows numerous duplicate styles for many of the fonts. If you then select one of those collections, when subsequently then go back to the All Fonts listing, it will now show even more duplicate font styles, thus making it a bit impossible to select a font and style, not knowing if you've selected a real one or some corruption of the list. This first began with either v1.9.x and/or my switch to Big Sur. Can't be sure which caused it since both happened at about the same time for me. Prior to this, I used Font Book collections routinely in all Affinity apps without any issues. This problem was also confirmed by Old Bruce. Full details of the troubleshooting and narrowing down of the problem was reported in this 1.9 bug thread. However, the problem is still in the newest 1.10.xRC beta as well. Font Book collections are useless and will cause the main All Fonts menu to corrupt.

Aha! Think I may have found the workaround! According to this article by a prepress guy, apparently one of the font managers (TypeFace) can actually shut off/deactivate the OS11 System/Library/Fonts/Supplemental fonts, which are 283 fonts, many of which are seldom used by some people. Assuming this is true (I hope!!!), I can thus use TypeFace to create actual sets that would only include the fonts I want, plus it has to include the 73+ system fonts that cannot be deactivated. That would really help clear up the All Fonts dropdown!! http://www.jklstudios.com/misc/osxfonts.html UPDATE: Just tried to deactivate one of the Supplemental fonts and it worked! And it no longer showed up in APub All Fonts!!! Looks like I may have found the magic solution! Plus TypeFace is only $35, so a lot more affordable than some of the other options, which according to the article, none of the others can deactivate these 283 Supplemental fonts. Thank goodness!!

So in other words, the font sets/groups you create in a font manager become the only active fonts showing in apps??? But not clear on how can they not show (deactivate) the 355 "permanent" fonts in OS11 that can't be deactivated? Is a font manager app actually moving fonts out of fonts folders, or trying to deactivate fonts not in a group?? But that, of course, can't be done in OS11 with the 355 fonts in System/Library/Fonts. I guess I'm still not seeing how what is created as sets within the font manager apps affects what I see as font lists within apps. Old age, I'm thinking!! 😂

Old thread, but have a question. I've downloaded a few free trials of these mentioned font manager apps, but for the life of me I cannot see how to use them within Affinity apps! None of their documentation explains how to use the managers within an app, only how to organize fonts. Can anyone explain how to use TypeFace, FontBase, RightFont, etc. Like I said, adding and organizing looks easy. But how are these used within the Affinity apps themselves to select and set type? Thanks.

INTERESTING!!! So you have the same issue with Affinity's listing of Font Book user font collections?!? As I've said in previous posts, I'm not seeing the duplication of fonts in any other app other than Affinity apps, and all Affinity apps are showing the same duplicates within the font collections, which if viewed, then corrupts the All Fonts list as well! Yeah, in the old days, I used to use Suitcase (years ago, and even before OSX), etc. to only have my main fonts showing in my main apps. But with Big Sur/OS11 especially, it is no longer possible to do that. OS11 puts 355 mandatory fonts into the System/Library/Fonts and Supplemental folders that can't be deactivated. Makes for a very congested fonts menu! I have for a few years used Font Book's user-designated Collections, and with no problems. I was using them routinely in Affinity apps as well and was not aware of the problem I'm now seeing. For me it started with what appears to be OS11 and/or Affinity 1.9.x. But interesting that you see the same thing! I haven't used a font management app in years, so am not aware if using one can overcome this issue. Might be worth the very hefty price they now ask for one of those previously inexpensive utilities if it could fix this problem. Maybe someone who uses a font management utility could answer that. The way it is right now with OS11, scrolling through several hundred mostly useless fonts to try to set type in client docs/images is really not pleasant at all. Thanks for the input, Bruce! At least I now know that I'm not alone in seeing this issue (and totally cursed!!). And it does raise the question, where is Affinity getting its Font Collection listing from? Or why is it "corrupting" Apple's Font Book's user Collections?

@Jon P Just to clarify, it does not appear that the issue involves the Futura fonts that were originally creating an issue in some docs due to being very old (now replaced). All fonts within any of my font Collections show up as duplicated when viewed under the Affinity Font Collection view, then subsequently corrupt the All Fonts list view as well after having viewed the collections list (see attached pic of one of the collections with every font containing duplicate styles). I have also tried deleting the macOS font caches using Terminal. I also downloaded a trial of Suitcase and used their utility to delete font caches. The problem persists. This suggests that Affinity apps appear to be referencing their own font cache, or at least a Font Collections cache. The Affinity apps are the only ones having this problem of a "corrupt" font list, especially font collections. Hopefully you guys can suggest a fix. Thanks.

Just to be sure, I just deleted my copy of Publisher (Affinity Store) and downloaded a fresh copy, deleted/moved all the prefs (App Support and Prefs), and restarted with Control, resetting everything. I still get the same issue. Under All Fonts, I get the correct number of styles within the problematic fonts. But when I look at a font collection, those same fonts then show more than double the number of actual styles, and then subsequently corrupt the All Fonts listing. I also tried clicking the Reset Fonts in the app/prefs. Didn't fix anything. This suggests that Affinity is storing the font info somewhere for all Affinity apps since they all are showing this problem?? If not, where are the apps getting the info for fonts and collections? While I have little expertise in this area, the actual font collections are correctly shown in all apps that use Apple's Font viewer/listing window, such as in Mail, Pages, Numbers, BBEdit, etc. That leads me to believe that the macOS file/cache of the fonts and collections is correct, but somehow the Affinity apps are retaining or showing a corrupt version. As said many times, I really need to find a fix for this so that I can get back to client work. Trying to scroll through the large number of Big Sur fonts just to get to our clients' set of fonts is a real PITA! And if uninstalling the app doesn't fix it, there must be a way to fix Affinity apps' font collections cache.

Chris, yes, this was a one-off. My concern is what did that Terminal session do? The nature of the commands are beyond my knowledge in Terminal, so was hoping you guys might understand what it was doing and if anything "bad" happened as a result. Just seems strange/suspicious that a crash in Photo would initiate a Terminal session of any kind! Thanks.

@Jon P Thanks. Big question is how do I fix it? This is really slowing down my work in all my Affinity apps not being able to use font collections, especially after Big Sur having installed so many never-used fonts. A real PITA to get to my frequently used fonts. There must be some way to manually flush/delete Affinity's cache of font collections? The regular All Fonts display is correct, it's just Affinity's display of font collections that's wrong/corrupt. And once I view those collections, it then corrupts the All Fonts listings as well. And as described in the previous posts, this isn't the case in non-Affinity apps -- they show the font collections correctly. So I'm assuming Affinity apps seem to have their own cache for the collections.

@Chris B Any progress on this?

@Jon P Any progress on this issue?

Forgot to answer your question. NONE of them can be turned off!!! They now put those fonts into the System/Library/Fonts directory and move your personally installed fonts into the Library/Fonts and ~/Library/Fonts folders. The workaround that I finally figured out is to use Font Book's font collections with only your own fonts/styles. In the collections, you can Disable the numerous OS11 installed fonts and styles. Helps clean up an otherwise huge font dropdown containing these new "permanent" fonts that a person might not ever use.

Thanks Bruce. As you can read in the other thread in Publisher Bugs (with much more detail), we've tried that. The permanent/locked Futura installed by OS11 is a very limited one with only a couple actual styles. As you can read in the other thread, since cleaning out the "antique" Futura fonts I used to use for many, many years, then installing the two new good Futura font families (reg and cond), I now have all the various styles available. And when I load an Affinity app, when I first look at the All Fonts listing, it is correct, listing 17 Futuras, 10 Fut Cond and a single Impact. The 17 Futuras includes a couple duplicates from Big Sur in the All Fonts list, so easy to discern. But in my font collections created in Font Book (newly edited, created, etc.), in Affinity apps (but not any other) those font collections show up to 41 styles of Futura, a bunch of Condensed, up to 4 styles for Impact, etc. I can use the Reset Fonts within Affinity and a whole bunch of other things as per the other thread, and it still shows wrong in Affinity apps. And worse, once I open a font "collection" in Affinity apps with the dups, when I go back to the All Fonts view, I now have even more styles!!! Amazing!! Never seen this since the fist Affinity apps, so don't know what's going on. Only started with my switch to the new iMac with Big Sur, coming from Catalina, so thinking it must be related. But I have gone down the path of looking at OS11's built in fonts and isolated that issue. And as I said, none of the other apps that show collections have this issue. Just Affinity apps. And as Jon has said on the other forum, Affinity apps are supposed to be flushing each launch, but they aren't flushing the collections listings. I had really hoped one of us old timers had seen this before and had a quick cure!

@Callum We're working on this over on the Publisher Bugs on MacOS. We've found that the issue is that since my update to OS11, my Affinity apps (1.9.3 and newer betas) are not clearing/renewing the font Collections cache upon loading. Thus, I'm getting multiple duplicates of several fonts including the key font of Futura. As you'll read, I replaced a very old set of Futura font families with a new pair (Futura and Futura Cond), but none of the Affinity apps will clear the old styles and also show numerous duplicates of several of them in the Collections groups of fonts. If you have any ideas on how to fix this issue, sure like to hear them! Very frustrating since I cannot do a lot of client work until I get this resolved since I use the main affected font (Futura) and another problem one (Impact) extensively for several clients. Thus every doc and artwork I open is messed up until I can go through and "fix" the fonts, styles, etc. But with the font menus in Affinity apps showing 2-3 times the right number of styles, pretty tough to be sure I select the right ones to replace and update the files! Very strange issue!

I uploaded the old Futura set that had been in use for years (without any significant prior problem), plus the new set installed due to this issue and Big Sur. Also uploaded an old Impact, since that one does the same thing (shows anywhere from 3-4 styles in collections). Yes, I'm at a loss. The Apple apps and others that use Apple's font interface all show the collections correctly. And Affinity apps initially read the All Fonts correctly as well, until I open a collection. But when I switch to a font collection in Affinity apps, everything goes bad. The collection shows dups, plus then All Fonts subsequently shows even more dups. And often not even the same number of dups. Thinking that the collections themselves were corrupt, I even created a new collection, but that also shows dups in Affinity. I even deleted the com.apple.Recents.collection from the ~/Library/FontCollections. Didn't fix it. Somehow Affinity apps appear to be retaining old font info, even though the fonts are no longer on the computer (except in a zipped folder not in any Fonts directory). Really has brought my work to an almost stop since we have so much work that contains Futura and Impact, so hopefully can figure this out. Thanks. ----------- I also looked for any apps that are non-Affinity or don't use Apple's fonts interface, but I'm at a point where with OS11 all my non-Affinity graphics apps are in a legacy Sierra VM. Become dependent on Affinity for my modern apps! 😩

To further update, I have looked at Apple's apps and the font collections. They are all showing correct listings. It appears that only Affinity apps are not showing the correct updated font collections, and as mentioned above, once a "bad" collection is viewed, it also corrupts the All Fonts view list.

FWIW, I did try in Font Book to remove Impact from one of my collections, then add it back in. Still had same issues in APub. I did a Reset Fonts each time. I also tried to create a new collection in Font Book, adding Futura and Impact, but in APub the collections once again had a lot of duplicates. Pretty clear that Affinity apps are apparently not handling collections correctly for some reason.

Yes, Big Sur! Came with my new iMac, so having several issues due to the "upgrade". That's how my problem started and now I'm virtually out of business doing client work until I can get this resolved. You can see in the first pic above from APub that after doing a Reset Fonts in APub, initially the All Fonts view showed the correct number of styles within Futura (17) and Futura Condensed (10). The 17 showing in Futura did include a couple duplicates that come from the fixed/non-removable Big Sur Futura fonts. But what I had done in Font Book was to modify my "collections" to not include (disable) the Big Sur versions of Futura in those collections, thus showing only the new Futura styles in the personal collections (can't disable them in the All Fonts section, but can in the collections). However, as you can see in pic 2, when I then subsequently selected the My Favorites font collection from within APub, suddenly I had 29 and 20 styles in Futura and Condensed. Amazing! Even more puzzling is that having done that, when I then went back to All Fonts view, where I had just shown only 17/10, I now have 41 showing and the Condensed family is not even showing anymore! Something is truly broken in Affinity apps handling of fonts. I also have watched another one I use a lot, Impact. I've never had more than the single stock Impact font installed for years. If I do the Reset Fonts in APub, then look at Impact in All Fonts, it shows only 1 style (correctly). But when I go to one of my font collections, it shows 3. Then back in All Fonts it now shows 4 duplicates for Impact! Don't think that's how it should work. I've searched the web and Affinity Help for how to refresh the font cache for Affinity but cannot find anything anywhere, other than the Reset Fonts in prefs. And that seems ineffective or broken. At the moment, all my client work is at a standstill since I use Futura and Impact for a lot of work including embedded and linked logos and other graphics. If I can't replace the previous versions with what I know are "real"/new versions, all those documents will go crazy. That's how this all started. I had opened one with the old Futura still installed and one of the Text Styles in APub that used a Futura font as a character style was showing incorrectly. When I tried to edit the text style, the entire text frame went corrupt with text overlaying itself, totally illegible. Couldn't even change the font or style manually. That finally led me to buying the new Futura package to replace my ancient package (from back when they chiseled out the fonts as you typed!! 😂). But until I can figure out how to "flush" Affinity's font lists, I'm dead. No work can get done since I use those fonts so much for many clients. And it's not like I'm using any 3rd party font manager (like I used to years ago with System 7 and early 10, etc.). Just using Apple's Font Manager, so nothing trick there. Affinity's font lists just seem corrupt and for some reason are not rebuilding, especially the Collections parts. I had hoped one of us old-timers with Affinity and betas had run into this before. Hopefully Monday someone at Affinity will know how to cure this so that I can get back to work! Frustrating to say the least!