Setting custom dpi on Windows 10 crashes Affinity

[VolkerMB]

Hi there!

While 1.10.x and 2.0.4 do work fine at my end with setting custom dpi to anything but 100/125/150/175%, the new 2.1.0 doesn't. That is a step backward.

The Affinity apps do start despite having set Windows 10 to a custom dpi value, but the moment I want to call the colour dialogue in Affinity the apps crash without any warning or any crash report. The are also reports here in the forum that it does happen with the gradient tool, too.

Would be highly appreciated if this regression could be fixed with the next version/update.

Best, Volker

[Callum]

Hi VolkerMB,

I'm struggling to recreate this crash here, just to clarify are you using the display scaling slider or setting a custom value using the advanced scaling setting? If you are are using a custom value which value are you entering?

Thanks
C

[AlainP]

Probably the same problem I had in Windows 11 reported here. I was using a custom setting of 115%.

Removing custom DPI setting fixed the issue, but it shouldn't be.

[VolkerMB]

On 5/30/2023 at 1:34 PM, Callum said:

Hi VolkerMB,

I'm struggling to recreate this crash here, just to clarify are you using the display scaling slider or setting a custom value using the advanced scaling setting? If you are are using a custom value which value are you entering?

Thanks
C

Hi @Callum,

thanks for looking into that.

Some infos about my system: Windows 10 22H2 (built 19045), Intel i7-7500U, 16 GB RAM, nVidia Geforce 940MX with driver version 531.79, Windows custom scaling set to 115%.

The same laptop worked fine with Affinity 2.0.4 and still does with 1.10.6, but crashes with 2.1.0 without warning or crash report as described initially.

Best,
Volker

 

[VolkerMB]

@Callum

Hi there!

One more thing: I've installed Affinity 2.1.0 on another PC with an AMD card (RX 5700xt) and set the display scaling to 115%, too. Result: no issues. So, with my devices the crashes happen only on the nVidia machine.

Best,
Volker

 

[Callum]

Thank you for the extra info, we are currently investigating this internally but are having difficulties recreating this on our machines here in the office. I should hopefully have an update on this issue soon.