Pretty consistent for me.Please upload a screenshot or a short video. The issue needs to be reproducible in order to be resolved.
Pretty consistent for me.Please upload a screenshot or a short video. The issue needs to be reproducible in order to be resolved.
@Thogapotomus , The bug has been identified and fixed. A corrected version will be released in the next update.Pretty consistent for me.
Please upload a screenshot or a short video. The issue needs to be reproducible in order to be resolved.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!![]()
Ok, here you go!Please upload a screenshot or a short video. The issue needs to be reproducible in order to be resolved.
@DrRagon , The bug has been identified and fixed. A corrected version will be released in the next update.Ok, here you go!
Well THAT was fast!!@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 ).