Search Issue Tracker

Fixed in 2020.2.X

Fixed in 2019.3.X, 2020.1.X



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. Resolution Note (fix version 2020.2):

    Fixed in 2020.2.0a1

  2. Resolution Note (fix version 2020.1):

    Fixed in 2020.1.0a26

  3. Resolution Note (fix version 2019.3):

    Fixed in 2019.3.4f1

Comments (40)

  1. zackblack

    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!!

  2. Haeferlkaffee

    Feb 17, 2020 20:09

    I cannot regress my project version far enough without it breaking other assets. This needs to be fixed immediately, this is the main file format for assets.

  3. Haeferlkaffee

    Feb 17, 2020 18:57

    Still in effect. Every new FBX's import tabs just floods the console with errors and animation information cannot be accessed. Test your builds before you release them, please.

  4. DusmigaisBebrs

    Feb 13, 2020 19:08

    When comes this great day, when Unity before publish their new releases will start testing own program? I am tired every time rolling back projects to older version.

  5. peterparnes

    Feb 13, 2020 09:53

    2019.2.21f is still ok and doesn't have the bug.

  6. peterparnes

    Feb 13, 2020 09:42

    Just wanted to confirm that this bug has NOT been fixed in 2019.3.1f1.

  7. Whirlwave

    Feb 07, 2020 05:25

    2019.3.0f6 here, same issue when trying to import .blend files directly (since internally it uses the .fbx importer anyway). Only feasible workaround that doesn't require a previous Unity install is to export multiple .fbx files (or in my case .blend files) each with one and only one animation, as mentioned in a previous comment.

  8. RandomPatty

    Feb 06, 2020 06:14

    2020.1.0a21 same problem.

  9. NVDaniel

    Feb 05, 2020 10:18

    Same issue. Making it very hard to progress! Opening in another version of Unity doesn't seem to help.

  10. SwatMessiah

    Feb 03, 2020 13:57

    same problem when i import an FBX with an NLA Strip it causes lot of errors (only in unity 2019.3.0f6)

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.