Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.3.X
Votes
0
Found in
2020.3.31f1
Issue ID
1412466
Regression
Yes
Animation state properties not visible when the state has an outgoing transition
How to reproduce:
1. Open the user's attached project
2. In the Animator window select "Idle_FR" or "Walk_FR" animation state
3. Observe the Inspector window
Expected result: Animations state properties are visible
Actual result: Animation state properties are not visible
Reproducible with: 2020.3.31f1, 2020.3.32f1
Not reproducible with: 2019.4.37f1, 2020.3.30f1, 2021.1.0a1, 2021.1.7f1, 2021.2.18f1, 2022.1.0b13, 2022.2.0a8
-
BroVodo
May 22, 2022 02:15
If Unity's service is providing strategically timed bugs designed to coincide with whatever I need to work on at a given moment, then well-played.
-
angiemon
Apr 12, 2022 11:11
@NEMLAR I just logged in to say, you really saved our ass and like 70% of all my work in the gamejam we attended last week by sharing this much needed workaround!
You, Sir, are a legend, thank you!
-
radagabald
Apr 07, 2022 19:07
Or is it Long Time to get Support?
-
Maxim
Apr 07, 2022 19:00
Be patient. It's only been 2.5 weeks. LTS means long time support.
-
Tsigaro
Apr 06, 2022 20:37
Still waiting for this bug (and the one where I can't move my state block if there is a transition) to be fixed... This is a LTS version, come on !
-
parixit2411
Apr 03, 2022 06:32
First I was using some version of 2020.3 LTS. It was working fine really. Then I updated it to 2020.3.29f because one project needed that specific version. That version was taking too long to build WebGL and Android build and getting stuck while closing unity but it was overall functional.
I thought the performance issue would have been solved in the latest LTS releases so I downloaded the 2020.2.32f. It has more bugs.
Now I don't care that it is happening with LTS and there is no proper response from unity its just in review. I just want to ask if someone from unity can confirm which latest 2020 version should we use which does not have this kind of silly bug. Generally, it should be the latest LTS version but in the case of unity, we cant say.
So please while you fix these bugs, just comment and let everyone know which latest 2020 version is stable.
-
Nemlar
Apr 03, 2022 01:12
Although this really unacceptable in an LTS version (I'm using 2020.3.32f1), one workaround I found was in the animator putting the inspector into debug mode. For some reason after that one is able to make transitions again (i.e. the states seem to function properly again).
-
ZeHgS
Apr 02, 2022 04:28
Yeah, people are being harsh but it's absolutely true. LTS versions shouldn't have previously known bugs in them and the fixes should not have to wait for anything at all to be released. They need to be released immediately even if it means releasing 15 fixes per week
-
Neale_FFS
Apr 01, 2022 11:16
Can you please release a patch for this for 3.3.2f1 ASAP.
I can't believe you released an LTS in this state- it makes the animator virtually unusable for complex character-based games. You want to have a word with your QA team, if there actually is anyone checking this stuff, as there's no way something that serious should be part of a stable release!!
-
mrcraigoman
Apr 01, 2022 11:07
This needs to be fixed on the latest LTS version, shocking.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.33f1