![]() This isn’t so much about translating geometry between programs but instead translating data between them. Lyrebird the plugin follows a similar logic as our previous interop tool, particularly that we create intelligent objects (families) in Revit so that when we use Grasshopper as a computational design tool, we structure the data in Grasshopper to make it easier to instantiate those Revit objects. If you haven’t seen this video you should take a couple of minutes and check out the Superb Lyrebird in action. The results of those discussions and their help is what we’re now calling Lyrebird after one of the great communicators of the animal world. ![]() We ended trading emails for a couple of months passing around different ideas about how we could improve the UX and element creation aspects and create a better overall plugin. Nothing much happened with it for a month or two until we were contacted by fellow Tech Studio alumnus and current Robert McNeel and Associates employee Dan Belcher.ĭan was kind enough to show it around McNeel’s offices and they gave us the opportunity to show it to them in person and start a discussion of how we could make it better. It was a great first pass, but we ran into some limitations with how it created elements and it really didn’t wind up getting used as much as I hoped. A few months ago we posted about an interoperability tool that we made to help us go between Grasshopper and a couple of other applications that we were working with in the office.
0 Comments
Leave a Reply. |