Search Issue Tracker

Fixed in 2020.2

Fixed in 2019.3, 2020.1

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

Asset Importers

-

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)

  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. Cf4e53a375fc651c54b01a87c1338447?d=mm

    mistergreen2016

    Feb 21, 2020 02:37

    It doesn't work in 2019.3.2f1 also.

  2. 18ae349dd2976c2dc25b5581d76df581?d=mm

    chorizo6457

    Feb 20, 2020 05:00

    I have the same problem here.

  3. 03053c9f839d1b04f88b79abbb730816?d=mm

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

  4. 7be4fc1fdcdb999cec475d9656144e36?d=mm

    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.

  5. 7be4fc1fdcdb999cec475d9656144e36?d=mm

    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.

  6. 5a28e52d6ed9b6edcfb3e03fec8210b5?d=mm

    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.

  7. 2f8e9aa5f2f90f47f7e952d72e50e343?d=mm

    peterparnes

    Feb 13, 2020 09:53

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

  8. 2f8e9aa5f2f90f47f7e952d72e50e343?d=mm

    peterparnes

    Feb 13, 2020 09:42

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

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.