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 (44)

  1. 9b6d64e72f6400cde35b17a2033e9920?d=mm


    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.

  2. 413ddb36c6a988bdd3b4c69d5fbc3adf?d=mm


    Feb 06, 2020 06:14

    2020.1.0a21 same problem.

  3. E3ab6c31f9eb22bbd569dd2d409a33ac?d=mm


    Feb 05, 2020 10:18

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

  4. 7c7e2aaf4c7e5f02c349df88962c1162?d=mm


    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)

  5. 52e43349d432df73882657fcae43aa05?d=mm


    Feb 03, 2020 10:23

    Sorry for the double post as there is no way to edit, however downgrading back to 2019.3.0.b11 fixed the issue for now. Just a heads up.

  6. 52e43349d432df73882657fcae43aa05?d=mm


    Feb 03, 2020 10:00

    Im getting the same issue. The only change is that I updated my projects Editor from 2019.3.0b11 to 2019.3.0f6. Been doing this the whole project on the older unity. Just today after updating I am getting this error and cannot use/import my meshes with animation clips.

  7. C5062031f24d448cf25924e738d211fa?d=mm


    Feb 02, 2020 10:44

    The workaround of importing via an earlier version of Unity didn't work for me – same error occurs when bringing the imported asset back into the 2019.3.x project. The best way around this is to split the multi-animation clip .FBX file into multiple single animation clip .FBX files. Where there is only one clip, I didn't see the problem and the animations imported fine for me.

    Was ok for me as I had a low number of animations – can imagine that would be annoying with complex characters, etc. until the Unity team can fix this one.

  8. 59342fef6207de40640be85647522900?d=mm


    Feb 02, 2020 01:55

    for anyone who got those kind of trouble just import your fbx in an older Unity version (2019.2.x worked for me) and export it as a package, then just bring it back in 2019.3 and it should go well (at least worked for me

  9. Bf15e06e613baf4c1313c7b268a51050?d=mm


    Feb 01, 2020 23:11

    Same :')

  10. Af06b5e7e937747db5f1af8f1b4bf5d1?d=mm


    Feb 01, 2020 19:15

    Same here.

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.