Okay, scale is on my to do list now . There are also some other features i'm thinking of adding, but i don't want to put on too many features.

jayderyu

I think putting that feature on the main litetween is not really a good idea <img src="{SMILIES_PATH}/icon_e_surprised.gif" alt=":o" title="Surprised">, so i forked it instead and make a simple capx here. Not sure if this is what you wanted.

Oh, and can you tell me why you need 24fps update? I'm just curious as why it is not desirable to play with as much fps as you can.

https://www.dropbox.com/s/enktbw4cm6ewo ... ps_cap.zip

JackAttackNZ

Group tween was there in the old EaseTween behavior, if you're okay with the state it is currently is, I suggest you take a look on it (the link to download is in the first page). You can just name the group on the tween behavior and use group start to play all tween at the same time. I haven't checked the capx yet since i haven't downloaded 166, will take a look after this. :>

edit: Forget what i said above :<. if you need objects to keep distance against a central axis, I don't think it is a good use case for litetween/easetween. Compromise mode might help, but i'm not so sure. I think it is better to ask in the How Do I forum as suggested.

skyhunter93

shinkan

Oops, didn't know that. It should be okay now, I fixed the links on the first page.

clrammer

Hi rammer, sorry for the late reply, you're right, that bug with EaseInOutBack is now fixed, thank you very much for pointing out the bug

mist

Did you got the one with c2addon extension? It is actually a zip, you can just rename it into zip and extract it.

mwmwmw

340 to 0 works fine here... :o The same with 0 to -90.

If you can reproduce it in a simple capx, I can probably help more...

rexrainbow

Thanks for the quick fix

Joskin

Okay, this one should be working now :D. Please redownload again...

Something like this?

Damage Number CAPX

Joskin

Oops, sorry for all the inconvenience, but you just uncovered a bug. I have fixed it on my part, but I also need rex_rainbow to fix his behavior for this.

EDIT: rex already fixed the behavior :o, you should redownload his behavior too

While I'm waiting for rex's response, you can try redownloading the litetween behavior, once again...

Oh, and I also made some modification to your capx, basically it's something like:

1. Changing the star's sprite background from white to transparent

2. Changing various value of the litetween on the stars

3. Setting starting value on the event sheet before starting the tween

Modified CAPX

PS: To try running the modified capx, you have to wait till rex changed his Tween2Effects, or it won't run as intended.

rexrainbow

Rex, turns out I'm saving the value in the sprite's instance, so multiple litetween will use the same value. I should've stored the value in the behavior instead just like the old tween :(.

Could you please change the Tween2Effect (at around line 69)

var value = (this.tween_behavior_type == TYPE_LITETWEEN)? this.tween_behavior_inst.inst.value : this.tween_behavior_inst.value;

to this?

var value = this.tween_behavior_inst.value;

Joskin

EDIT: Silly me, I put the new litetween on the dropbox folder but forgot to sync it to the cloud :o, please redownload again :D

Joskin

Done a quick fix to make it compatible with Tween2Effect. You should re-download the behavior. :>

Long answer:

As to why it happened, it's not a bug actually, but it has something to do with how tween.active variable was used differently in litetween and the previous version of tween. The tween2effect detects whether the tween is running based on this variable so it won't work. I fixed it now so that active properly stores tween running state.

PS: Oh, and I think you should take how 'Compromise' works with Value tween into consideration, or just simply set it to 'Enforce' if you want simplicity.