Counter Block for VS2.3
VS2.3 will come with a timer and an event controller.
I would like to suggest that a counter with a trigger value be added as well.
This could be a new block or as a secondary function of the timer.
A counter would count event triggers, moving on the count value each time a measured trigger occurs until a threshold has been reached.
This could be by counting up to a defined value or counting from a defined value down to zero( like the timer).
Once the trigger value has been reached the counter will produce it's own trigger event.
This feature will provide for an event not based on timing, but upon a number of actions leaving the player guessing as to what caused the event.
Ideally the counter should be able to receive event triggers from a number of sources, 4 sources would probably be sufficient.
If simplicity of the blocks control interface is required then only event blocks would be used as triggers.
The counter should also have a reset function that can be triggered by an event.
Counters would provide for many more creative possibilities
I like this feedback
To add craziness a random relay would be fun too i.e. event trigger = RND do thing 0 or do thing 1.
To add craziness a random relay would be fun too i.e. event trigger = RND do thing 0 or do thing 1.
A continuos loop function would be a another good option for this block.
eg if the counter was set to 5, a trigger would go off on the 5th input event and then would loop back and count another 5 and trigger again and so on.
This would be good to use in a factory like situation.
eg if an event was caused every time a rotor went passed 0 degrees, the counter would keep track of the number of rotations and then cause a new event when its count had been reached. the process would repeat for ever or until turn off.
Having a counter could save on having a lot of unnecessary blocks when creating event based automations.
A continuos loop function would be a another good option for this block.
eg if the counter was set to 5, a trigger would go off on the 5th input event and then would loop back and count another 5 and trigger again and so on.
This would be good to use in a factory like situation.
eg if an event was caused every time a rotor went passed 0 degrees, the counter would keep track of the number of rotations and then cause a new event when its count had been reached. the process would repeat for ever or until turn off.
Having a counter could save on having a lot of unnecessary blocks when creating event based automations.
Replies have been locked on this page!