Search Issue Tracker
By Design
Votes
14
Found in
2020.3.47f1
2021.3.22f1
2022.2.13f1
2023.1.0b11
2023.2.0a9
2023.3.0a3
Issue ID
UUM-32799
Regression
No
Incorrect resolutions when reading from the player using Screen.currentResolution on macOS
Reproduction steps:
1. Open the attached project “WrongResolution”
2. Go to File > Build Settings
3. Make sure that "Development Build", "Script Debugging" and "Wait for Managed Debugger" are checked and press “Build and Run”
4. When the Player prompts, attach the Debugger to the build through Console Window by pressing Editor and then the Player
Expected result: The used system resolution is reported
Actual result: A bigger resolution than the system is reported
Reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.2.13f1, 2023.1.0b11, 2023.2.0a9
Reproducible on: macOS 13.1 (Intel)
Not reproducible on: Windows 10
-
muppetpuppet
May 01, 2023 13:44
any progress on this,., I feel this is a larger issue than it being prioritized.
-
TheFalconeerDev
Apr 06, 2023 17:38
This also happens on windows 11 . I have multiple reports form players on various windows machines mostly with multiple monitors.
Built with latest 21 lts. Been reported as s seperate issue and forwarded to this.
I can confirm this also happens on windows.
And it will ends up your screencast (cursor ) on a camera with a RT.
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
- TextMeshPro Caret has an active raycast when TMP_InputField is non-interactable
- Shadows do not smoothly fade in when transitioning between real-time shadows and baked distance shadows
- [Android][Vulkan] The Color Channel of videos changes from RGB to BGR when streaming in the Player
- Post Processing SMAA breaks when HDR mode R11G11B10 is selected and Color Space is changed
- The "UnityWebRequest.result" of the "UnityWebRequestTexture.GetTexture" method changes when accessing "UnityWebRequest.downloadHandler" texture
Resolution Note:
The higher current resolution is only reported when the macOS display screen is set to HiDPI resolution (backingScaleFactor equal to 2), which renders content at 2x resolution. So current resolution is matching system rendering resolution, which in this case is 2x bigger and it is as designed.