- Home /
How to avoid iTween's AddComponent
I love iTween. Every time I try to replace it with something else, I end up missing it's simplicity of use.
There is however, one big problem with iTween, and it's the way it adds a component on every tween it does, and then destroys it. As most iTween users know, this sometimes creates a noticeable and undesirable hiccup.
I know the docs recommend calling iTween.Init( gameObject )
to prevent exactly that, although if you look at the iTween source, you see that it just forces the creation of an unnoticeable tween (move to zero) to speed up future AddComponent
calls.
My question is:
Does anyone know of a way, or a branch of iTween that does not use this AddComponent
approach?
I mean, I would like to either add some "tween slot" components on my own, or some other way that does not perform these performance-heavy component additions.
Your answer
![](https://koobas.hobune.stream/wayback/20220613103717im_/https://answers.unity.com/themes/thub/images/avi.jpg)
Follow this Question
Related Questions
How to change a value over specified time? 2 Answers
Play iTween on instantiated prefab 1 Answer
iTween Native Support OnComplete 0 Answers
SetFloat Shader Value question/issue 0 Answers
iOS slow performance only first time 0 Answers