Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.2.0f2
Issue ID
955914
Regression
No
Controller velocity reporting with what seems to be last known value, rather than zero or correct value
Steps to reproduce:
1. Open the attached project
2. Open the Assets/Scenes/MainScene.unity scene
3. Play the scene (when Mixed Reality Portal is on)
4. Switch to InterationManagerPollingInput by pressing the "Space" inside the Editor
5. Observe, velocity on motion controller polling input seems to be giving the last good value instead of zero or correct value (Sometimes it does not give anything or NaN values)
Actual results: Velocity on motion controller polling input seems to be giving the last good value instead of zero or correct value(Sometimes it does not give anything or NaN values)
Expected results: Velocity on motion controller polling input should return the correct values or zero
Note:
Make sure you are running Windows 10 build 16257 or higher
Reproduced with: 2017.2.0f3, 2017.3.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment