Search Issue Tracker
By Design
By Design in 2023.1.X
Votes
0
Found in
2019.4.39f1
2020.3.37f1
2021.3.7f1
2022.1.11f1
2022.2.0b2
2023.1.0a4
Issue ID
UUM-10518
Regression
No
[M1] Mouse position values are not correctly updated when project is built for Silicon macOS
Reproduction steps:
- Open the attached project
- Open the “/Assets/QA/Tests/KeyboardMouseBasic/ISX_KB_Mouse_Basic.unity” Scene
- Build And Run the project
- In the Player, move the mouse cursor to the lower-left corner of the screen
- Observe the “Mouse Pos” values
Expected result: “Mouse Pos” values are (0,0)
Actual result: ”Mouse Pos” values are (-59, 0)
Reproducible with: 1.1.1, 1.2.0, 1.3.0, 1.4.1 (2019.4.39f1, 2020.3.37f1, 2021.3.7f1, 2022.1.11f1, 2022.2.0b2, 2023.1.0a4)
Reproducible on: M1 MacOS 12.4 (21F79)
Not reproducible on: Intel MacOS 12.4
Note: This issue is reproducible on both Intel and Apple Silicon Editors on M1 Mac
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:
This is due to the slightly taller aspect ratio on the notched machines, the rendered area is pillarboxed so the negative number is the mouse moving "outside" the rendered area. This behaviour can be observed if you run the app windowed and move the mouse out of the window. Suggest if this affects users to clamp the mouse position in their code.
Resolution Note (2023.1.X):
This is due to the slightly taller aspect ratio on the notched machines, the rendered area is pillarboxed so the negative number is the mouse moving "outside" the rendered area. This behaviour can be observed if you run the app windowed and move the mouse out of the window. Suggest if this affects users to clamp the mouse position in their code.