Jump to content
You must now use your email address to sign in [click for more info] ×

Affinity Photo crashing when trying to search for a font


Recommended Posts

image.png.d59212724a2148ee91250068d533df40.png

Howdy, all! When trying to search for a font in the text tool with Affinity Photo (ver. 1.10.5.1342 on Windows 11 Pro), the app freezes for a second and then immediately crashes.
In order to reproduce, create a new file (My dimensions were 1189 x 841) and create a text element. Then double click to select all that text and, when searching for a font to replace it with, type in the font you're looking for, and it'll crash!

 

The workaround for this seems to be manually scrolling until you can find the font, however it is annoying for us with tons of fonts installed.

Link to comment
Share on other sites

As long as Microsoft does not provide a fix for the framework problem, the following solution is available if you still want to install the cumulative .NET updates.

Solution:
Open the directory in which the Affinity programmes are installed. As a rule, C:\Programme\Affinity\(Desinger ...Photo ...Publisher)
Search and open the .exe.config file (for example Designer.exe.config) with a text editor.
Search for "<add key="IsVirtualizingStackPanel_45Compatible" value="false"/>"
Replace the value true with the value false.
Save the file (administrative rights are required to overwrite!)
 

AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3296)
AMD A10-9600P | dGPU R7 M340 (2 GB)  | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) 

Affinity Suite V 2.4 & Beta 2.(latest)
Better translations with: https://www.deepl.com/translator  
Interested in a robust (selfhosted) PDF Solution? Have a look at Stirling PDF

Life is too short to have meaningless discussions!

Link to comment
Share on other sites

  • 5 weeks later...

Yes, but there seems there is a right better solution now.

There is a Microsoft NET Framework Update, that should fix this bug. Please download from MS the  NET Framework 4.8.1.

https://dotnet.microsoft.com/en-us/download/dotnet-framework/thank-you/net481-web-installer

 

AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3296)
AMD A10-9600P | dGPU R7 M340 (2 GB)  | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) 

Affinity Suite V 2.4 & Beta 2.(latest)
Better translations with: https://www.deepl.com/translator  
Interested in a robust (selfhosted) PDF Solution? Have a look at Stirling PDF

Life is too short to have meaningless discussions!

Link to comment
Share on other sites

On 10/27/2022 at 3:23 PM, Komatös said:

As long as Microsoft does not provide a fix for the framework problem, the following solution is available if you still want to install the cumulative .NET updates.

Solution:
Open the directory in which the Affinity programmes are installed. As a rule, C:\Programme\Affinity\(Desinger ...Photo ...Publisher)
Search and open the .exe.config file (for example Designer.exe.config) with a text editor.
Search for "<add key="IsVirtualizingStackPanel_45Compatible" value="false"/>"
Replace the value true with the value false.
Save the file (administrative rights are required to overwrite!)
 

It worked like a charm! Thank you!

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.