ToySerialController: Driven Dildo Fork

Plugins + Scripts ToySerialController: Driven Dildo Fork

Download [<1 MB]
Joined
Feb 8, 2022
Messages
14
Reactions
13
MahiroOyama submitted a new resource:

Toy Serial Controller (Fork 4 Dance Lovers) - Now can be driven by only one person without dildo/CUA. Just let her dance on your dick!

ToySerialController DancerFork extends the original Toy Serial Controller with a new Virtual Reference motion mode designed for single-person motion scenes, especially dance, MMD, and other performance-focused use cases.

Unlike the original plugin, this mode no longer depends on interaction between two separate atoms. It only requires one person atom rather than a person atom plus another interacting atom. By using a selected target point on that character and analyzing the motion of that...

Read more about this resource...
 
MahiroOyama updated Toy Serial Controller (Fork 4 Dance Lovers) with a new update entry:

ToySerialController: Driven Dildo Fork

Passerby: What does this plugin do?

MahiroOyama: Before I introduce this plugin, I need to introduce the original ToySerialController. In short, ToySerialController can drive your real-life sex toy to move by capturing a reference pose from one object inside VaM penetrating another. But the original ToySerialController cannot drive a Dildo/CUA to move. I...

Read the rest of this update entry...
 
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
 
Last edited:
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.
 
I have been using v1 since launch and it is exactly what I wanted. I am not able to get version 2 to work. I followed the instructions, everything looks right, enabled debug mode, I see things moving, but the tcode values in the debug box never change.
I do like the simplicity of v1 and am using that for now since dancing scenes are my main use case but would like to try v2 to see if there is an improvement.
 
I have been using v1 since launch and it is exactly what I wanted. I am not able to get version 2 to work. I followed the instructions, everything looks right, enabled debug mode, I see things moving, but the tcode values in the debug box never change.
I do like the simplicity of v1 and am using that for now since dancing scenes are my main use case but would like to try v2 to see if there is an improvement.
V2 could be hard to understand.....But it worth, provide more elegant driven way than v1.
I will try update that with some initial parameter presets in the future, so people can directly use it without being confused.
 
Fantastic plugin, I've used it in a couple scenes so far, one was on a dancing character using drive mode, then other was to add toy support to tentacIes. I manage to get it working through trial and error, and a bit of luck. Your description page is a good "why should I use this" document, but I think it would be better to have usage documentation and examples. I think seeing and understanding how to use it will be all people need to understand why this fork is useful.
 
Is the source code for the plugin hosted anywhere? The plugin is excellent, but I’m wondering how to handle scenes involving multiple girls—specifically, how to automatically switch between actions involving the different girls and the boy without having to manually change the plugin's target.
 
Is the source code for the plugin hosted anywhere? The plugin is excellent, but I’m wondering how to handle scenes involving multiple girls—specifically, how to automatically switch between actions involving the different girls and the boy without having to manually change the plugin's target.
Thank you for your comment.
Technically it is hard to fully automatically switch between the targets without human intervention, because it is a must to define at which conditions we should change the target, but his is not very easy for a script to do that, even it is very hard for AIs nowadays.
But don't be upset, there is still some last resorts.
The first one is, you can use trigger to automatically change the target binding in this plugin, but you still need to define when the trigger triggers, I believe some plugins can help you to manage the triggers to let you define the proper period to trigger and switch, since triggers can switch the target, our plugin can work fine with that.
The second one is, I can change the plugin's source code, to let multiple dildos follow their own target in each, and we can blend the parameters, but we still need to tell the plugin the proper period to change the target or how to blend the parameters, since we still need to define the triggers.
So the key issue is, can you tell it very clearly and functionably that at which condition you want to switch between the targets?
 
MahiroOyama updated ToySerialController: Driven Dildo Fork with a new update entry:

v3: Alignment & Insertion-Point Offsets, New Hold Damper, Auto-Rebuild on Scene Load

This update reworks the Driven Dildo system and fixes a few long-standing rough edges:

New: Alignment Offset (Target Frame) — nudge the dildo/CUA mesh itself (Up/Right/Forward, cm) to visually match its actual shaft, without touching the driven math or measurements at all.

New: Insertion Point Offset (Dildo Frame) — independently offset the measured insertion reference point without moving the dildo body. Useful when the toy's real sensor/insertion point doesn't line up with the mesh's...

Read the rest of this update entry...
 
Back
Top Bottom