Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
89
Found in
2019.3.0f6
2020.1.0a20
Issue ID
1215431
Regression
Yes
NullReferenceException is thrown when inspecting a .FBX file with multiple clips and opening Animation tab
How to reproduce:
1. Open the attached 'project-1215431.zip' project
2. In the Project window select 'MultiClipSingleFile'
3. Observe the Console window
4. In the Inspector select 'Animation' tab
5. Observe the Console window
Expected result: NullReferenceExceptions are spammed in the Console window, the asset is broken
Actual result: No exceptions are thrown in the Console window, the asset is not broken
Reproducible with: 2019.3.0f6, 2020.1.0a20, 2020.1.0a21
Not reproducible with: 2017.4.36f1, 2018.4.16f1, 2019.2.20f1, 2019.3.0f5, 2020.1.0a1, 2020.1.0a19
Thrown exceptions:
1) NullReferenceException: Object reference not set to an instance of an object
UnityEditor.ModelImporterClipEditor.FindNextAvailableName (System.String baseName) (at <866e5e4337c74147a9a0249666f72660>:0)
2) NullReferenceException: Object reference not set to an instance of an object
UnityEditor.ModelImporterClipEditor.AnimationClipGUI () (at <866e5e4337c74147a9a0249666f72660>:0)
UnityEditor.ModelImporterClipEditor.OnInspectorGUI () (at <866e5e4337c74147a9a0249666f72660>:0)
-
Lorash
Feb 27, 2020 08:52
Voting disabled for resolved issues, thank goodness, I was worried there for a while.
-
zackblack
Feb 26, 2020 16:20
2019.3.3f1 came out today and this still isn't fixed. WHAT A SURPRISE.
-
omertr
Feb 25, 2020 18:46
Still not fixed in 2019.3.2f1 ....
-
Billygoatman123
Feb 25, 2020 02:29
I also got around this issue by importing the FBX file in 2019.2.11f1, organized the animation clips in the import settings, then I exported the model as a unitypackage. The custom unity package imported into 2019.3x as expected.
-
luciusponto
Feb 24, 2020 11:35
If you are really stuck and can't wait for the official fix, I found a workaround that worked for my case. Back up your project beforehand and try it at your own risk.
It involves creating a post processor for the model importer.
See steps and code to copy and paste in the Google doc:
https://docs.google.com/document/d/1aO0kTRX7ElshRNQ62hSPtjWMxJEtPzIb-_avQIHRZSw/edit?usp=sharing -
SaltwaterAssemnly
Feb 24, 2020 07:25
FYI Downgraded project to 2019.2.17.f1 and .FBX file import with anims works fine.
-
SaltwaterAssemnly
Feb 24, 2020 04:05
Had no issues until now. Tried to import an updated model with only 2 anims on it. And now project at a standstill :( When is the fix due?
-
trsh
Feb 23, 2020 12:47
Still ongoing 2019.3.2f1. Co moon Unity fix this please. This is a real blocker for lot's of game development pipelines :(
-
mistergreen2016
Feb 21, 2020 02:37
It doesn't work in 2019.3.2f1 also.
-
chorizo6457
Feb 20, 2020 05:00
I have the same problem here.
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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a1
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a26
Resolution Note (fix version 2019.3):
Fixed in 2019.3.4f1