Search Issue Tracker
Fixed in 5.3.6
Votes
0
Found in
5.3.4f1
Issue ID
788684
Regression
No
Custom Texture2D cursor is not shown in full-screen on secondary monitor
Steps to reproduce:
1. Download and open attached project "SecondDisplayCursor.zip"
2. Build standalone (including "Test" scene)
3. Play it in full-screen mode (secondary monitor)
4. Move mouse over the cube
Actual result: If the build is played on the primary monitor, everything works fine - moving mouse over the cube changes cursor.
If the build is played on the secondary monitor, nothing happens
Expected result: Consistent behavior in all monitors (mouse cursor changes when moved over cube)
Notes: Does not seem to be impacted by any other settings. Changing from full-screen to windowed mode with Alt+Enter, and then dragging it to other screen, making it full-screen again, change the behavior depending if its primary screen or not
Tested and reproduced on:
Windows 10
Unity 5.1.4f1, 5.2.4p1, 5.3.4p3, 5.4.0b15
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
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
wsessums
Oct 12, 2017 13:54
I am still seeing this behavior in 5.6.3p1 on Windows 10.