Secondary monitor scaling issue

Hi,

I just installed NCrunch on my work laptop and are experiencing issues with the coverage markers. When clicking a marker to see what tests are covering a line the window starts to become unreadable.

Working setup on laptop
3840 x 2160 at 250% scale

Non working setup on secondary screen
2560 x 1440 at 100% scale

If I change the scale to 225% on the secondary screen the NChrunch windows look normal but everything else is too big and practially useless to use the monitor.
Then the covering tests window start to go weird at around 175%. It is readable at 150% but at any lower scale the font is bigger than the grid lines and they overlap.
See screenshots below:

Hover over coverage marker:
https://ibb.co/1XsQmXY

After click on coverage marker:
https://ibb.co/NW7kqBD


Versions:
VS 2022 17.12.1
NCrunch 5.11.0.1
Windows 10 Enterprise 22H2

This looks similar to this older issue but for other windows (the images have expired, so I cannot verify):
https://forum.ncrunch.net/yaf_postst3465_UI-scaling-issues--Hot-Spots.aspx
https://forum.ncrunch.net/yaf_postst3444_Update-call-to-action-popup-doesn-t-render-well.aspx

I see that this also applies to the "Test starts on this line" marker.

Hi, thanks for sharing this issue.

The tool tip window establishes the scaling factor from the monitor containing the control when it gets opened.

Unfortunately, we've seen situations where some versions of Windows/.NET don't seem to report this correctly internally. I'm not sure if the issue is due to something not right in the installed version of .NET, or the version of Windows itself, or potentially both.

Check that you have all updates installed for both your O/S and .NET Framework (under VS2022 we're usually on .NET Framework v4.8).

... Could you also confirm for me if adjusting the 'Optimize rendering for screens with different pixel densities' setting under your VS options (Environment->General) has any impact on this issue?

Remco wrote:... Could you also confirm for me if adjusting the 'Optimize rendering for screens with different pixel densities' setting under your VS options (Environment->General) has any impact on this issue?

That seems to have resolved the issue. I disabled the "Optimize rendering for screens with different pixel densities" and restarted. Now it looks like it should.
Thanks!