Search Issue Tracker
Fixed in 5.3.6
Votes
1
Found in
5.3.4p3
Issue ID
788946
Regression
Yes
Animating GameObject.IsActive of a child with Animator Controller crashes.
Animating GameObject.IsActive() of a child with Animator Controller crashes.
Steps to reproduce:
1. Download attached project "788946.zip".
2. Run scene "reproScene".
3. After few cube blinks Unity crashes.
Steps to reproduce without a project:
1. Create empty game object.
2. Create and parent cube to previously created GO.
3. Create animator for both of them.
4. Create animation for empty game object - animate child cube's GameObject.IsActive() - make the cube "blink".
5. Enter play mode - after few seconds Unity crashes.
Reproduced with 5.3.4p2, 5.3.4p3, 5.4.0b13 and 5.4.0b14.
Does not reproduce on 5.3.4p1 and 5.4.0b12
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
- [Android] The Player freezes when disabling Bluetooth while connected to the headphones
- Addressable bundles are not retrieved from the cache when a WebGL Player is refreshed
- Sprites are incorrectly occluded by Sprite Physics Shape culling when behind in sorting order
- CPU usage is increased when the Editor is idle with the ProBuilder Package installed
- Unstable lighting when additional light sources are added in Shader Graph nodes
Aedous
Apr 20, 2016 15:38
Just some extra notes, it's not just animating the gameobject, but any gameobject with an animator that has children with an animator will cause Unity to crash if you delete/disable the parent whether it's through code or the editor.
I've tested it on 5.3.4p2 and 5.3.4p3.