Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
Issue ID
1222562
Regression
No
[Asset Importer] Custom framerate error should only be logged when frame rate is used
Reproduction steps:
1. Import the attached file.
2. Look at console.
Expected result: No errors are shown when file has no animation / no frame rate is used.
Actual result: When importing FBX from MODO, the error "ImportFBX Errors:
Framerate was set to 0.00, it's been reset to 1.0." is shown when file has no animation / no frame rate is used
Existing Workaround: In Modo, use "Unity Static" preset. It does set properly the FBX global settings for "TimeMode" to default which will get rid of the error.
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
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
- Loading animations are hitching or stopping when using "SceneManager.LoadSceneAsync" to load new scenes
Resolution Note (fix version 2020.2):
Fixed in 2021.2.0a1