No, because `rotation`

is not a `Basis`

, it's a `Vector3`

.

This would run fine:

```
tween.interpolate_property(self, "rotation", mynode.rotation, othernode.rotation, 0.3, Tween.TRANS_LINEAR, Tween.EASE_IN)
tween.start()
```

I'm just a bit skeptical about the wrapping cases, for example, if your Y rotation is `175`

, and you want to look at `-175`

, `Tween`

is going to make the node rotate all the way around rather than going the shortest route (because angles can wrap!). If you end up with this problem, you will need `Basis`

or `Quat`

.

After asking Reduz (cuz there is no doc about this), the proper syntax to interpolate `transform.basis`

is this:

```
tween.interpolate_property(self, "transform:basis", mynode.transform.basis, othernode.transform.basis, 0.3, Tween.TRANS_LINEAR, Tween.EASE_IN)
tween.start()
```

And still, this only covers the rotation tween itself. If the source of your initial and final rotations are for "looking at node A, then at node B" there is some math involved to obtain the rotations you need, which I think you did by calling `look_at`

, getting the result, then changing rotation again through the tween.