Plugins + Scripts IncrementalTrigger

[Thogapotomus]

Please upload a screenshot or a short video. The issue needs to be reproducible in order to be resolved.

Pretty consistent for me.

 

[14mhz]

Pretty consistent for me.

@Thogapotomus , The bug has been identified and fixed. A corrected version will be released in the next update.
Accidentally divided a value by zero (Peak Retention Duration Time == 0) — rookie mistake, haha
Thank you for reporting the issue !!!

 

[DrRagon]

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]

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!

Please upload a screenshot or a short video. The issue needs to be reproducible in order to be resolved.

 

[DrRagon]

Please upload a screenshot or a short video. The issue needs to be reproducible in order to be resolved.

Ok, here you go!

 

[14mhz]

Ok, here you go!

@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.
Once you have tested it and confirmed it works correctly, I would appreciate it if you could post a message on the forum.

Spoiler: alpha.8 Revision history

● 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 ).

 

[DrRagon]

@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.

Spoiler: alpha.8 Revision history

● 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 ).

Well THAT was fast!!

Seems to be working fine!
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!!

 

[14mhz]

14mhz updated IncrementalTrigger with a new update entry:

IncrementalTrigger v0.8 20260519

● 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 ).

Read the rest of this update entry...

 

[Thogapotomus]

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]

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.

Threshold triggers are already provided in IncrementalTrigger as peak triggers, but if I misunderstood, could you please explain a bit more?

 

[Thogapotomus]

Threshold triggers are already provided in IncrementalTrigger as peak triggers, but if I misunderstood, could you please explain a bit more?

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.

 

[DrRagon]

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.

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...)