Why do I find that version 2 is getting more complicated? Also, my current tests show that you need to manually generate an atom and it doesn't follow. Clicking the driver and enabling it doesn't follow either
Moreover, this method has limitations and requires clicking to find or reconstruct atoms in each scene
Previously, just loading the session plugin would always be effective
Thank you for your reply. It is understandable to have such questions, as I modified many features over the past month to make the system more powerful. While this inevitably increased complexity, I am confident that once you familiarize yourself with these features, you will find the tool much more useful.
Regarding your comment: "Why do I find that version 2 is getting more complicated? Also, my current tests show that you need to manually generate an atom and it doesn't follow"—the new "Empty" atom you added is not intended to track the target point; instead, it likely serves as the point of influence for the "Displacement Weighting on Position" function. It moves with the character rather than following the insertion point. Please refer to my documentation for details on the "Displacement Weighting on Position" feature.
You also mentioned: "Moreover, this method has limitations and requires clicking to find or reconstruct atoms in each scene." That is indeed how the system operates following our recent modifications.
Why did we shift from using a single atom for control to a mode where one atom drives another? Relying on physics completely independent of VaM has a drawback: that very independence makes it difficult to integrate with Dildos or CUAs. To allow a user to interact with a character using a Dildo or CUA—even if the object itself is hidden from view—we must actively control the Dildo/CUA atom. For instance, the first version of the plugin could not synchronize the visual effect of the insertion with the physical toy itself. Furthermore, utilizing VaM's native physics for Dildos/CUAs grants users greater flexibility for customization.
Achieving results similar to the previous version is still entirely possible. You can try switching to "Dildo+Female" mode, loading and binding a Dildo, disabling its collision, making it transparent, and then enabling "Driven Mode." I highly recommend enabling the "Velocity Field" mechanism; this prevents the Dildo/CUA from exceeding the toy's physical range and slow down the motion of the toy while reaching the edge, hence this would be a powerful feature that was absent in the first version.
