Feedback Unity 2019.3. FBX importer broken

Ok, looks like the after beta version of Unity 2019.3. are the worst considering they destroyed the fbx importer.
Can no longer import my asset as trying so just throws errors into the console.
When will this be fixed and I can go on working? How can something this important get broken and sneaked unnoticed through QA?

Please vote in this issue: https://issuetracker.unity3d.com/is...with-multiple-clips-and-opening-animation-tab

Only solution seems to downgrade to any version below 2019.3.0f6 or go into vacation until fix arrives.

 

The status says the fix is already done and in review. So I don't see how voting on this issue will change anything.

Unity QA must not have a regression test case where they import an FBX with multiple animations and specifically open the animation tab.

 

I disagree, models with animations are a core feature of any 3D game, just think of characters, or did encountered main characters with just a single walking animation?
So many bugs coould simply be encountered by just using Unity in a normal way a developer would do. Cannot imagine nobody at Unity notice such things.

 

I didn't say they weren't core features of 3D games, just that importing an FBX with multiple animations and then specifically clicking on the animation tab must not have been in their regression test suite.

Unity QA doesn't make games by the way. They don't have time go through an entire game development process every couple weeks for every release. It is simply not feasible. Every game doesn't cover every common bit of functionality either anyways.

 

Only very few of our FBX files with multiple animations are experiencing this bug, so I assume whatever the cause is, its more complicated than just an FBX with multiple animations.

 

I don't say they make games, but they should collect information about the process. Unity has some small teams making demos for example. So there must be any kind of communication when a dev team encounter a bug.
And if nobody is interested in collecting bugs by simple testing the application, who should then get paid for it?
You would noticed it immedately, if you working on a project, upgrade your Unity version, continue to work on your fbx assets. But if nobody at Unity does this, then ground breaking bugs like this come through, annoying the developers.

 

This is still not fixed in the newest update 2019.3.2f1.

 

Same issue here

 

The voting was closed, despite the fix landed only in 2020.2.
Unity 2019.3.3f1 still did not got this fix. (We have this bug since 2019.3.0f6).
I'm confused about the Issue Tracker policy.