Open wrymn opened 11 months ago
Indeed the issue seems with tweens trying to be restarted when they don't exist, but if you delete the gameObject this shouldn't trigger. Going to test this (after I test the other issue you had), which is puzzling me right now
Any hints how to solve this or what may we be doing wrong?
We get literally hundreds of these messages when enabling verbose logging:
![image](https://github.com/Demigiant/dotween/assets/12801017/f7a866d9-cb8d-4263-8e59-1178bc8d96f1)
I fear it may cause performance issues in our game (even with disabled logging, as something is definitely wrong)
Unfortunately I have no idea how to reproduce it or what could be wrong, as I believe we are using DOTween according to documentation :)
Maybe some hints: We are using only
DOTweenAnimation
components on prefabs and scenes. None of them have AutoKill, as we are using them withDoTweenVisualManager
component that restarts the tween OnEnable(), as this is how we are using the tweens in the project, where we just activate some UI element and expect it to tween scale or fade automatically, so I presume auto kill would make it not work on next OnEnable().Some hint 2: The first screenshot tells about NULL tweens. We have tween animation components with autoplay on the scene. However, when scene loads, we destroy these gameobjects with tweens right away, as they get replaced by proper prefabs. Maybe this is causing the issue? As dotween is trying to auto start and restart the tween, but it gets destroyed by unity.