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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2020.2):
Fixed in 2021.2.0a1