Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0b5
Issue ID
938142
Regression
Yes
UI scaling inconsistent in macOS editor between 2017.2.0a3- and 2017.2.0a4+ using Canvas Scaler's "Constant Physical Size" mode
How to reproduce:
1. Open QA-supplied project using Unity 2017.2.0a3 or earlier, load scene "REPRO"
2. Memorize or screenshot the Game view
3. Open the same project using Unity 2017.2.0a4 or later, load scene "REPRO"
4. Memorize or screenshot the Game view and compare with what was seen before
Expected result: Image (white rectangle) size stays the same.
Actual result: Image (white rectangle) is bigger in 2017.2.0a4+.
Reproducible with: 2017.3.0a2, 2017.2.0b5, 2017.2.0b1, 2017.2.0a4
Not reproducible with: 2017.2.0a3, 2017.1.0p2, 2017.1.0f2, 5.6.3f1
Regression introduced in: 2017.2.0a4
Note #1: The bug does not reproduce on Windows, only macOS editor (build works fine).
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
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
- Loading animations are hitching or stopping when using "SceneManager.LoadSceneAsync" to load new scenes
Resolution Note (2017.2.0f3):
low priority for the moment and defect found from the past. we may get back to it at some point but unlikely for the moment.