Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
0
Found in
2018.1.1f1
2018.2.0b1
Issue ID
1042946
Regression
Yes
InputTracking.GetNodeName results in null value
Fixes are making their way through our publishing process. This issue will be closed when the fixes are published in a public release
Steps to reproduce:
1. Download and open the latest attach project("nodebug.zip")
2. Enter Play Mode
3. Inspect "GetNodeStatesObject" gameobject or check console
Expected result: node names are listed
Actual result: node names are null
Reproduced on 2018.2.0b1, 2018.2.0b6
Not reproduced on 2018.2.0a8*, 2018.1.3f1*
Regression introduced in 2018.2.0b1
*these versions do not get the nodeIDs correct, leading to a single ID working, but all are duplicates. breaks on next patch where ids are correctly returned
FIXED 2018.2.5f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Add comment