Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
2020.1.0a5
Issue ID
1185536
Regression
Yes
[macOS] Screen.currentResolution method returns incorrect screen resolution
How to reproduce:
1. Open user's attached 'screenresolution.zip' project
2. Maximize Editor window
3. Screen -> Log current Resolution
4. Observe Console's log
Expected result: Screen.currentResolution method logs correct resolution of Editor window
Actual result: Screen.currentResolution method logs incorrect resolution of Editor window
Reproducible with: 2018.4.0f1, 2018.4.10f1, 2019.2.7f1, 2019.3.0b5, 2020.1.0a5
Not reproducible with: 2017.4.32f1
Note: Not reproducible on Windows
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment