This module is helpful for all tasks which require the notion of: "Do that, then that, then that.." and so on. Its often hard to patch something like this, and patches tend to get complicated if such "timing things" are involved, but its often needed in projects. This is no replacement for Timeliner (Animation) or Automata (Animation), use them if it gets more complex, involvig conditional jumps from one state into another.
now as a plugin with action progress output.
cool one thanks ;]
nice module and typical tebjan patching style inside :)
although, its almost tidy
cool thanks! we just need something like
wow, very helpful - cool module _ thanks tebjan
It's only > beta28?
ah, probably yes... i used a new time property of the IHDEHost to get the frame time. which beta are you using?
This will be incredibly handy, can't wait to get to use it!
I've few patches are still with b27.2
I missed the previous version, maybe you could keep it downloadable as well.
ok, fixed one and it should be compatible to b27 now
Yes...Thanks a lot
do you think would be possible to implement OnEnd event for every single Action? Could be done the same way/strings as for Timeliner. Would be very useful to make simple cue sequencer
that is the 'Action Last Frame' output. its a bang before the next action starts.
let's say i want to have simple "Pause" at the end of Process 1
As workaround i can patch Process 2 as "pause" with Action Time -1, but maybe there is more elegant solution instead of patching every OnEnd action as separate process
having 'pause' states in between is good thinking. that is actually the idea of the -1 actions, to stop the process and continue whenever another condition is met. to start the next action then, you press 'Next'.
the more elegant solution would be to have another bool input which defines whether the next action will start automatically... maybe i will find the time after node13 to code it.
@tonfilm: would be great
@velcrome: did not find anything wrong in your patch-runs in loop as expected
greatly appreciate this "chapter-wise" approach, however a sub-process directly on the first pin doesn't seem to work for me, neither do two sub-processes in a row.
hello jim, please start a forum thread and post a patch. thanks!
this is great but a frame based switch would make it even greater!
what do you mean by framebased switch? if your in the mood of coding, the sources are shipped with the plugin, so you can modify it to your needs.
hey Ton, yeah not clear from me. I meant frame based timings. So rather than - do this, wait 1 second, do that. Do this, wait 20 frames, do that.
Wow, this one is going to solve my "connect some patches together in loop" problem :) Thank you.
A little something concerning what xd_nitro asked for.
Seems like the Timings are system based (which is good, so it's tight), but I just had the issue that I had a little framedrop and the timings weren't in sync with what's on screen anymore.
Will fix the framedrop anyway (some time), but it would be cool to have the possibility to make the timings dependend on the frames/mainloop to catch those drops.
you can use the mainloop in increment time mode, this will bind all time dependent nodes to frames (if they are programmed correctly).
This is so useful and needs updating!
can you elaborate whats not working ATM?
anonymous user login