Search Issue Tracker
By Design
Votes
7
Found in
2018.2.0f2
Issue ID
1079788
Regression
No
Unity WebGL is not "DPI Aware"
To reproduce:
1) Create new project
2) Add some high font sized text
3) Build and run for WebGL
4) Compare results on a low DPI and high DPI monitor
High DPI monitor is blurrier compared to low DPI one
Reproduced in 2017.4.4f1, 2018.2.7f1
Comments (5)
-
fkorsa
Apr 19, 2020 19:14
Yep, 2019.3.8f1 and I can still reproduce this issue (Screen.Dpi returns 0 for WebGL builds).
-
jeffweber
Feb 27, 2020 15:19
To be clear, for me, in 2019.3.3 Screen.Dpi always returns 0 for WebGL builds.
-
jeffweber
Feb 27, 2020 15:18
I'm currently seeing this issue in Unity 2019.3.3
-
Kamyker
Sep 22, 2019 04:26
It's fixed in 2019.3 beta.
-
JETom
Dec 17, 2018 15:40
This issue appears to be linked to the system’s scaling option for high-resolution screens. The resolution of the build is divided by the scaling factor, where 2160p becomes 1440p at 150%, 1080p at 150%, 864p at 200%, etc.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2019.3.X):
This is a feature request. We are actively working on it. Until that feature is released, this is by design.