Jaiden Magic

The bug must have gotten some attention. After a few days' break from the project, I came back to it, using non-keyframed motion to cross the border, and it works perfectly. The bug must've gotten some attention and got fixed. Thanks for the help, everyone!

:matte-motes-smile: It's fine, I've just looked at this function 20 diffferent ways trying to fix this problem. Thanks for trying.

How would I use them? The movement vector passed into llSetKeyframedMotion isn't a "Go to this spot" vector as much as a "Go west three paces" vector, not caring where the object currently is.

I have been attempting to produce a train of sorts using llSetKeyframedMotion(). It works beautifully in the preliminary tests within one sim, but when I tried to cross a sim border with it, the function loses the ability to do anything after crossing into the next sim. The sensor that powers it is still going, triggering the no_sensor events that set off new commands of the next keyframe. But it will not move, nor will it resist my manual movement of the object as it would when working normally in the sim it started in. Moving it back into the sim it was in lets it resume keyframed motion as normal. Stopping and playing keyframes doesn't work, nor does resetting the script or dragging a new copy in the new sim. The only way I can get it to work in the new sim is to pick it up into my inventory and re-rez it across the border, after which it works normally. So it seems to me that llSetKeyframedMotion only works in the sim that the object is natively rezzed to. The LSL wiki says "Inter-region are supported." Has anyone else tried inter-sim motion? Thoughts? Suggestions?