Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4
2019.4.24f1
2020.3
2021.1
2021.2
2022.1
Issue ID
1348502
Regression
No
Importing a FBX model will incorrectly strip a suffix from Node Name
How to reproduce:
1. Open the attached project "NodeNameTruncation.zip"
2. Expand the in the Project View
3. Observe the names of the child elements
Expected result: The names are 'One(1)', 'Two(2.0)' and 'Three(Three)'
Actual result: The names are 'One', 'Two(2.0)' and 'Three(Three)'
Reproducible with: 2018.4.34f1, 2019.4.29f1, 2020.3.14f1, 2021.1.14f1, 2021.2.0b3, 2022.1.0a1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
Resolution Note (2022.1.X):
"(1), (2), (3)" form legacy behavior for identifying duplicates in the FBX format - this is inherent to the format, and something not designed by Unity. When reading the node, the FBX SDK strips the postfix & registers that node as a duplicate. In this regard, Unity behavior is consistent with other DCC FBX-SDK based tools (Maya/Max), which also strip the extensions on read.
This is not the case for files generated using newer version of the FBX SDK which no longer use "(1), (2)" etc. to identify duplicates.