Dotween: Appending short sequence into sequence causes the "outer" sequence to stuck

Created on 9 May 2017  路  5Comments  路  Source: Demigiant/dotween

I generate sequences procedurally and then I chain them or encapsulate them (put one into another), sometimes I generate a sequence that is empty or has just small interval inside itself.

What I have encountered is that if I have sequence that is very short and I put it into some other sequence, it couses the other (outer) sequence to stuck at the moment it should execute the inner sequence.

var inner = DOTween.Sequence().AppendInterval(0.1f); var outer = DOTween.Sequence() ... (other tweens) .Append(inner);

Most helpful comment

  1. If you have an empty sequence, it won't work - https://github.com/Demigiant/dotween/issues/40
  2. Have you tried disabling SafeMode?
  3. Which version of DOTween are you using?
  4. What platform are you testing on?
  5. Can you provide minimal tween/project that reproduces the bug?
  6. Does the bug also happens when running project in Editor?

Note: I'm not anyhow developing this code, I'm just interested in it being reliable.

All 5 comments

  1. If you have an empty sequence, it won't work - https://github.com/Demigiant/dotween/issues/40
  2. Have you tried disabling SafeMode?
  3. Which version of DOTween are you using?
  4. What platform are you testing on?
  5. Can you provide minimal tween/project that reproduces the bug?
  6. Does the bug also happens when running project in Editor?

Note: I'm not anyhow developing this code, I'm just interested in it being reliable.

  1. I have figured out that the empty sequence does not work, that's why I have tried to append 0.1f interval to it. It worked in editor, but on the iOS it caused the sequence to stuck
  2. Nope I didn't even know there is something like this in there
  3. The one that is currently on the Unity Asset Store
  4. Editor - works fine, iOS - bug appears, didn't try other platforms
  5. Probably later on, don't have time to do it now, sorry
  6. In editor it only get stuck if the sequence is empty, if the sequence is just short interval, it gets stuck only on the iOS. As I'm thinking about it now, maybe the problem is not that the inner sequence is short but that inner sequence is just a sequnce consisting one interval only. I didn't check the code but it's possible the DOTween removes interval at the tail of the sequence and thus resulting this as an empty sequence which we know does not work

I would personally add some warning or something about puting an empty sequence into a sequence, because as someone has stated in the #40 it took me quite a time to debug and find out what is the problam (I has an empty array from which I was constructing the sequence)

The solution I have applied is that I'm checking if the lists I'm constructing sequences from is empty and if it is, I return null instead of empty sequence (or sequence with short interval).

@Malhavok But overall I'm using DOTween on almost all my projects and this is the first time I have runned into an issue so I would say it's pretty reliable and I would recommend using it.

Ahoy!

I just added a note marked as important on the docs, to say that empty Sequences are no good.

About the rest, I'll have to investigate (next week). Sorry for the issue!

Any news on this ?
This is party stopper for us.

Yea It would be nice to have appends / prepends and so on to ignore empty sequences or the execution of the tween to ignore them because I'm able to work around it but I have code full of ifs that checks whenever something was added to the sequence and appending it only if was which makes my code much more messy.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jizc picture jizc  路  10Comments

Mukarillo picture Mukarillo  路  4Comments

Dentrax picture Dentrax  路  10Comments

ceyhuntasci picture ceyhuntasci  路  5Comments

RDeluxe picture RDeluxe  路  8Comments