In need of a creative solution!

[Mikhail]

What if you use 10 different areas, block_box entities and non-uniform circular motion equations to calculate the angular speed and angular acceleration every time you rotate the rings by 16 degrees? And then, use RotatePropToSpeed with the calculated speed and acceleration to rotate the planets?

This method NEEDS a part of the rings to be able to collide with the areas without the entire ring doing it. That's why I propose adding something similar to a block_box entity on the rings in the Model Editor.

Also, the areas should be really thin and placed like if they were the diameter of the rings. The ending result should look like a pizza.

Finally, I would recomend the use of two tablets instead of only one. A big one in wich the players are supoused to place the planets, and a small one used to rotate the rings.

When the player rotates a ring on the small tablet, collide callbacks between the 10 different areas and the block_box entity use the N-UCM equations and a timer (by using GetTimerTimerLeft) to calculate the afAcc and afGoalSpeed variables used by the RotatePropToSpeed function. Then, you use this function to move the rings on the big tablet AND the planets at the same time.

If you use 20 areas, the distance between them would be reduced to 8 degrees, making the rotation of rings and planets more accurate.

This is the only way I can think of to get your puzzle to work. Although It might prove to be a bit difficult to get it right.

By the way, I apologize for any grammatical errors. English is not my first language.


Wow, my first post is longer than I expected...

EDIT: Angular acceleration, not tangential.