Search Issue Tracker
Fixed in 2020.1.X
Votes
2
Found in
2017.4
2020.1
2020.1.0a18
Issue ID
1212108
Regression
No
[Linux] The default cursor is not hidden in Play Mode when using SetCursor() with CursorMode.ForceSoftware
How to reproduce:
1. Download and open the attached project "New Unity Project (33).zip"
2. Open SampleScene (Assets -> Scenes 1 -> SampleScene)
3. Enter Play Mode and hover the mouse cursor over the Game View screen
Expected result: Only the custom cursor is present on the screen
Actual result: Both the default and custom cursors are present on the screen
Reproducible with: 2017.4.36f1, 2018.4.16f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a22
Notes:
-The default cursor is absent as intended when using SetCursor() with CursorMode.Auto
-The issue is not reproducible on Windows and macOS
Comments (1)
-
Lemar76
Dec 20, 2020 22:48
Can confirm the issue with version 2019.4.12 and 2019.4.16 LTS
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2020.1):
set gdk cursor invisible when forcing software cursor in editor playmode