Search Issue Tracker
By Design
Votes
1
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.2.5f1
2019.3.0a1
2020.1.0a1
Issue ID
1186348
Regression
No
[macOS] Cursor size is not affected by Cursor.SetCursor
How to reproduce:
1. Open attached project (CursorTooBig.zip)
2. Open "SampleScene" Scene -> enter the Play Mode
3. Exit the Play Mode -> select "CustomCursorBehaviour" GameObject
4. In Inspector's "Custom Cursor Behaviour" Component -> select "CustomCursorSmall" Asset
5. Enter the Play Mode
Expected result: Cursor size is affected by Cursor.SetCursor and stays the same using either of the Cursor Assets ( CustomCursorSmall or CustomCursorLarge)
Actual result: Cursor size is not affected by Cursor.SetCursor and Cursor Assets are shown in different sizes
Reproducible in: 2017.4.33f1, 2018.4.11f1, 2019.2.10f1, 2019.3.0b7, 2020.1.0a9
Notes: Only reproducible on macOS
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
Resolution Note (2020.1.X):
This is by design, custom cursors on macOS will be displayed at the size of the provided texture if possible. A workaround is to set the max size of the cursor asset to 32 in the inspector. Then any size of the cursor asset will be restricted to 32x32 size.