Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.6.0f3
Issue ID
911008
Regression
No
[UWP] Input Mouse axies return invalid values in the first frame after locking cursor
Steps to reproduce:
1. Open attached project "911008.zip"
2. Build "test" scene for UWP
3. Open VS solution
4. Build & Deploy on local machine
5. Place the cursor anywhere on the screen but the centre
6. Press left mouse button (without moving the mouse)
*cursor gets locked and mouse movement rotates the camera while holding down the button*
Expected result: Mouse X and Mouse Y axies return actual mouse input values (like in Editor)
Actual result: Mouse X and Mouse Y axies return invalid values in the first frame after locking cursor making cameras rotation to 'jump'
Not reproducible on Editor
Reproducible with: 5.5.3p3, 5.6.1p1, 2017.1.0b5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment