Plugins + Scripts Thrust Response Driver

[SwitchViewVR]

SwitchViewVR submitted a new resource:

Thrust Response Driver - Physically coherent thrust-driven body response

Description​

Thrust Response Driver is a lightweight physics plugin that adds natural, impulse-based body response to thrusting motion in Virt-A-Mate.


The receiver body moves with the thrust direction, driven directly by the source atom’s hip velocity. This results in more believable follow-through, delayed response, and subtle back-fall behavior that enhances realism without overpowering existing animations or physics.


The system is...

Read more about this resource...

 

[StaticShaka]

Wow. I've been looking for something like this for a while. Nice work!

 

[BANANANA]

When changing from Sex Pose A (Doggy Style) to Sex Pose B (Cowgirl Style), the hips would sometimes shift in an unexpected direction, possibly because the setting for A remained.
Unchecking Hips, Chest, and Head and then checking them again will allow the plugin to work in the new position.

This problem can be solved by simply creating a timeline that turns the check box off and then turns it on 0.2 seconds later.
I hope this information will be helpful if anyone is having the same problem.

This is an easy-to-use plugin that produces great results.
I'd definitely like to continue using it in the future.
Amazing!!
Thank you for making it.

 

[SwitchViewVR]

When changing from Sex Pose A (Doggy Style) to Sex Pose B (Cowgirl Style), the hips would sometimes shift in an unexpected direction, possibly because the setting for A remained.
Unchecking Hips, Chest, and Head and then checking them again will allow the plugin to work in the new position.

This problem can be solved by simply creating a timeline that turns the check box off and then turns it on 0.2 seconds later.
I hope this information will be helpful if anyone is having the same problem.

This is an easy-to-use plugin that produces great results.
I'd definitely like to continue using it in the future.
Amazing!!
Thank you for making it.

You’re absolutely right — that behavior was caused by anchors from the previous pose being kept when switching positions.


Your workaround (toggling the receiver parts via Timeline) is spot-on and does exactly what was needed internally.


I had already identified and fixed this earlier today, and I’ve just uploaded a big overhaul update that automatically detects pose changes and recalibrates anchors on the fly, so this should no longer be necessary once the update is approved.


Thanks a lot for the detailed feedback — it helped confirm the issue