I guess they have not met you yet haha.
Have you any hints on a direction?
In the solution I’ve been attempting to solve is using a position list on one object and putting it on a path constraint targeting a line connecting the two points. Then when the line rotates it rotates one object around another…but not vise versa yet.
How many nodes/objects are being used?
i’m a little confused. i don’t know what to do. if i show my solution the hundred people on this forum says – sure… it’s obvious.
hmmm… maybe i could give you some ‘incomplete’ rigs to play with…
Is there no clue you could give without giving it entirely away?
i’ve given a clue… my solution is based on list controllers where some of their sub controllers are scripted.
THERE ARE NO WEAK REFERENCED NODES IN MY RIG
(ps. the weak reference is a myth)
that’s exactly what i said above.
i will believe anyone who say “i’ve solved that!”. great! you don’t have to show and prove it. good for you.
but i don’t see anyone who is close to a solving.
weak reference…
there is a very old code in max sdk that checks the dependency loop. and the checking is wrong!
there are many situations where the system ‘locks’ some connection (wiring, referencing, etc.) because of a ‘fake’ dependency loop.
i think that nodemonitor and nodetransformmonitor classes were specially designed to just fool and only fool the system. these classes do only ‘not sending’ some messages to the system making the system ‘not check’ dependency loop. it’s just only a trick and not a solution.
i mean that i didn’t see yet any idea that works. i didn’t see THE KEY to make me believe that the idea works.
Well just throwing ideas out there – i’m not near max but here goes using just my brain. We could do something like this:
3 nodes A, B, C
B instanced rotation onto A, C
A, C position list controller with two bezier_positions controllers
Instance B’s position controller on to A, C’s first bezier_position controller
A script controller on A/C’s second bezier position controller
Edit: this is less of an orbit around each other, more of an orbit around the center.
hmmm… sounds promising. but i don’t really understand the role of the third node. and i don’t see a ‘switch parent’ mechanics.
well… there is another clue:
it should be a controller based mechanics to make one node a driver and another node driven.
OneAcc was close when he was using the ‘who is selected’ idea. it might be realized with a controller solution.
Well, i re-made this sample by using get/set value of constants in script controller instead of selected objects, it works but animation still unusable. Keys are created just by moving animation slider. May be correct solution needs smth like boolean controller somewhere.
CATHDPivotTrans controller (max 2010 and above), provides the ability to have an animated pivot point.
Edit, I didn’t saw the above reply… beat me to it
Does this involve CATHDPivotTrans and animated pivot points?