Log in
Register
IncrementalTrigger

Plugins + Scripts IncrementalTrigger

Download [<1 MB]
Overview Updates (8) Reviews (9) History Discussion Dependency Usage (18)
Please correct me if I am wrong, but if target atom belongs to a SubScene, triggered actions DO NOT retain Receiver Atom and Receiver, after SubScene is loaded (all other settings are retained). As a result, all IncrementalTrigger functionality becomes useless.
As I'm sure you know, SubScenes are crucial for VAM workflow, since complex logic can be easily reused in new Scenes by utilizing them.
Please see to it.
Thank you for your amazing work! 🙏
 
14mhz said:
@DrRagon , The bug has been identified and fixed. A corrected version will be released in the next update.
Thank you for reporting the issue !!!

I have uploaded the alpha version as an attachment.
After downloading, please rename the file extension from .txt to .var before using it.
Once you have tested it and confirmed it works correctly, I would appreciate it if you could post a message on the forum.

● fixed the problem of [Random Jitter Duration (sec)] not taking effect.
● fixed the issue where the system crashes if Rise Time, Decay Time, or Peak Retention Duration are less than or equal to zero (report by @Thogapotomus ).
● resolved the problem of all Trigger ReceiverAtoms being unlinked when the plugin is part of a SubScene (report by @DrRagon ).
Click to expand...
Well THAT was fast!! o_O

Seems to be working fine! (y)
I'll test it in production as well and if I come across any flaws, I'll report back!

Thanx and keep up the good work!! 🙏
 
Would you be open the idea of adding threshold triggers? That's the one thing that I keep finding myself missing in scenes. The only good threshold triggering system I've found is the stimulation triggers in Cheesy's BodyLanguage plugin. It bundles threshold overshot/undershot and cool downs for both, as well as being able to drive variables from a specific range of the source variable.
 
14mhz said:
Threshold triggers are already provided in IncrementalTrigger as peak triggers, but if I misunderstood, could you please explain a bit more?
Click to expand...
Yeah, the peak triggers are great, but not what I'm talking about. Here's what the trigger page looks like. This whole page would be super useful to be able to use on any variable in VaM, and you can add as many triggers/pages as you want. Currently, there's nothing available that can do this which is unfortunate. Logic Bricks has a threshold trigger, but you need a seperate threshold brick for every single trigger, which would be a nightmare to organize and setup. I realize this may be outside the scope of IncrementalTrigger but I humbly request you consider something like this. You have a bunch of useful utilities already, so if it is outside the scope of IncrementalTrigger, perhaps you'd consider even making it it's own standalone plugin? Either way, thanks for your time and all of your other contributions to the community as well.
 

Attachments

  • Screenshot (73).jpg
    Screenshot (73).jpg
    505.6 KB · Views: 0
Thogapotomus said:
Yeah, the peak triggers are great, but not what I'm talking about. Here's what the trigger page looks like. This whole page would be super useful to be able to use on any variable in VaM, and you can add as many triggers/pages as you want. Currently, there's nothing available that can do this which is unfortunate. Logic Bricks has a threshold trigger, but you need a seperate threshold brick for every single trigger, which would be a nightmare to organize and setup. I realize this may be outside the scope of IncrementalTrigger but I humbly request you consider something like this. You have a bunch of useful utilities already, so if it is outside the scope of IncrementalTrigger, perhaps you'd consider even making it it's own standalone plugin? Either way, thanks for your time and all of your other contributions to the community as well.
Click to expand...
I totally agree with this proposition!! At least consider adding two or three threshold events for the time being.
I am currently using Delay triggers to simulate intermediate events occurring before Peak...
(a solution would be to use multiple Incremental Triggers, each one watching for a different Peak, but its a waste of resources...)
 
14mhz said:
@DrRagon , I’ll take some time to think it over and consider it. However, if you have any ideas about the UI flow or sketches for implementation,
I feel that would help me share the same line of thought and ease my own concerns.
Thank you.
Click to expand...
Of course!

Here's a rough idea of what the interface would look like after the addition of two threshold triggers:
 

Attachments

  • thresholds_example.png
    thresholds_example.png
    225.8 KB · Views: 0
very nice the thresholds, but could you add at least one more?
6 total would be perfect (and fit the UI nicely)
 
Last edited:
14mhz said:
Are you referring to the threshold settings? If so, could you please explain the purpose and reason why six of them are needed? I’ll be happy to review it once I understand the intention. Since I am not the scene creator, I only want to understand in what situations incremental triggers are needed and for what purposes they are best suited.
Click to expand...
I think it has to do with adding Thresholds D, E and F with the same functionality as Thresholds A, B and C ... 🤷‍♂️
 
14mhz said:
Are you referring to the threshold settings? If so, could you please explain the purpose and reason why six of them are needed? I’ll be happy to review it once I understand the intention. Since I am not the scene creator, I only want to understand in what situations incremental triggers are needed and for what purposes they are best suited.
Click to expand...
yes like DrRagon said, having more threshold levels D,E,F. I personally use 4 thresholds setup with logickbricks for my personal moaning system, and I need 4 levels, and having 2 more to have more granularity could be welcome.
 
You must log in or register to reply here.
Back
Top Bottom