iTween Move Add - DO Tween equivalent?[SOLVED]

[curb47]

Hello, I'm new here, so...

I'm following a tutorial (Jonathan O'Duffy) and have hit a little problem. He uses iTween in many of his FSMs, which is out of date now, and I've got DO Tween installed which is great. I've managed to translate the iTween actions to the DOTween equivalent... apart from 'iTween Move Add'.

I've tried Transform Move and Transform Local Move, but it's not doing what I need.

The Do Tween transform actions all seem to be 'to world' or 'relative', and you provide a Vector3 position or variable for the object to move to, however, I want to ignore World or Relative positions, and just ADD an animated float to X, so regardless of where the object starts (position), it will move that amount.

This is the tutorial I'm working on:

http://jonathan-oduffy.thinkific.com/courses/take/playmaker-101-the-complete-course/lessons/232817-chapter-9-14-three-ways-of-setting-up-default-variable-values

Thanks in advance.

[curb47]

In a nutshell, I want to ADD a variable ( Vector3- 10, 0, 0) to the current position of the object. DOTween Translate always wants to move the object TO Vector3- 10, 0, 0.

Clicking the relative box almost works, but it's still essentially doing the same thing; moving TO Vector3- 10, 0, 0, relative to itself.

Make sense?

[curb47]

Mmm. Upon closer inspection, it appears that DOTween Transform Move does actually calculate the new vector as ADD when the 'Relative' box is checked, rather than moving to an absolute value.

I don't know what's going on then, because it's glitching all over the place.

[curb47]

Okay, I'll just carry on posting what I find...

So, it turns out that DO Tween Transform Move does not support an object that has a Rigidbody component attached to it, which is REALLY annoying because that's exactly what I need to do.

I read online that DOTween Pro supports Rigidbodies, so I paid the money for that, and have reconstructed the entire project (tutorial) from the beginning, and have finally got to the part where I attach the Rigidbody to the object... And it's still got the same problem!

I'm getting quite annoyed at this now, because what should have been a simple step is wasting so much time, trying to find a solution.

Why are there official tutorials that are using functions that are obsolete?

Alternatively, has anyone got a solution for attaching a Rigidbody component to an object with a movement Tween, and actually have it working how it's supposed to?

Thanks.

[djaydino]

Hi.
Maybe the Playmaker Tweens (Beta) can help out.

For the official tutorials that use itween they should indeed be updated and or removed, but maybe Playmaker is waiting to make new tutorials when Playmaker 2 is released

[curb47]

Thanks for your input.

I just wondered, is there a release date for Playmaker2? For people who have purchased Playmaker1, would it be free?

Thank you.

[djaydino]

Hi.
Sorry i have no idea,
I only know that Playmaker is working on it

[ManInAShedGames]

Okay, I'll just carry on posting what I find...

So, it turns out that DO Tween Transform Move does not support an object that has a Rigidbody component attached to it, which is REALLY annoying because that's exactly what I need to do.

I read online that DOTween Pro supports Rigidbodies, so I paid the money for that, and have reconstructed the entire project (tutorial) from the beginning, and have finally got to the part where I attach the Rigidbody to the object... And it's still got the same problem!

I'm getting quite annoyed at this now, because what should have been a simple step is wasting so much time, trying to find a solution.

Why are there official tutorials that are using functions that are obsolete?

Alternatively, has anyone got a solution for attaching a Rigidbody component to an object with a movement Tween, and actually have it working how it's supposed to?

Thanks.

Did this work out in the end? Interested in dotween myself.
I completed Jonathans course last year. I managed to use itween just fine with it.

[Christoph]

I have the exact same problem. Itween seems so easy to use while with Dotween it's doing almost what it wants. I still haven't really figured out what it exactly does, but my guess is also that it has to do with local/global. Same settings from itween move the cube to a complete different position.

[Scott Moffitt]

So I had the same problem. I think I figured it out.  First, make sure you do not have a rigidbody. Then use the Action from my image with these settings.

[LuminRabbit]

Hi curb47,

You could create an empty game object then put the object you want to move inside it (make it a child), the child object would have the FSM and use DoTween Transform Local Move as a test set the "To" of XYZ to X1, Y0, Z0, then check the box for Set Relative and Duration to 1,

Thats it drag the empty game object anywhere you like and it will only move the specified distance (nice for platforms, especially when you set loops to -1 and LoopType to yoyo).

Hope it helps...

There's gonna be a playmaker 2, Whoa! where can I get more details?

[curb47]

Hi there,
Thanks for your input. Sorry, I should have marked this problem as solved, I fixed this quite a while ago.

Happy Xmas.

J.

[Broken Stylus]

DoTween is a bit more cryptic, you must test it a lot.
Unless you plan on manipulating the tween you created (like pausing it, or playing it backwards), you can kill it automatically.
The recycle option means that when you create a new tween for the first time, it generates a model (stored in the buffer IIRC), a template of sorts which will then be used again every time the same tween action requires a new "copy" of this tween.

I'm not sure if there's a Playmaker support for sequences yet. As I understand it, sequences are successions of chained tweens played in a given order.

Do not forget about the "set relative" option.
As a measure of security and peace of mind, I prefer to always set up the element that is going to be modified by a tween with an initialization phase even if in theory it shouldn't be necessary. This because with DoTween you can have a tween swap from being a "A to B" to "B to A"; in other words, it becomes a FROM tween instead of a TO tween, where the finishing state of your element is how it rests in your scene and the starting value is defined by the parameters you enter in the tween controls.

Also, as a rule of thumb, if you apply tween to RectTransforms, try to avoid changing the pivot point's position, just keep it in the center of the object because some actions will have behaviours which are just impossible to understand if you move such pivots and it's just not worth the hassle.