IncrementalTrigger

Plugins + Scripts IncrementalTrigger

Download [<1 MB]
Thank you for the update but, i have a couple requests/questions if possible =)

1. Could you also add male morphs to the list so the plugin can be used also on altfuta atoms? like this, things like "erect" or "foreskin" are missing
2. Can an option that counts the number of mouse click of your other plugin "atomclicktrigger" be added? i tried but for some reasons, i can't find a way to have incremental trigger see how many times i click on the atom with "atomclicktrigger". I've setup clicktrigger as usual and works "alone" but i can't see a way to have it work with incremental trigger..

thank you in advance =)
 
Thank you for making this. Really fun. If you make an update for this, would you consider adding an "invoke time" slider?
 
which resource was that "breast supa big"? can i have them xD
 
I absolutely love it. I created a similar effect in my years-old scene, requiring a slew of plugins chained together - this would easily hand the use case (and many others). I just used it with Penetration Counter to create some pretty create procedural effects.

My only suggestion is this:

IMO this is a crucial and universal plugin to handle any pressure systems, not just sex-specific side-effects. However, when you do, you're left using "soft" "hard" and "deep" (sexual and arbitrary). I'd suggest renaming them to something more universal/ambiguous personally.

Soft -> Medium -> Hard (appropriate for general pressure effects)
Small -> Medium -> Large (appropriate for size of effect)

or something like that...

This would basically make it into my scenes as a progressive meter to control any decaying levels. For example:

Moods (e.g. an annoyance meter)
Orgasm buildup (but not directly related to specific penetration events)
Sweat (perhaps based on activity based triggers)
 
Was literally going to suggest a rise control (opposite of decay) and see you already added that... epic.

You Are Amazing Love It GIF by Late Night with Seth Meyers
 
Loving using this plugin to automate expressions!

Can I make a request? It seems decay time is set to be an integer? For the expressions, I'm using random increase (triggered by a timer) with a pretty low end value and quick decay on IncrementalTrigger. Then as the animation speeds up I lower the end value so that the expressions get stronger, but as that happens a decay of 1.0 is too slow so the character gets stuck at the end value.

So, would it be possible for a decay value of 0.1?
 
Is there any way to possibly use this to control floats on another plugin? I want to use MacGruber's PostMagic in conjunction with the incremental trigger to do some increasing bloom effects during deep penetration, to sort of simulate that "swimmy" feeling of pleasure by blowing out some of the stronger light sources in the scene on deep thrusts, i.e. as the sex gets deeper and more intense, the bloom rises with each thrust (with this plugin driving the increase and allowing it to fall off when things slow down). But I can't seem to figure out if there's a way to hook to those floats on the "Empty" atom that the PostMagic plugins are attached to.

Edit: Never mind the above, I got it figured out. For others trying to do similar, I had to go into the plugin, find the "Normalized Value" trigger, and set up a transition between the lowest and highest points for the other plugin I wanted to control, e.g. for my case, Bloom 0.00 to 4.00. Then, testing with increases on the scale correctly causes the bloom intensity to increase on each hit; decay allows it to fall gradually. Works great, and adds some nice effects!
 
Last edited:
Totally agree with the decision to remove the direct morph tie-in... definitely not the core focus, and super easy for a user to add using the variable triggers anyway.

Love the new interface direction!
 
If peak hold time to less than 1sec and decay and decay after peak are both on, VaM instantly crashes when peak is hit for me. I've tested it multiple times and in an empty scene. It's odd because sometimes going under 1sec works, so it might be lower value threshold than 1 that causes the crash, but it's always been under 1 for sure when it's happened to me.

Also the new design is sick. This is easily one of my favorite and most useful plugins.
 
Back
Top Bottom