joal Posted March 12, 2020 Share Posted March 12, 2020 I just was just able to successfully install and run Affinity Photo 1.8.1.610 beta. Great Job! Patrick Connor and Mark Ingram 2 Quote Link to comment Share on other sites More sharing options...
grunnvms Posted March 12, 2020 Share Posted March 12, 2020 So the problem was caused by fonts that were not is the standard Windows font directory. My very personal opinion is that fonts should be in that directory anyway, unless you're using some kind of font manager with its own directory structure. So I'm glad I moved all fonts that were in my personal font directory to the standard Windows font directory. Quote Link to comment Share on other sites More sharing options...
Mark Ingram Posted March 12, 2020 Share Posted March 12, 2020 1 hour ago, grunnvms said: So the problem was caused by fonts that were not is the standard Windows font directory. My very personal opinion is that fonts should be in that directory anyway, unless you're using some kind of font manager with its own directory structure. So I'm glad I moved all fonts that were in my personal font directory to the standard Windows font directory. We're not entirely sure what's causing the crash. We managed to reproduce it by frantically adding and removing fonts during application startup, but we don't imagine that's how our customers have been operating. Either way, doing that highlighted a problem in the code which we thought would be causing all these customer problems, so it's good to read this feedback! stokerg, joal and Leigh 2 1 Quote Link to comment Share on other sites More sharing options...
Ddraiggoch Posted March 12, 2020 Share Posted March 12, 2020 I can confirm that getting rid of the fonts in C:\Users\<username>\AppData\Local\Microsoft\Windows\Fonts\ and rebuilding the font cache does solve the problem. Thank you for your quick response and resolution with the beta Quote Link to comment Share on other sites More sharing options...
Staff Jon W Posted March 12, 2020 Staff Share Posted March 12, 2020 To all users who have experienced this problem: please don't delete any fonts or rebuild the font cache. The current beta should fix the problem without doing that. If it doesn't, please let us know! Thanks. Quote Link to comment Share on other sites More sharing options...
Ddraiggoch Posted March 12, 2020 Share Posted March 12, 2020 The current beta for all three applications have this fix? Quote Link to comment Share on other sites More sharing options...
Staff Jon W Posted March 12, 2020 Staff Share Posted March 12, 2020 Only Photo and Designer so far. Quote Link to comment Share on other sites More sharing options...
Mark Ingram Posted March 12, 2020 Share Posted March 12, 2020 14 minutes ago, Ddraiggoch said: I can confirm that getting rid of the fonts in C:\Users\<username>\AppData\Local\Microsoft\Windows\Fonts\ and rebuilding the font cache does solve the problem. Thank you for your quick response and resolution with the beta It'd be good if we could get a copy of the local fonts before you delete them, then we can try to reproduce what our customers have been experiencing (even though we think we've fixed the problem). Quote Link to comment Share on other sites More sharing options...
Ddraiggoch Posted March 12, 2020 Share Posted March 12, 2020 Yes I have sent through the list of fonts and the text file requested, i also made a copy of the folder before i delete them but at this moment it is the only way i can get publisher to open. Mark Ingram 1 Quote Link to comment Share on other sites More sharing options...
Mark Ingram Posted March 12, 2020 Share Posted March 12, 2020 32 minutes ago, Ddraiggoch said: Yes I have sent through the list of fonts and the text file requested, i also made a copy of the folder before i delete them but at this moment it is the only way i can get publisher to open. That's great - so Publisher will still crash with that folder of fonts? We may have another way to reproduce this bug - thanks. Quote Link to comment Share on other sites More sharing options...
Ddraiggoch Posted March 12, 2020 Share Posted March 12, 2020 Yes if that folder has fonts in it publisher will take many attempts to open. Mark Ingram 1 Quote Link to comment Share on other sites More sharing options...
grunnvms Posted March 12, 2020 Share Posted March 12, 2020 2 hours ago, Mark Ingram said: It'd be good if we could get a copy of the local fonts before you delete them, then we can try to reproduce what our customers have been experiencing (even though we think we've fixed the problem). You had that from me as well. So after I send you all that information, I copied the font files from my personal directories to the standard windows font directory (install for all users), removed the registry entries for those personal fonts, and deleted them in the personal directories. I then rebuilt the font cache. After this the standard 1.8 photo worked fine. Mark Ingram 1 Quote Link to comment Share on other sites More sharing options...
joal Posted March 13, 2020 Share Posted March 13, 2020 Apart from any workaround and beta version, is there any guess of when an updated production version of Affinity Photo 1.8 plus Publisher and Designer might be available? Quote Link to comment Share on other sites More sharing options...
Staff Leigh Posted March 16, 2020 Staff Share Posted March 16, 2020 On 3/13/2020 at 8:26 AM, joal said: Apart from any workaround and beta version, is there any guess of when an updated production version of Affinity Photo 1.8 plus Publisher and Designer might be available? The Affinity Store retail update should be available very soon stokerg, Ddraiggoch and trevordl 2 1 Quote Link to comment Share on other sites More sharing options...
sDuccio Posted March 16, 2020 Share Posted March 16, 2020 Hi there, I've encountered the same issue since I've updated AP to 1.8. This is a workaround I have not read any mention about: run the program using the gpu processor (NVIDIA in my case) and not the default processor (usually the integrated Intel). It starts without any crash. Unfortunately it's not the solution. Quote OS: windows 10 home 64 bits Lenovo core I7 6700HQ 8Gb Ram Nvidia GTX 950 4 gb Memory SSD 256Gb HD 1TB 5400 rpm Link to comment Share on other sites More sharing options...
BobDaBilder Posted March 16, 2020 Share Posted March 16, 2020 I followed grunnvms advice and was able to go from both Photo and Designer crashing on startup to both loading successfully - Thank You. My problem with fonts was caused by having older versions of Adobe Reader and Adobe Elements. When I uninstalled the Adobe products the uninstall caused all kinds of fonts to be deleted, or not found. Rebuilding the font cache was a good long term fix for my system. I did not have any of the local fonts that others have reported. Patrick Connor and Leigh 1 1 Quote Link to comment Share on other sites More sharing options...
Staff Leigh Posted March 18, 2020 Staff Share Posted March 18, 2020 I just wanted to let everyone know that we have released the new update, 1.8.2, that fixes the issue users were having where the app wouldn't get past the loading screen because of fonts. If you purchased the app from the Affinity Store you can download the update from: https://store.serif.com/update/windows/photo/1/ https://store.serif.com/update/windows/designer/1/ https://store.serif.com/update/windows/publisher/1/ If you purchased the app from the Microsoft Store the update will be available to download from the updates section. joal 1 Quote Link to comment Share on other sites More sharing options...
joal Posted March 18, 2020 Share Posted March 18, 2020 21 minutes ago, Leigh said: I just wanted to let everyone know that we have released the new update, 1.8.2, that fixes the issue users were having where the app wouldn't get past the loading screen because of fonts. Thanks a lot. I installed the new version 1.8.2 and found it working. Great job! Leigh and Mark Ingram 2 Quote Link to comment Share on other sites More sharing options...
trevordl Posted March 18, 2020 Author Share Posted March 18, 2020 Thanks very much 👍 all apps working on my pc. joal, Mark Ingram and Leigh 2 1 Quote Link to comment Share on other sites More sharing options...
AnthonyN Posted March 21, 2020 Share Posted March 21, 2020 I just wanted to say thank you for fixing this problem so quickly and also for the way you interacted with us all. Everything works now. Great stuff. joal and Leigh 2 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.