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

  1. Cfa5ea06880479fdca40d74c85767640?d=mm

    trsh

    Mar 02, 2020 18:08

    Ahhh, Fixed in 2019.3.4f1

  2. Cfa5ea06880479fdca40d74c85767640?d=mm

    trsh

    Mar 02, 2020 18:08

    But why it's marked as fixed, if it isn't?

  3. De9496b4fb962b5b9a99111ccd5fffed?d=mm

    VitioPax

    Mar 02, 2020 16:17

    Well, still does't work.

  4. C758f3a7a5d04711668f307d67cf510f?d=mm

    ArkadiuszR

    Mar 01, 2020 22:22

    Still not work o.O

  5. D44d589267c96109167726ab55df4349?d=mm

    Lorash

    Feb 27, 2020 08:52

    Voting disabled for resolved issues, thank goodness, I was worried there for a while.

  6. 03053c9f839d1b04f88b79abbb730816?d=mm

    zackblack

    Feb 26, 2020 16:20

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

  7. Db07513415458bdc1aa5f7afad2e638c?d=mm

    omertr

    Feb 25, 2020 18:46

    Still not fixed in 2019.3.2f1 ....

  8. Fa0985026ba63bd17abee8f6a2b614d0?d=mm

    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.

  9. F478a09c13ac7edd16d915a25dcb03a9?d=mm

    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

  10. Dd5d04f54945a127d2b650f84fb5e944?d=mm

    SaltwaterAssemnly

    Feb 24, 2020 07:25

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

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.