VIKINGS

I made a simple example and put it on my dropbox, it will be easier if you use family so you don't have to make bunch of functions for each object. You can download it here

Sorry for the late replies guys :<

VIKINGS

Well, it's not something that I would like add to the litetween behaviour, if I add more and more features into it, the behavior will slowly be infested with more bugs and the interface and actions will become complicated. For things that can be done with event sheet, I prefer it to be done on event sheet. These kinds of things like controlling the tween or randomizing it really should be done with event sheet.

ome6a1717

Try setting it on 'Enforce' instead of compromise, it looked like that is what you need. Compromise will try to 'compromise' with another behavior that change the object's position, for example if you have sine and tween run together, it will try to still play both instead of trying to compete with the behavior for controlling the object position.

blackant

On the Litetween start there's an option to choose 'start from last recorded' or 'start from current' which will start the tween from the proper position. Litetween is originally made to make movements of GUI, so it is simpler to make it defaulting to 'start from last recorded' instead of current. But if this is not what you mean, please let me know and I'll check it again.

Bodhran:

Can you give me simple capx demonstrating the problem? I will fix it.

Edit: Uh, nevermind that one, I re-fixed it, it reverted back to some version some time when i got HDD failure and i started working from the wrong version afterward. Sorry for the late reply, was busy these days. Download on the first page as usual :>.

bhain7

It shouldn't have that problem it should be light enough because i use lookup array. Can you show me your capx or at least explain which part is causing trouble?

blackhornet

Thank you for telling me, I just changed the 1.2.1 version to 1.3. It's not something big that warrant a minor version change, but I still change it from 1.2 to 1.3 to make sure people knew something was changed.

anmaz

Okay, been busy these two days. I just checked out your code. You use two tween that plays together.

There are two tween which is Up, and Down; The problem is, the Up progress is still at 1.0 when Down finished playing, so Up won't be able to play since it's already at the end. You need to either use Reverse, or 'Seek 0' to place it back at the beginning.

This is the corrected capx and the other one is just something i think would simplify it.

https://dl.dropboxusercontent.com/u/553 ... waves.capx

https://dl.dropboxusercontent.com/u/553 ... aves2.capx

PS: I changed the tween behaviour a bit to help with reversing control, please redownload it.

anmaz:

I tried to understand the code but it is really easier if you could give me a simple capx demonstrating the problem. Could you please send me the link to the capx?

bladedpenguin:

I added save and load support, can you try if it works or not?

—

It works, but you have to tween value and insert the value manually into the spritefont.

— le Canapin

Nope, but you can easily extend the behavior by yourself. Which easing do you want to implement? If it's not much trouble and it does not have so many param, I might add it.

kingpirux

Is it the ping pong and stop from easetween? I removed that in Litetween :<... The reason for that is that I tried to decouple play control with the tween itself. Things like play control should be done in the even sheet.

You can use normal ping pong, then add just one event to make it happen, which is

On Tween Reverse End > LiteTween Stop

Vintehin

Thank you and happy new year too :>

—

Sorry for the late reply. It is not possible to do it with the stock litetween, maybe you can try to tween the timescale of the object while doing tween. But I am quite busy nowadays, so I can't help you by making a small capx for it >.<

xoros

I'm sorry for not answering quickly, been busy these few months. Can you explain which part of seek doesn't work? I used it quite alot, and I don't find anything wrong with it, so maybe you could post a small capx that introduce the error?

veronica

if you mean the litetween behaviour, it's on the very first post. If you mean the real 'light' behavior, i can't help you :<