Search Issue Tracker
Feature Request
Votes
0
Found in
2021.3.33f1
2022.3.16f1
2023.2.4f1
2023.3.0b1
Issue ID
UUM-59184
Regression
No
"Screen.dpi" value is incorrect compared to the manually calculated value
How to reproduce:
1. Open the "IN_62437" project
2. Open the "SampleScene"
3. Open the “Test.cs” script and change the “monitorDiagonalInches” value to your monitor diagonal
4. Enter the Play Mode
5. Observe the Console
Expected result: "Screen.dpi" value is roughly (-+1) the same as the "Manual DPI" value
Actual result: "Screen.dpi" value is different more than 1 from the “Manual DPI” value
Reproducible with: 2021.3.33f1, 2022.3.16f1, 2023.2.4f1, 2023.3.0b1
Reproducible on: Windows 10 Pro
Not reproducible on: macOS Ventura 13.5.2 (M1)
Notes:
- Also reproducible in the Windows Standalone Player
- Also reproducible on the Android Platform
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
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team has determined this is a new feature request, as it would require new public APIs to expose all the new information mentioned in the report. We will investigate adding this functionality to future versions of Unity, but this will require a bit more planning on our side to determine the best way to add it.
Today we will be closing this case. Thank you again for taking the time to raise this issue, and please let us know if you have have further thoughts on this.