DPI scalling issues on Windows

[MichalLytek]

The interface on my second screen with different DPI is awfully blurred.

On my main screen with 100% DPI, I have correct image:

When I have on my notebook LCD DPI set to 150%, I got this blurred image:

All I can do is to disable the scaling in Windows compatibility settings and have super small fonts on 1080p 15" screen 😞

[DanPristupov]

I can't reproduce this problem locally right now as it has happened that my system doesn't allow DPI changing.

I can setup W10 on my old laptop and try to reproduce the problem there. Or I can make some changes and send a private build to you, if you are willing to cooperate.

[MichalLytek]

You can count on me, I would be glad to cooperate 😉

[DanPristupov]

OK, today I'm busy releasing the 1.30 update, but hopefully will find time for that until 1.31.
Please drop me a message to winsupport@fork.dev, so I could send you the build.

[MichalLytek]

@DanPristupov
Something wrong is with your email:

You can find mine on my profile:
https://github.com/19majkel94

[DanPristupov]

Ouch. Can you open http://fork.dev?

It looks like it's too early to move my emails to the new domain then. Seems like some email servers still don't recognize .dev domain zone.

[MichalLytek]

Yeah, the website is working, only the email has been rejected.

[sm-g]

mirrored cursor is too smal on my 200% scaled monitor

expected:

[donjo9]

Still an issue in 1.45.4.0

[gratianlup]

@DanPristupov, I had the same issue with my WPF application that I'm seeing with Fork and the fix is to enable per-monitor DPI awareness in the app.manifest file, it is not on by default sadly.

  <application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings>
		<dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitor</dpiAwareness>
		<dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware>
    </windowsSettings>
  </application>

I have one display set at 100% DPI and one at 175% (4k screen). When Fork is moved from the 100 to the 175 one, the entire window, but especially text gets quite blurry because Windows just rescales the 100% output. That app.manifest change will have the window render properly at the new DPI.

Hope this helps,
A happy Fork user :)

[martinfalk]

My setup is the exact opposite. 150% dpi scaling on the main monitor (UI scaling looks good) and 100% dpi scaling on the second monitor (UI scale is way too large).
@DanPristupov Placing app.manifest by @gratianlup into the app-1.xx.x folder solves the issue for me. The UI looks properly scaled on both screens. Tested with Windows 10 v20h2.

[DanPristupov]

@martinfalk strange... Fork has the app.manifest file with the following content:

<?xml version="1.0" encoding="utf-8"?>
<assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1">
  <assemblyIdentity version="1.0.0.0" name="MyApplication.app"/>
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
    <security>
      <requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3">
        <requestedExecutionLevel level="asInvoker" uiAccess="false" />
      </requestedPrivileges>
    </security>
  </trustInfo>

  <application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings>
      <dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitor</dpiAwareness>
      <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware>
    </windowsSettings>
  </application>

</assembly>

Update: gosh!

Update2: no, this turned out to be a bug in VS UI which shows the selected manifest incorrectly. Fork does have the app.manifest embedded in .csproj:

[martinfalk]

Then it's weird that the manifest does not seem to be correctly embedded into the executable.
As I mentioned earlier, I had to manually put the file into the app-1.xx.x folder, that is %LOCALAPPDATA%\fork\app-1.55.5, and not the main folder %LOCALAPPDATA%\fork.