joe_l Posted April 26, 2024 Posted April 26, 2024 The betas for AD and AP open fine. Reset was already made. Crash report attached. 6bb8d8fe-dca9-4a10-b987-144938457a0e.dmp Quote ---------- Windows 10 / 11, Complete Suite Retail and Beta
Staff Sean P Posted April 26, 2024 Staff Posted April 26, 2024 Hi joe_j Thanks for the crash report - from a quick skim it looks like the new Variable Font feature introduced in 2415 is causing Publisher to crash on startup. It could be down to it not liking a font you have installed, however I've passed the crash dump on to development for a better insight into what the issue might be! Had you already updated Designer or Photo, or are they still running 2402 (which doesn't have the VF changes)? Quote
joe_l Posted April 26, 2024 Author Posted April 26, 2024 5 minutes ago, Sean P said: Had you already updated Designer or Photo Yes, both of them without problems. VF works with AD 2.5.2514. Quote ---------- Windows 10 / 11, Complete Suite Retail and Beta
Staff Sean P Posted April 26, 2024 Staff Posted April 26, 2024 Hi joe_j It looks like you may have an affont file installed in your Publisher Beta which is causing the crash on startup, and unfortunately a Ctrl Run up will not clear it. If you go to %userprofile%\.affinity\Publisher\2.0 (Beta)\AffinityFonts\ and remove all the files from there for the time being you will be able to get back into Publisher. I'm going to get this logged with development and hopefully have a fix soon! Thanks for letting us know! joe_l 1 Quote
Staff Affinity Info Bot Posted April 26, 2024 Staff Posted April 26, 2024 An issue raised in this thread ("Installing AF Fonts will cause the app to crash, and then crash on launch with no way to Ctrl runup") has now been reported to the developers by the testing team (Ref: AF-2877). Thank you very much for reporting this issue to us. Quote
Staff Affinity Info Bot Posted May 2, 2024 Staff Posted May 2, 2024 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. Quote
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.