Grasshopper

algorithmic modeling for Rhino

I am trying bake a series of incrementally manipulated geometries (controlled by a single slider) that I need to reference as a whole in a later part of the script. Basically, i'm looking for something similar to the "animate" function in a slider, but instead of outputting images, it outputs baked geometry into the existing file.

 

A possible solution would be to, create redundant algorithms, with different inputs that represent the all the points along the slider I want, but that is untidy, and heavy computationally for my lengthy script.

 

There might be something in Finches: Local Code (never used, just read up on) or geometry cache that some one more clever than I could figure out. Is there anything that I'm just overlooking?

Views: 1789

Replies to This Discussion

Hi Will,

 

you could use a Data Recorder to remember all shapes from a certain 'slider run', then either drag the slider yourself or use a Slider animation. You can bake all stuff inside the recorder afterwards.

 

--

David Rutten

david@mcneel.com

Leusden, Holland

So david, could you recommend something in the situation that I'm recording move vectors, and want to keep it long term in the script? The issue is that I'm collecting a list of move vectors that I would like to reference continually (like the geometry cache component) in subsequent uses of the file. The record data component is emptied once I close and re-open the file. 

 

Thanks

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service