I'm Told It Can't Be Done

One of the rides I'm trying to build for Lindenworld is a Scrambler. You probably have seen one at an amusement park or carnival. It has a three corner arm on top that spins clockwise with three satellites attached to the ends of the arms that spin counterclockwise. Of course, everything wants to spin clockwise if the top piece is the parent object. It all has to be linked to stay together but that does not allow the satellite pieces to spin counterclockwise. I have experimented with point to point connections but that won't work with linked objects. Any suggestions?

OH boy I been trying that one, as alot of people in Olive have sen or felt in the past few days.

It fails physical tolerances badly, and it breaks apart great.

So far I cant see it happening. At least in a smooth fluid manner.

However if you want a really choppy looking one, try a combo of llSetPos and llSetRot with no physics. I didn't try this as my previous attempts to make something look smooth and fast at the same time were highly unsuccesfull.

Maybe llTargetOmega too.

llSetPos and llSetRot should look smoother in 1.1 so maybe then.

You mean how those two functions are going to be damped?

Any word about whether or not the damping will be optional? Since it kinda should be...

I'm sure that if you only use the one parameter, the position vector to move to, it will do the standard 20M-max snap-to action. The damped behavior would engage if you add the extra parameters it needs.

all llSetPos and llSetRot calls are damped although that is the wrong wording and wrong way to think about it.

Server side the motion is the same - the object 'snaps' to the new position.

Client side it looks as if it moves there instead of warps there.

The precision isn't lost, functionality isn't lost. It only looks different. And really in about 99% of the cases it looks better.

So doors that use a few llSetRot to work will look like they are swinging open instead of snaping to a few places in between open and closed.

You will be able to use llSetPos calls (several times) and it will seem as though you are moving through the intervening space, not jumping over it.

I posted a big gripe about the damping not being optional and I was told that in 1.2 you can set the damping such that it takes 0 time, effectively turning it off.

But for 1.1, not optional.

As long as I can can instantly snap objects from place to place, I'm happy. If that behavior is removed from the game, a lot of things will break. I'd LOVE to have a smooth, linear, non-physical motion option, but I still want to be able to teleport objects around.

I can't see the old functionality being removed though... One of the problems for the developers is keeping every update as back-compatible as possible, especially with the scripting language.

Somethings will definately suffer in the look and feel dept. but nothing should break. What do you have that breaks?

Anyhow, I'm with you, and LL already addressed it. But be prepared to not be happy until 1.2 hehe

Oh, I'll be happy with 1.2, never fear.

As for breaking, my ride for Lindenworld uses the instant motion of llSetPos to move the car around in the dark. But I'm not worried.