Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2018.4
2020.2
2020.2.0b2
Issue ID
1279753
Regression
No
"type is not a supported string value" error appears in the console window when selecting multiple FBX models
Reproduction steps:
1. Open the user's attached project "Bug Test.zip"
2. In the Project window select the "it_avatar_test_all_skin.FBX" model
3. Hold the shift button and select the "it_avatar_test_all_skin_lods.FBX" model
Expected result: "type is not a supported string value" error does not appear in the console window when selecting multiple FBX models
Actual result: "type is not a supported string value" error appears in the console window when selecting multiple FBX models
Reproducible with: 2018.4.27f1, 2019.4.9f1, 2020.1.5f1, 2020.2.0b2
Note:
- Workaround: The issue no longer reproduces when deleting "it_avatar_test_all_skin.FBX.meta" META file from the Assets folder
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
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
- Editor crashes after entering long Asset name and pressing "Force Quit" in "Moving file failed" pop-up
- Long strings are not truncated in the Assistant search results list
- The Editor freezes indefinitely when copy pasting large amounts of characters into New Scaler Profile Name field in the Adaptive Performance Settings
Resolution Note (fix version 2021.1):
Fixed in 2021.2.0a5
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b12