llTargetOmega:Simultanious clockwise and counterclockwise rotation around shared axis

Hello,

I was trying to create an object.
a CYLINDER(axis) with two Tires(TORUSSES) with profile (SPHERES) on it.

Using llTargetOmega i have created two tires, one that rotate clockwise and the other counter clockwise. This is what i want, one rotating clockwise and the other counterclockwise.

Now i want to add profile on the tires in the form of spheres.

So i selected all the spheres and then the torus and LINKED them.
I can have the TIRES rotate with the spheres attached.
Each TIRE has it's own llTargetOmega and one now turns clockwise and the other counter clockwise.

So i now have two objects.
- TIRE1 which rotates clockwise
- TIRE2 which rotates counter clockwise.

The problem:
Now i want to link TIRE1 and TIRE2 to a common axis but each TIRE still has to maintain their own rotation.
When i link the object to the axis te spheres become sperated from the torus i think because SL doesn't support nested linked objects. So the linking causes the spheres to relate to the axis instead of the TIRE causing the spheres no longer to rotate together with it's previous 'parent' the TIRE.
I can't put rotation on the axis because one TIRE goes clockwise and the other counterclockwise.

Is there any way to give the spheres(Profile on the tires) their own rotation so they move along the edge of the torus but are moving relative to the axis and each other, i don't want the sphere's to overtake one another?

Aka: HELP!

Sorry. There's currently no way to rotate around an arbitrary offset using llTargetOmega unless you want to rotate the entire object around the root prim. If you can get away without linking the axis to anything else, you could try splitting it in two--one half going clockwise and the other counterclockwise--and put the rotation control in the two half-axes (which would each be root prims of their own sub objects). Otherwise, you're out of luck; your only recourse then is to move the spheres individually using llSetPos and a common timer.

I was affraid of that Tezkat.
Good to see it confirmed
I'm sure it will be in the next point release.

It must have a common root object since it will be attached to a person.
Oh well, tough luck.
Guess i will have to change the design then.

Thanks for the reply.

Over and out.