You’re very welcome, thanulee!
Of course, I can elaborate, and its a pleasure to do so.
The dynamics are calculated after the MoGraph has created and placed the clones. At the moment the Dynamics take over, the initial position and rotation are kept as a starting point, but anything that happens will be not available for the MoGraph set up. However, the Render-Instances or the Multi-Instances are calculated during the MoGraph time. An instance can’t have an initial position and change based on Dynamics in a different way for each clone, hence the term instances.
What you saw, when you shared the file, the average (kind of) change from “initial to current position” is applied to all instance. Well not at once, as the trigger is set on impact. So the Instance group is partially MoGraph and increasingly Dynamics, hence the progressive screw up.
At the moment we go back to pure instances (vs. Render or Multi), things stabilize, as the storage is individual again.
This position and rotation are supplied to the Cloner.1 (pale blue arrow, @ 47 seconds of the screen capture), and so we have again all positions in one set, not split between MoGraph and Dynamics. Now the Cloner.1 can be set to Render or Multi-Instance, to take advantage of the increased render-speed. So we have both, dynamics and Render/Multi Instances
Screen capture (download please for a better viewing experience)
https://www.amazon.com/clouddrive/share/QROGG19TlR3Jn832GJk1SYY05rWmMkO5rkAljfCrqbv
Does it make sense what I wrote, if not, let me know.
Cheers