jayderyu:

Okie, already updated the litetween with that suggestion. Also removed a stray 'console.log' which make it unable to run on a version of internet explorer.

Rhindon:

I made a simple manual for you

Manual PDF

Manual seems like alot of work to do :o, but I'll see if I can write one.

Hi ghost,

By removing the old one, did you mean Easetween? I think you can delete the specific behavior folder (in this case lunarray.tween) in the program files behavior folder and in C:\Users\<username>\AppData\Roaming\Construct2\behaviors

And about compressor, the strange thing is that I can minify any projects with litetween just fine here. I'm really not sure if this is litetween's fault.

Whiteclaws

Sorry I missed your post.

1. Yes, Create/Initialize will override plugin edittime settings

2. About autostart, it will not autostart, except if it is on the onCreate and you set autostart to yes. You can use start tween action just below the create/initialize to make sure it runs though.

—

gamma, strange, I tried it with many sprites, but can't seem to reproduce the problem you said. It should be that tween automatically disables when it stops...

—

Could you give me capx? :o Sorry for not answering quickly. I'm on a trip for summer vacation right now, will surely look at it later on after i got back.

CreativeSpark

I guess I'll write a summary about difference between compromise and enforce. Maybe this should be on the main post.

Compromise: It will try to automatically adjust position, angle etc, honoring other behaviour and commands. So, you can put sine and tween x and they'll work together without problem.

Enforce: It will not honor other behaviour or commands. If you put both sine and tween x together, it will not work like what you expect. There are reasons why this mode exists, but i forgot what is it :o.

If you're not sure, just use compromise. And you can download the example on the main post, there is an example there.

chasethomas

There are two ways of doing that.

1. Pin all the sprites to one invisible sprite using the pin behavior. Then we tween the invisible sprite instead. (similar technique to one big MC)

2. Use the combination of Pick by UID and For each sprite and tween them using it. (similar to doing for in an array and tween them one by one)

blackhornet

Oh, that can be done with the current LiteTween without any tweak, if you want to tween only X, you set the Y to 0 (relative). And don't forget to set it to compromise mode.

Is it something like this?

Shark CAPX

KPS

That car is not done using tween, it is done using Physics. The car itself is a compound object of two wheel, two axle and a body. While the other objects are simply normal physics object.

As far as I know, physics official plugin didn't have motor objects and prismatic joint yet (you need it to spin the wheel, attaching it to cars etc). I'll see what I can do, but maybe this question is much more suitable for the "How do I?" forum.

KPS

Could you explain that in more detail or in some other way? I don't really understand what you are trying to make...

jayderyu

Ah, I added that "second(s)" behind the set duration now :>

—

Ah yes, found the culprit for the error in 432. Should be fixed now, thanks gamma... :>

vee41 & NaSTy

I'm trying to find what is causing that, but I think it must be the onTick event (because it should be there if there is any resource hog), so I did move the "this.inst.set_bbox_changed();" inside the tween state check and removed the now unused "for". Can you check it again vee?

JKID

I'm afraid that would be kinda too specific for litetween. And I didn't really understand what do you mean by clamp for tween.

I am developing Litetween for the purpose of taking providing user with the most essential tools for tweening, therefore I took down alot of convenient but rather non-straightforward approach like playmode, etc.