To use the template, vvvv must be equiped with addonpack and DX11 Pack.
List of shortcuts:
Mouse input is on by default, to use with touch screen, first open config.ini and find
and change to
The contribution is free for use, but comes with no support.
Please contact us for commercial support.
Thanks for sharing
Will try it
a bit more about the contribution
nice template, i can see some similarities to our template structure. definitely inspiring.
any reason why you still use the old automata ?
good work ¡¡ thanks.
this is madness, thanks for sharing!
@u7angel Hi! Thanks for appreciation! I think every professional user / company has similar template and all together we have a chance to create "The Template"
You made the great tool - it already has tools like GetState and ResetToState which were in our todo list for too long, but when I started with the new Automata I found two things:
1/ I'm too conservative about ctrl-z/ctrl-c/ctrl-v
2/ We actually use a different method of logic parsing into vvvv, so the new version isn't save much time for us. I'll try to explain:
We use a keyword to describe a state. Let's say "Game" is a key word. Next we create many substates like "Game-Idle", "Game-Pause", "Reset-Game" etc.
Please have a look at the pic I made for the example:
Next we use Sift (String) with Comparison set to "ContainsAny" so all of the states will give us the single "State-Game" with single transition.
Next we use =(String) or Sift (String) with Comparison set to "MatchesAny" to define exact substates like "Game-Pause", "Reset-Game" etc.
Note to Reset-Game and Set-Game with 0 time transition. For vvvv they work like 1 frame bangs, but they are very different of TogEdge and different of another in-out/change bangs, because they are solid defined states. So we can get as many bangs as needed, while staying in the same state "Game" with no extra AND OR NOT patching.
With this method we can make changes much easier and faster. Thing like
now comes much-much easier and not a problem for us and a client anymore.
@bo27 , so if i understand you right, you want some state grouping, something like nested statemachines in states or even simpler: regions. to sort of group states and tell wether the active state belongs to a certain group of states, right ?
if so, yes this is on my list, we need that too. just working out what would be the most intuitive way of defining this. in the end, you would'nt need all this sift stuff.
@u7angel yes, you're right! great minds think alike!
In our todo list is something similar to GetState plugin from your Automata, but with access to nested states and probably with auto S node generator (same as we done with configurator from the Template).
But we don't even start it yet.
Thanks for this!
anonymous user login