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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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.