Windows DPI scaling causes blurry graphics unless disabled #1041

Closed
jameswilddev opened this Issue Mar 28, 2016 · 7 comments

Comments

Projects
None yet
3 participants

When Windows is set to use DPI scaling (in Windows 10: settings->system->display->change the size of text, apps and other items) Aseprite looks blurry. (bilinear filtered?)

broken

I can fix this by changing the compatability settings not to apply DPI scaling:

setting

I then have to use the GUI scaling option to make the GUI the same scale as the surrounding OS, but it then looks great:

fixed

I think the reliability of stylus input is improved by doing this too though it's somewhat subjective.

It might be possible to do this without requiring configuration by the user, as outlined in https://msdn.microsoft.com/en-gb/library/windows/desktop/dn469266(v=vs.85).aspx (modifying the application manifest)

@dacap dacap added bug windows labels Mar 28, 2016

dacap added this to the v1.1 milestone Mar 28, 2016

Owner

dacap commented Mar 28, 2016

Hi @jameswilddev, thanks for reporting this issue. I saw that you are (probably) using the Steam version, could you please try if this bug happens in the beta version?

It does unfortunately.

upload

dacap added the critical label Apr 12, 2016

When I enable the "Disable display scaling on high DPI settings" option, it stopped freezing on close.

Owner

dacap commented Apr 18, 2016

I've tested adding a manifest and it doesn't fix the issue. I'll be investigating what is missing yet.

Owner

dacap commented Apr 18, 2016

@vncastanheira I didn't know that the application freezing on close. Can you reproduce the problem? debug it? Or do you have a crash report?

Owner

dacap commented Apr 18, 2016

Done, the manifest really fixed this issue, but we need a specific value (True/PM) (that is compatible with Windows Vista, 7, 8, 8.1, and 10).

dacap closed this in 8775604 Apr 18, 2016

@dacap Since you fixed the DPI scaling, I will be testing the application in the next release.

dacap self-assigned this Apr 18, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment