Thanks Tori - that's an interesting point.

Given that LogViewPlus can be dragged between monitors with different scaling options, I am not sure that disabling the setting is the right thing to do.  Instead, I think we could add a warning if the option is selected when the current display is scaled to say something like, "DirectX rendering may not scale properly on high resolution displays."

Thanks for the suggestion!

Toby

I can confirm that the beta works fine for me when enable dynamic display res scaling is ON and DirectX is OFF - I'm good thanks!

(Just in case you wanted to know, it still does NOT work when DirectX is on.  If I were you guys I'd consider disabling DirectX enhanced rendering if the scaling in windows is set high.  You know someone in the future will go in and check something that says "enhanced" and you'll continue to get support posts)

Glad to hear it - thanks for letting me know!

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

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

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 

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

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.

I'm using 3 screens, all the same resolution and scaling. Windows ver 22H2 (OS Build 19045.3155)

I have these .NET runtimes installed:

> dotnet --list-runtimes
Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.18 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.18 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Running your script I get: .NET Framework Version: 4.8.1 or later

Just one screen on the laptop with the problem.  Thank you!

Thanks for the update.

How many screens are you using - just one?  If you are running multiple monitors, what are the settings of your primary display vs the target display?  Windows adjusts the application based on the settings of the 'primary' monitor.

LogViewPlus is a WinForms application.  WPF does not have this problem.