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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.