@StyleMavin @babul If you have time to play around with the "Use Parent Control" functionality and let me know how it goes, please do!
Ok, I got to test it a little. At first I was confused that align parent to thrust was forcing my origin empty atom to have "bad" rotation of my hips, but it works exactly as advertised. Looks like it only actually aligns when you press the buton while plugin is active and motion is happening already, so gotta watch out for that. Once I figured that out, it's nice. I could choose just one axis and force my controller to move perfectly along that.
Could you extend that to AutoGensThruster as well? I tested my animation with both and while I can move hips perfectly vertically from its initial position now with AutoThruster, if I use gens thruster aimed at mouth with AutoGensThruster, it will always start too high, because it's completely dependant on rotation of the head. If you could simply move/rotate mouth/vagina/anus target, you could possibly get rid of target adj. left/right and down/up as well. But in this case I think rotation is the issue. In my BJ animation where head is sideways, but slightly pointing up, male will start way higher. Idea would be to change head origin point so it's perfectly vertical (despite head pointing up), and it would work just like the updated AutoThruster. Pretty nice for sideways blowjob at an angle or something.
For what it does now, I think it's pretty good now, I think. No more tiresome adjusting angles so it works. If you could make changing of origin position/rotation in AutoGensThruster possible, and maybe in the future having control of 'in-out' float, that would already cover pretty much any use case I think. To give one more example that just came to me: right now you can nicely set up start/end angles in the plugin, but it's a smooth curve. If you had access to that float mentioned before, you could simply animate your dummy atom that acts as a parent to e. g. have the same rotation at 0.0 to 0.8, but then change the rotation at 0.8, so you could achieve sudden twist at the end if you wish so.. or sudden extra movement in some direction, that would work nicely with automated thrust. Controlling it like that instead of messing with hip keyframes in Timeline would be pretty elegant I think. (So in the example above, 0-1 out-in float would be passed to 'Set Time' of Timeline instance that's attached to the thrust origin controller. Not sure if it's possible, but if you could have VAMMoan instead take control of that 'out-in', you could simply use VAMMoan to also animate the thrust origin. Maybe a checkbox that doesn't touch the float when checked and waits for input from the user <<so if you checked it but didn't animate it yourself, there would be no movement at all if you activated the thrust>>, and when unchecked, it would provide its own motion and ignore other input, in case you don't want to control it with 3rd party)
Anyway, sorry for a wall of text. This update is pretty good and a big improvement.
