Police style is missing on existing document with Affinity Photo 2.5.0

[L.G.]

Bonjour,
Vous trouverez sur l'image jointe un condensé des explications que j'espère être suffisamment claire quand j'ouvre un modèle.
La "signature" était correcte avant la mise à jour en version 2.5. Il semblerait que le style de la police soit effacée sur la nouvelle version.

Merci de bien vouloir faire le nécessaire afin de corriger ce léger bug.

Laurent


Hello
You will find in the attached image a summary of the explanations which I hope will be sufficiently clear when I open a model document.
The "signature" was correct before the update to version 2.5.
It seems that the font style is deleted on the new version.

Please do what is necessary to correct this slight bug.

 

Processeur    Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz   2.21 GHz
Mémoire RAM installée    32,0 Go (31,8 Go utilisable)
Type du système    Système d’exploitation 64 bits, processeur x64

Édition    Windows 10 Famille    Version    22H2
Build du système d’exploitation    19045.4412
Expérience    Windows Feature Experience Pack 1000.19056.1000.0

 

 

 

[Lee D]

@L.G. Our developers are investigating font related issues with our 2.5 update. For the moment you can revert to the previous version (2.4.2) using the links below.

• https://store.serif.com/update/windows/designer/2/
• https://store.serif.com/update/windows/photo/2/
• https://store.serif.com/update/windows/publisher/2/

We also have a new beta available 2.5.2(2478), if you can try this to see if the issue still exists, we can update our reports. If you haven't tested a beta before you can signup here.

There's also another forum thread reporting the same issue using the same screenshot as you.

 

[Affinity Info Bot]

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.