Currently I have a setup where I have TheEngine at the beginning of my script to interate an integer. The integer feeds into an offset distance of a curve on a surface. That curve then has customized shapes created along its length via a revolve surface. That resolve surface is then input into a bake vb block.
Currently I have to set TheEngine block to around a 20 second pause between interations because at the end of its iterations (when the integer gets big), it offset and revolving takes quite a while, but if it iterates before the revolves finishes it won't bake. This ends up making this functino take quite a long time to complete even tho the initial couple dozen iterations only need like 5 seconds tops. I've thought of maybe plugging an Engine into the engine to iterate the delay times so the delay time increments too.... but this seems like a sloppy solution at best that would take quite a bit of troubleshooting and skirt the real issue.
The way the timer component works should do something more like what I want, where the whole entire set will iterate as soon as the last bake component finishes, but I can't seem to figure out how the Timer component works and there is literally no documentation on it as best I can tell besides the tooltip.
Any suggestions? I'll upload a definition in a bit when I get back from this test.
are you even just a little bit familiar with C# or Vb?
What you could do is listen to the SolutionComplete event and then start a new solution (I think I remember it was called like that) with due caution.
- Giulio
_____________________
giulio@mcneel.com
McNeel Europe, Barcelona
Giulio Piacentino
are you even just a little bit familiar with C# or Vb?
What you could do is listen to the SolutionComplete event and then start a new solution (I think I remember it was called like that) with due caution.
- Giulio
_____________________
giulio@mcneel.com
McNeel Europe, Barcelona
Nov 5, 2010