Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
7
Found in
4.1.5f1
Issue ID
546969
Regression
No
MousePosition offset after Screen.SetResolution() in OSX standalone widowed mode
Steps to reproduce :
- import the project attached
- build for standalone OSX
- run the scene and notice the mouse offset
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
baopham
May 08, 2017 23:30
This happens to me as well. On Windows platform. Unity 5.5
andyz
Jan 23, 2015 11:12
Probably related - exporting to win7, resizable window can sometimes end up showing wrong mouse coordinates after the window is re-sized