Hi,
I just installed v3.0.16 and many of the fonts are either too large or too small.  I'm running on Win10 at 3840x2160 with 150% scaling.

In the image, the text in the Log Files column gets cut off at the bottom also in the stats at the bottom of the window.  In the settings dialog the font is even larger and more cutoff, yet on the property pages the font is very small, completely unscaled.


It seems like the ListView control isn't scaling correctly wherever it's used:


If I uncheck Enable dynamic display resolution scaling, the fonts do fit, but everything is blurry and low-res due to hidpi compatability mode.
If I uncheck the DirectX option, the fonts are proportionally correct, but unscaled, so everything is very very small and there aren't any options to set those font sizes.



Highlight is also affected by this issue:
Before

After


I've reset the settings back to the installation defaults and also tried deleting the LogViewPlus setting folder, but neither helped.

I just want to give you a quick update on this problem.

We have done some additional testing and have found issues in Windows 10 and 11.  These issues seem to have been introduced after v3.0.8, so the recommendation for high resolution settings at the moment is to install version 3.0.8.

The problem seems to be something DevExpress changed between v22.2.3.0 and v22.2.5.0 as this was the primary DPI related change between LVP v3.0.8 and v3.0.16.  It is currently unclear what the change is or how to work around it.

The Win10 issues appear to be more severe - especially with DirectX enabled.  Win11 issues only appeared when testing on a single high resolution monitor.  This is likely due the the settings of the primary monitor.

This is a high priority issue for us and we hope to have a fix out soon.

Thanks! I can confirm that the scaling in 3.0.8 is correct when the DirectX option is disabled.

This issue has now been addressed in LogViewPlus 3.0.21 currently available as a BETA release.  We are looking to push this version to a full release later this week.  

During testing, we found it best to disable DirectX rendering.  This will be the new default setting, but you may need to modify it manually if it has been set previously.

Apologies for the delay in addressing this issue.  We made two mistakes: the 3.0.16 release was inadequately tested for DPI issues and we miscategorised the initial bug report as a known issue rather than a regression.  We will watch out for those mistakes in future.

Thanks for your help!

Toby 

I can confirm the beta works for me with DirectX off.
Thanks!

Glad to hear it - thanks for letting me know!

Btw - you win the award for best forum name.  Makes me laugh every time.