Search Issue Tracker
Fixed in 5.3.6
Votes
2
Found in
5.3.6p1
Issue ID
817286
Regression
No
Cursor is not visible in editor window
Using Unity editor on Windows tablet, mouse cursor is not visible, but can select or hover over editor's UI elements. Cursor disappears when using touch input in startup project wizard. Selecting or creating a new project with touch input and launching editor, mouse cursor hides.
Issue does not happen, when project is launched with physical mouse or using touch pad.
Reproducible on all Unity 5.3, 5.4 versions. Currently checked with 5.3.6f1, 5.4.0f2.
Reproduced on Surface 4 tablet.
Repro steps:
1. Launch editor. Project wizard opens.
2. With touch input open or create a new project.
3. Observe that mouse cursor is not visible, but it is possible to click on editor's UI elements.
Comments (2)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
mishli
Apr 03, 2019 00:20
I have this same issue on my touchscreen dell laptop. The same issue also happens with Chrome. There it can be fixed by disabling 'hardware acceleration in settings. My research said it was an openGL issue. Could this also be the problem in unity?
irve
Jan 06, 2019 20:57
Had the same problem with a touchscreen laptop after a Windows Upgrade. Running once in Aministrator mode fixed it.