Garbage Recycle Problem With Load Level

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Use some dotween's feature in a scene.
2.Load another scene.
3.Check the number of gameobject in total.
4.Every load level operation, there will be some dotween's object stocked there.

What is the expected output? What do you see instead?
    In addition, it feels like the time flow is a bit faster when every load level operation happens. For example, a animation with duration=2 will be finish in 0.5 sec after several load level operation.
    There shouldn't be any object left behind nor any animation speed issue even after loading levels. I changed all the things into hotween then everything works fine.

What version of the product are you using? On what operating system?
V0.9.380 (December 03, 2014)

Please provide any additional information below.

Original issue reported on code.google.com by alex530...@gmail.com on 6 Dec 2014 at 2:38

[GoogleCodeExporter]

Hi,

supersorry for the late reply. I was doing the last Ludum Dare and going crazy 
with it.

This double speed happens if you have more than one DOTween object in your 
Hierarchy, and this issue causes more than one to appear. The problem is that I 
implemented various routines to avoid this, and I tried to replicate it many 
times but all works perfectly here. If you managed to replicate this issue in a 
small barebone project and send it to me it would be incredibly useful, so I 
can finally understand what causes this bug and fix it once and forever.

Original comment by daniele....@gmail.com on 9 Dec 2014 at 12:55

• Changed state: DataNeeded

[GoogleCodeExporter]

It may cause me some time to replicate the problem since I have a midterm
next week :(
I encountered this problem when I'm developing a project and I already
remove the part that cause the problem.
I will send you a small project once I tried to replicate it successfully.

2014-12-09 20:55 GMT+08:00 <dotween@googlecode.com>:

Original comment by alex530...@gmail.com on 9 Dec 2014 at 5:38

[GoogleCodeExporter]

Thank you very much! I will wait: I'm already very happy that you'll try to 
replicate it, since it's driving me crazy. By the way, if you have time (and 
without rush), can you tell me what you had to do to solve the problem? Maybe 
that will help me enough already :)

Original comment by daniele....@gmail.com on 9 Dec 2014 at 6:21

[GoogleCodeExporter]

I simply changed all the dotween's functions into hotween's and the problem
was gone.
More specify, I changed the only DOMove in the whole scene at the Start
function to Hotween.To.

2014-12-10 2:21 GMT+08:00 <dotween@googlecode.com>:

Original comment by alex530...@gmail.com on 10 Dec 2014 at 2:36

[GoogleCodeExporter]

Our version control is very broken...
I may need some time to replicate it :(
By the way, I found out that I used both Hotween and Dotween at the same time 
and I am not sure if that will cause any problem.

Original comment by alex530...@gmail.com on 23 Dec 2014 at 3:51

[GoogleCodeExporter]

Ouch, when version control breaks it's really bad. Don't worry I'll wait. And 
in the meantime I can confirm that using HOTween and DOTween together is not a 
problem.

Original comment by daniele....@gmail.com on 23 Dec 2014 at 8:08

[GoogleCodeExporter]

Finally managed to replicate this and fixed in recent versions

Original comment by daniele....@gmail.com on 29 Jan 2015 at 11:23

• Changed state: Fixed