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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment