Plugins + Scripts AutoThruster Plus

[Dragontales]

I was having issues with reinsert/pullout and setting up timeline keyframes, I was using the old vinput settings (all penis controls off) so here's what you need.

Penis Tip - Position: OFF, Rotation: OFF
Penis Mid- Positon: OFF, Rotation: OFF
Penis Base - Position: OFF, Rotation: ON
Penis Tip - JointDriveMaxForce: 100, JointDriveSpring:100 (to your own taste)

But once you keyframe it, it works. I even setup a little configuration button trigger for simplicity.
View attachment 544572

yeah, so much of VAM's functionality depends on how nodes are set up. Physics, etc I still may implement those settings right into the plugin so that it doesn't mess up others that may not know.

 

[GGnome]

When I set the Joint Drive Spring to max when I enabled thrust it resets to 100 and bounces down to about 70 and back

That's probably caused by bodylanguage, happened to me also.

 

[rarirurero69]

First of all, thank you for creating this plugin.
While using it, there’s one feature I’d really like to request: immediate-response preset save/load slots.


The current method—saving, setting a preview, and entering a name is perfectly fine, but it would be even better if there were multiple quick-save slots. With slot-based saving, I could use Timeline or Trigger functions so that pressing a button instantly switches the values, making it much easier to see animation changes in real time.


I would really appreciate it if you could consider adding this feature.

 

[Dragontales]

First of all, thank you for creating this plugin.
While using it, there’s one feature I’d really like to request: immediate-response preset save/load slots.


The current method—saving, setting a preview, and entering a name is perfectly fine, but it would be even better if there were multiple quick-save slots. With slot-based saving, I could use Timeline or Trigger functions so that pressing a button instantly switches the values, making it much easier to see animation changes in real time.


I would really appreciate it if you could consider adding this feature.

Hi. Glad you like the plugin. I have thought about adding preset slots and still might add them, but wanted to make sure you knew you could trigger loading the presets instantly. My personal issue with slots is that you'd be locked into a maximum amount (like three or so) whereas the current system means you could trigger any number of presets via trigger. My demo scene that I uploaded the other day shows how to do this. Let me know if that helps or if there's a reason that the slot method would be better/easier for you.

 

[rarirurero69]

Hi. Glad you like the plugin. I have thought about adding preset slots and still might add them, but wanted to make sure you knew you could trigger loading the presets instantly. My personal issue with slots is that you'd be locked into a maximum amount (like three or so) whereas the current system means you could trigger any number of presets via trigger. My demo scene that I uploaded the other day shows how to do this. Let me know if that helps or if there's a reason that the slot method would be better/easier for you.

Thanks to the demo version you mentioned, I learned how to load presets through LoadPresetPath, and I was able to get exactly what I wanted. Thank you for your help

 

[Dragontales]

Thanks to the demo version you mentioned, I learned how to load presets through LoadPresetPath, and I was able to get exactly what I wanted. Thank you for your help

Happy to help! Glad you got it sorted.

 

[yuezy3]

Please tell me, what should i do to make a female character ride a male character. i load this plugins in a female, and this female dont move.

 

[Dragontales]

Please tell me, what should i do to make a female character ride a male character. i load this plugins in a female, and this female dont move.

Hi. The plugin can only be applied to a male (or futa) figure. To have the female do the thrusting, you would either use the toggle to turn off the male thrust entirely, or minimize it's movements with the in and out distances. You make her thrust using the "Extra Body motions" sliders. I have a demo scene up on the hub here that you can download and take a look at to see how to implement it for that. Let me know how you make out.

 

[rarirurero69]

Hello, I have a question.
Is there a way to reset the cycle duration value?
For example, I save Preset 1 with a cycle duration of min 0.25, max 0.8, and Preset 2 with the max value set to 0.4. Then I use a timeline trigger to loop playback.
However, when switching back from Preset 2 to Preset 1, the speed value from Preset 1 is not applied, and the speed value from Preset 2 continues to remain active.
I would like to know if there is a way to resolve this issue.

 

[Dragontales]

Hello, I have a question.
Is there a way to reset the cycle duration value?
For example, I save Preset 1 with a cycle duration of min 0.25, max 0.8, and Preset 2 with the max value set to 0.4. Then I use a timeline trigger to loop playback.
However, when switching back from Preset 2 to Preset 1, the speed value from Preset 1 is not applied, and the speed value from Preset 2 continues to remain active.
I would like to know if there is a way to resolve this issue.

The presets should be storing all the slider settings. Can you share the scene with me so I can take a look? I will also take a look under the plugin's hood to see if there's anything wrong.

 

[rarirurero69]

The presets should be storing all the slider settings. Can you share the scene with me so I can take a look? I will also take a look under the plugin's hood to see if there's anything wrong.

Here https://gofile.io/d/mAeeLN

Additionally, I would like to know if there is a way to reduce or smooth out the snapping/jumping issue that occurs when transitioning to the next linked action, especially when there is a large difference in speed values.

 

[Dragontales]

Here https://gofile.io/d/mAeeLN

Additionally, I would like to know if there is a way to reduce or smooth out the snapping/jumping issue that occurs when transitioning to the next linked action, especially when there is a large difference in speed values.

Thanks. I'll check it out in the morning and let you know what I find.

 

[Dragontales]

The var file

Here https://gofile.io/d/mAeeLN

Additionally, I would like to know if there is a way to reduce or smooth out the snapping/jumping issue that occurs when transitioning to the next linked action, especially when there is a large difference in speed values.

I've looked at your file and I'm honestly still stumped about why that scene is having issues. The one thing I'm thinking is that somehow Timeline is causing some sort of conflict with my plugin. I'm going to try setting up the triggers into VAMStory's Director plugin and then using timeline to trigger that instead to see what happens.

 

[Dragontales]

Here https://gofile.io/d/mAeeLN

Additionally, I would like to know if there is a way to reduce or smooth out the snapping/jumping issue that occurs when transitioning to the next linked action, especially when there is a large difference in speed values.

AH!! I found the issue. You have Duration Change rate set to zero. This means that the thrust duration never changes. So that means even setting a min and max....the thrust duration won't change within those parameters. It ALSO means that loading another preset that's also set to zero for duration change, the new duration of the thrust won't change either. I should probably update this plugin so that setting can't be set to zero. If you do want zero variability in the thrust speed within a preset, set the min and max to be the same. Then do the same for the second preset. Allowing a duration change for each should ALSO address the immediate snap you're seeing. Can you try those things and let me know how you make out?

 

[rarirurero69]

AH!! I found the issue. You have Duration Change rate set to zero. This means that the thrust duration never changes. So that means even setting a min and max....the thrust duration won't change within those parameters. It ALSO means that loading another preset that's also set to zero for duration change, the new duration of the thrust won't change either. I should probably update this plugin so that setting can't be set to zero. If you do want zero variability in the thrust speed within a preset, set the min and max to be the same. Then do the same for the second preset. Allowing a duration change for each should ALSO address the immediate snap you're seeing. Can you try those things and let me know how you make out?

That makes sense. In my case, I want consistent, non-random motion, and then have the movement speed increase in the next stage. Because of that, I set the Duration Change Rate to 0.

However, when I allow a Duration Change Rate and set a min and max range, the immediate snapping becomes very severe during transitions, and the distance gap increases, which completely breaks the motion. That’s why I found that keeping a very small difference between the min and max values in Preset 1, while allowing a Duration Change Rate, felt like the least problematic workaround.

Separately, even when I am not using the timeline and instead adjusting the values in real time directly within the plugin, I noticed an issue where if I reduce the max speed to 0.6 and then later increase it back to 1.0, the reduced speed value continues to be applied. Because of this behavior, I assumed that the plugin might be structured this way by design, and I wanted to ask if there is a proper way to handle or reset this behavior.

 

[rarirurero69]

AH!! I found the issue. You have Duration Change rate set to zero. This means that the thrust duration never changes. So that means even setting a min and max....the thrust duration won't change within those parameters. It ALSO means that loading another preset that's also set to zero for duration change, the new duration of the thrust won't change either. I should probably update this plugin so that setting can't be set to zero. If you do want zero variability in the thrust speed within a preset, set the min and max to be the same. Then do the same for the second preset. Allowing a duration change for each should ALSO address the immediate snap you're seeing. Can you try those things and let me know how you make out?

When I press the plugin’s Reload button and then load Preset 1 again, the speed is applied correctly. I tried to replicate this behavior using timeline triggers, but I couldn’t find anything equivalent. I tested toggling Enabled and Enabled Thrust on and off via timeline triggers, but it doesn’t behave like a reload.

If possible, it would be great to have immediate speed changes, similar to how the original Auto Thruster plugin worked. Alternatively, having a reset or initialize button, similar to the reload function, would be very helpful. That way, I could use a trigger to reset the plugin at the start frame and then play from Preset 1.

If this is a difficult request, please feel free to ignore it. I really appreciate the plugin as it is—thank you very much for making it available for free

 

[Dragontales]

When I press the plugin’s Reload button and then load Preset 1 again, the speed is applied correctly. I tried to replicate this behavior using timeline triggers, but I couldn’t find anything equivalent. I tested toggling Enabled and Enabled Thrust on and off via timeline triggers, but it doesn’t behave like a reload.

If possible, it would be great to have immediate speed changes, similar to how the original Auto Thruster plugin worked. Alternatively, having a reset or initialize button, similar to the reload function, would be very helpful. That way, I could use a trigger to reset the plugin at the start frame and then play from Preset 1.

If this is a difficult request, please feel free to ignore it. I really appreciate the plugin as it is—thank you very much for making it available for free

Earlier today I worked on a couple updates. One added a reset to defaults button. I think that's what you're asking for. So that should come out tonight or tomorrow. I'll look into some of those other things you mentioned

 

[rarirurero69]

Earlier today I worked on a couple updates. One added a reset to defaults button. I think that's what you're asking for. So that should come out tonight or tomorrow. I'll look into some of those other things you mentioned

Thank you, I’m looking forward to it.

 

[Dragontales]

Thank you, I’m looking forward to it.

Ok....I believe I know what the issue is for you, and I'm pretty sure it's a simple misunderstanding of the sliders and what they do. I'll try to explain as best I can so it's hopefully clearer. I've also uploaded a fixed version of the sample scene you gave me which can be found here - https://drive.google.com/file/d/1I6KA_bbRNx5ywMubQ2pWqTFHYP-Aei8z/view?usp=drive_link

We will start with the top section first (as you can see, I've added a reset button which will be uploaded right after I make this post)
- To start, this plugin works on the principle of "cycles". In other words, a cycle consists of a thrust in and a thrust back out. In order to keep cycles consistent and not allow snapping, the plugin does have built in to it, a feature that doesn't allow changes before a cycle is complete and you can set how many cycles per random setting before it changes to a new random. Since you don't want the random, we can still achieve this by setting the Speed Hold Cycles to just 1.

Starting at the top of the Thrust Cycle Controls.
1 - Initial Entry Duration: This setting ONLY works when going from Thrust being off to Thrust enabled. It's the duration of time when it moves the penis base node from where it is when off, to where it needs to be for the thrust. This plugin, much like the original, aligns the penis base node with two points of the target (which you can turn on in the plugin to see). This is what allows the penis to stay in line with the target since the pose itself may not be perfectly aligned. So to avoid a snap from thrust off to thrust on, we set a duration. I noticed you had these set at zero, meaning you get a snap from resting location to thrust location.
2 - Speed Ramp Duration: This works in tandem with the first setting and is also designed just for starting up the thrust. Instead of going from zero thrust to full thrust, it allows the cycles to ramp up in intensity over a set amount of time. I would suggest having some sort of time set for this, instead of zero. It doesn't have to be the default three seconds, but I'd avoid going less than 1 to avoid snapping behavior.
3 - Cycle Duration Min and Max sliders: As mentioned above, cycles are a complete in/out of a thrust. These sliders control the minimum amount of time a cycle takes and the max amount of time a cycle can take. If you don't want any randomization, you set these to be identical. Slower thrusts would have slower durations. Faster thrusting would have smaller durations. I believe these may have been where you were confused because in your sample scene, these were still set to the defaults.
4 - Duration % in: This slider changes how much of the entire thrust cycle (again, in and then out) is spent on the IN part of the thrust. Default is 40 percent, but you can change this to .5 for even time between in and out.
5 - Duration Change Rate: How fast the Durations (set by the min and max) change over time (this will work in conjunction with the Speed Hold Cycles sliders that I'll mention below) Since you want no variation, and we set the min and max to the same, this would have little effect, except when we load a new preset, so don't set this to zero (actually, I made it impossible to do so in the new version). In your case, think of this as how fast the preset will change from a slower speed to a faster speed when you load it. nothing in life is immediate. Setting this to a reasonable speed will prevent snaps.
6 - Duration range bias: If you WERE using randomization within a preset, this slider will allow the plugin to choose random durations closer to the min or max depending on how it's set. Default is .5 which means an even distribution of random durations within the set parameters of min/max. If both min and max are set identical as mentioned above, then changing this won't really do anything (not entirely true, but for the sake of the cycle speed/duration it is)
7 - Speed Drift Amount: This is very similar to the Duration Change Rate, except that it allows small micro changes in thrust durations for less "robotic" feeling thrusts. You can set this to zero, and it will just mean there's zero subtle variation. It shouldn't impact the change from one preset to another like the one above it does.
8 - Speed Hold Cycle Min and Max: As mentioned above, to prevent sudden changes during a thrust, this plugin works on ensuring a complete cycle before things change to a new random or loaded preset. The default for these allows for several cycles before allowing a change. In your case, you're looking to have the speed/cycle duration change as soon as you load the new preset. For this, setting these to 1 for both means that it will still allow the previous cycle to complete before allowing the new preset cycle to change it. Again, this is to allow for a smooth transition from one speed to the next.

Since the next section is also important for the thrust, I'll mention those controls too.
9 - Distance In and Out: As mentioned above, this plugin aligns the penis base node with two points on the target (which you can visibly see if you turn them on in the plugin). Using that "path", the plugin will move the penis base node from the set "out position" to the set "in position" and then back to the Out, completing a full cycle. You can adjust these points with these sliders. If the thrust isn't going in enough, move the Distance In slider up. If the thrust is pushing in too far, pull this back. Same for the out. It's important to note that on the initial movement when you turn thrust on, it moves the penis base node from the resting position of whatever pose is set, to this OUT point. This is why having a duration set in that setting above is vital to avoid a snap. It's basically aligning the penis with the target. When thrust is disabled, it will use that same duration to take it from the thrust path, back to the resting place of the set pose.
10 - Distance Random %: This allows for randomizing the in and out points of the path based on a percentage for less robotic thrusting. If you want consistent thrusts, leave this at zero.
11 - Target Tracking Smoothing - Since the target moves due to being thrust at and perhaps animations set on it, this slider allows for how smoothing the penis base tries to stay with the target path. If it's too low, thrusting may feel jittery if there's a lot of motion on the part of the target. IF she's not moving much, then this isn't as important.
12 - Distance Compression at Max Speed: This label might be confusing. Basically, this works in tandem with the Cycle Duration sliders above. When you're allowing for Randomization, and have a faster duration and a slower duration, this slider sets how much the Distance IN and OUT points compress together on the path, meaning smaller thrusts. In the real world, faster thrusting often means the distance in and out gets smaller. This slider is to mimic that behavior. If you have in and out points set....this compresses them together for the faster thrusts. What this means for you is that if this has a setting other than zero, even though your min and max are identical, the plugin is still choosing a random duration (though it doesn't change since they're identical) and some thrusts might have that compression. You might want to up this so you do get a little variation, or you may want to set it to zero so there's none.
13 - Distance offset at Max Speed: This, like the Compression slider also works in tandem with the Cycle Duration. Setting this to zero means the "offset" of the in and out doesn't change. But changing it to a positive or negative value changes the In and Out offset the closer the cycle gets to the shorter set duration. Again, in your case, if min and max are identical, there's still a "range" of speeds the cycle is randomizing (even though they're the same) and having this set to a non-zero setting will still impact your thrusts.

Let me know if all that makes sense.

 

[rarirurero69]

Ok....I believe I know what the issue is for you, and I'm pretty sure it's a simple misunderstanding of the sliders and what they do. I'll try to explain as best I can so it's hopefully clearer. I've also uploaded a fixed version of the sample scene you gave me which can be found here - https://drive.google.com/file/d/1I6KA_bbRNx5ywMubQ2pWqTFHYP-Aei8z/view?usp=drive_link

We will start with the top section first (as you can see, I've added a reset button which will be uploaded right after I make this post)
- To start, this plugin works on the principle of "cycles". In other words, a cycle consists of a thrust in and a thrust back out. In order to keep cycles consistent and not allow snapping, the plugin does have built in to it, a feature that doesn't allow changes before a cycle is complete and you can set how many cycles per random setting before it changes to a new random. Since you don't want the random, we can still achieve this by setting the Speed Hold Cycles to just 1.

Starting at the top of the Thrust Cycle Controls.
1 - Initial Entry Duration: This setting ONLY works when going from Thrust being off to Thrust enabled. It's the duration of time when it moves the penis base node from where it is when off, to where it needs to be for the thrust. This plugin, much like the original, aligns the penis base node with two points of the target (which you can turn on in the plugin to see). This is what allows the penis to stay in line with the target since the pose itself may not be perfectly aligned. So to avoid a snap from thrust off to thrust on, we set a duration. I noticed you had these set at zero, meaning you get a snap from resting location to thrust location.
2 - Speed Ramp Duration: This works in tandem with the first setting and is also designed just for starting up the thrust. Instead of going from zero thrust to full thrust, it allows the cycles to ramp up in intensity over a set amount of time. I would suggest having some sort of time set for this, instead of zero. It doesn't have to be the default three seconds, but I'd avoid going less than 1 to avoid snapping behavior.
3 - Cycle Duration Min and Max sliders: As mentioned above, cycles are a complete in/out of a thrust. These sliders control the minimum amount of time a cycle takes and the max amount of time a cycle can take. If you don't want any randomization, you set these to be identical. Slower thrusts would have slower durations. Faster thrusting would have smaller durations. I believe these may have been where you were confused because in your sample scene, these were still set to the defaults.
4 - Duration % in: This slider changes how much of the entire thrust cycle (again, in and then out) is spent on the IN part of the thrust. Default is 40 percent, but you can change this to .5 for even time between in and out.
5 - Duration Change Rate: How fast the Durations (set by the min and max) change over time (this will work in conjunction with the Speed Hold Cycles sliders that I'll mention below) Since you want no variation, and we set the min and max to the same, this would have little effect, except when we load a new preset, so don't set this to zero (actually, I made it impossible to do so in the new version). In your case, think of this as how fast the preset will change from a slower speed to a faster speed when you load it. nothing in life is immediate. Setting this to a reasonable speed will prevent snaps.
6 - Duration range bias: If you WERE using randomization within a preset, this slider will allow the plugin to choose random durations closer to the min or max depending on how it's set. Default is .5 which means an even distribution of random durations within the set parameters of min/max. If both min and max are set identical as mentioned above, then changing this won't really do anything (not entirely true, but for the sake of the cycle speed/duration it is)
7 - Speed Drift Amount: This is very similar to the Duration Change Rate, except that it allows small micro changes in thrust durations for less "robotic" feeling thrusts. You can set this to zero, and it will just mean there's zero subtle variation. It shouldn't impact the change from one preset to another like the one above it does.
8 - Speed Hold Cycle Min and Max: As mentioned above, to prevent sudden changes during a thrust, this plugin works on ensuring a complete cycle before things change to a new random or loaded preset. The default for these allows for several cycles before allowing a change. In your case, you're looking to have the speed/cycle duration change as soon as you load the new preset. For this, setting these to 1 for both means that it will still allow the previous cycle to complete before allowing the new preset cycle to change it. Again, this is to allow for a smooth transition from one speed to the next.

View attachment 561775

Since the next section is also important for the thrust, I'll mention those controls too.
9 - Distance In and Out: As mentioned above, this plugin aligns the penis base node with two points on the target (which you can visibly see if you turn them on in the plugin). Using that "path", the plugin will move the penis base node from the set "out position" to the set "in position" and then back to the Out, completing a full cycle. You can adjust these points with these sliders. If the thrust isn't going in enough, move the Distance In slider up. If the thrust is pushing in too far, pull this back. Same for the out. It's important to note that on the initial movement when you turn thrust on, it moves the penis base node from the resting position of whatever pose is set, to this OUT point. This is why having a duration set in that setting above is vital to avoid a snap. It's basically aligning the penis with the target. When thrust is disabled, it will use that same duration to take it from the thrust path, back to the resting place of the set pose.
10 - Distance Random %: This allows for randomizing the in and out points of the path based on a percentage for less robotic thrusting. If you want consistent thrusts, leave this at zero.
11 - Target Tracking Smoothing - Since the target moves due to being thrust at and perhaps animations set on it, this slider allows for how smoothing the penis base tries to stay with the target path. If it's too low, thrusting may feel jittery if there's a lot of motion on the part of the target. IF she's not moving much, then this isn't as important.
12 - Distance Compression at Max Speed: This label might be confusing. Basically, this works in tandem with the Cycle Duration sliders above. When you're allowing for Randomization, and have a faster duration and a slower duration, this slider sets how much the Distance IN and OUT points compress together on the path, meaning smaller thrusts. In the real world, faster thrusting often means the distance in and out gets smaller. This slider is to mimic that behavior. If you have in and out points set....this compresses them together for the faster thrusts. What this means for you is that if this has a setting other than zero, even though your min and max are identical, the plugin is still choosing a random duration (though it doesn't change since they're identical) and some thrusts might have that compression. You might want to up this so you do get a little variation, or you may want to set it to zero so there's none.
13 - Distance offset at Max Speed: This, like the Compression slider also works in tandem with the Cycle Duration. Setting this to zero means the "offset" of the in and out doesn't change. But changing it to a positive or negative value changes the In and Out offset the closer the cycle gets to the shorter set duration. Again, in your case, if min and max are identical, there's still a "range" of speeds the cycle is randomizing (even though they're the same) and having this set to a non-zero setting will still impact your thrusts.

View attachment 561777

Let me know if all that makes sense.

This is an amazingly detailed and kind explanation thank you so much!! I’ll try using the plugin while reading through the instructions.

 

[Dragontales]

This is an amazingly detailed and kind explanation thank you so much!! I’ll try using the plugin while reading through the instructions.

Please let me know how you make out. Also, I haven't uploaded a new version just yet. I've been toying with better transitioning when loading a preset during thrust.

 

[Dragontales]

Dragontales updated AutoThruster Plus with a new update entry:

Some more tweaks and additions.

1 - Added a reset button to reset all settings to default
2 - Added a bit more smoothing to when presets are loaded during active thrust (will still likely work on this more)
3 - Tweaked Duration Change Rate to dissallow setting this to zero
4 - Added and OUT Phase motion percentage for the Thruster (this already existed for the Target person)
5 - increased the Out Phase Motion percentage up to 2 to allow for up to twice as much motion on the OUT phase as the In phase (I found I needed this...

Read the rest of this update entry...

 

[rarirurero69]

Please let me know how you make out. Also, I haven't uploaded a new version just yet. I've been toying with better transitioning when loading a preset during thrust.

Dragontales updated AutoThruster Plus with a new update entry:

Some more tweaks and additions.



Read the rest of this update entry...

After understanding your explanation and testing it as you described, I was able to get the behavior I was aiming for.

For the initial start, I set Initial Entry Duration to 0.20 and Speed Ramp Duration to 1.00. I then set Cycle Duration Min/Max to the same value, with Duration Change Rate set to 1.0 and Speed Hold Cycles Min/Max set to 1.0. I also set Distance Random % to 0, Distance Compression at Max Speed to 0.00, and Distance Offset at Max Speed to 0.00.

After saving this as Preset 1, I reduced the Cycle Duration Min/Max values and saved it as Preset 2. When switching between the presets, I was able to see a smooth transition without any snapping issues.

After completing my tests, I downloaded and reviewed the file you shared, and I found that it matched exactly with the approach I had understood.

Thank you so much for your detailed explanation and kindness. Thanks to your help, the issue has been resolved, and I’m now able to create better animations.

 

[Dragontales]

After understanding your explanation and testing it as you described, I was able to get the behavior I was aiming for.

For the initial start, I set Initial Entry Duration to 0.20 and Speed Ramp Duration to 1.00. I then set Cycle Duration Min/Max to the same value, with Duration Change Rate set to 1.0 and Speed Hold Cycles Min/Max set to 1.0. I also set Distance Random % to 0, Distance Compression at Max Speed to 0.00, and Distance Offset at Max Speed to 0.00.

After saving this as Preset 1, I reduced the Cycle Duration Min/Max values and saved it as Preset 2. When switching between the presets, I was able to see a smooth transition without any snapping issues.

After completing my tests, I downloaded and reviewed the file you shared, and I found that it matched exactly with the approach I had understood.

Thank you so much for your detailed explanation and kindness. Thanks to your help, the issue has been resolved, and I’m now able to create better animations.

Glad to be of help. Vam is very complex and understanding nodes, and motions and all that stuff is already complicated, let alone adding a plugin that has a ton of controls on top of it. lol. I've been using VAM since almost the beginning so it sort of comes naturally now, but I know that it has a steep learning curve. Glad the explanation helped. I'll likely copy what I wrote into the main page of the plugin for others eventually.

 

[rarirurero69]

Glad to be of help. Vam is very complex and understanding nodes, and motions and all that stuff is already complicated, let alone adding a plugin that has a ton of controls on top of it. lol. I've been using VAM since almost the beginning so it sort of comes naturally now, but I know that it has a steep learning curve. Glad the explanation helped. I'll likely copy what I wrote into the main page of the plugin for others eventually.

I completely agree with you. New and improved plugins keep coming out, and learning each one isn’t always easy. However, compared to Blender, VaM is much easier to learn, which is why I keep using it.

Your plugin is amazing as well. Being able to apply motion directly to the character means I no longer have to manually set animation keys one by one in the timeline. On top of that, the randomization feature really surprised me when it was first released.

At the same time, I did run into some issues, and I spent quite a while wondering whether I should ask about them or not. After seeing how kind and helpful you are, I honestly wish I had asked sooner. Now that the problem has been resolved, I feel really great about it.

Thank you very much.