Search Issue Tracker

Fixed in 2020.2

Fixed in 2019.3, 2020.1



Found in



Issue ID




NullReferenceException is thrown when inspecting a .FBX file with multiple clips and opening Animation tab

Asset Importers


How to reproduce:
1. Open the attached '' 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)

  1. Response avatar

    Resolution Note (fix version 2020.2):

    Fixed in 2020.2.0a1

  2. Response avatar

    Resolution Note (fix version 2020.1):

    Fixed in 2020.1.0a26

  3. Response avatar

    Resolution Note (fix version 2019.3):

    Fixed in 2019.3.4f1

Comments (39)

  1. 03053c9f839d1b04f88b79abbb730816?d=mm


    Feb 26, 2020 16:20

    2019.3.3f1 came out today and this still isn't fixed. WHAT A SURPRISE.

  2. Db07513415458bdc1aa5f7afad2e638c?d=mm


    Feb 25, 2020 18:46

    Still not fixed in 2019.3.2f1 ....

  3. Fa0985026ba63bd17abee8f6a2b614d0?d=mm


    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.

  4. F478a09c13ac7edd16d915a25dcb03a9?d=mm


    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:

  5. Dd5d04f54945a127d2b650f84fb5e944?d=mm


    Feb 24, 2020 07:25

    FYI Downgraded project to 2019.2.17.f1 and .FBX file import with anims works fine.

  6. Dd5d04f54945a127d2b650f84fb5e944?d=mm


    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?

  7. Cfa5ea06880479fdca40d74c85767640?d=mm


    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 :(

  8. Cf4e53a375fc651c54b01a87c1338447?d=mm


    Feb 21, 2020 02:37

    It doesn't work in 2019.3.2f1 also.

  9. 18ae349dd2976c2dc25b5581d76df581?d=mm


    Feb 20, 2020 05:00

    I have the same problem here.

  10. 03053c9f839d1b04f88b79abbb730816?d=mm


    Feb 19, 2020 21:16

    They keep coming out with new updates and NOT fixing this. First 2019.3.1f1, and now 2019.3.2f1. meanwhile I CAN'T USE MY PROJECT IN 2019.3. Please fix this!!

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.