SetActive breaks Animation Component?

[ZerkyWerky]

I have a interesting issue. I think its a bug and I’ve searched for answers on this but haven’t found any answers pertaining to my problem. One thing is that people are saying that depreciating SetActiveRecursively in favor of the new SetActive is a step backwards. I tend to agree. SetActive is a confusing and hardER to manage approach to activating and de-activating objects. It takes the flavor out of customizing your objects behavior.

Anyway, my problem is this.

I have an object with an Animation component on it. The animation plays fine. But if I SetActive(false) then SetActive(true), then the animation component no longer works even if I do a animation.Play(“anim”) on it after the SetActive(true).

Any ideas why this bizarre behavior is happening?

[ZerkyWerky]

bump

[calypso]

@ZerkyWerky

I have a interesting issue. I think its a bug and I’ve searched for answers on this but haven’t found any answers pertaining to my problem. One thing is that people are saying that depreciating SetActiveRecursively in favor of the new SetActive is a step backwards. I tend to agree. SetActive is a confusing and hardER to manage approach to activating and de-activating objects. It takes the flavor out of customizing your objects behavior.

Anyway, my problem is this.

I have an object with an Animation component on it. The animation plays fine. But if I SetActive(false) then SetActive(true), then the animation component no longer works even if I do a animation.Play(“anim”) on it after the SetActive(true).

Any ideas why this bizarre behavior is happening?

I’m having the same problem, and I’d love to know why and if there’s a workaround.

[movAX13h]

I have the same problems… anyone got an answer yet?

[ukUnityVrUser]

Having the same issues…