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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Add comment