We now have bi-directional data exchange between Revit <–> Rhino.  A new version has been posted to the Food4Rhino site http://www.food4rhino.com/project/hummingbird?ufh that includes a component for reading .CSV files and using the data to build geometry in Rhino-Grasshopper.  This version also includes a lot of small fixes and additions so be sure to look at the new Users Guide.

There is also a new site, in addition to the FoodForRhino site, where you can download software as well as sample data and other kinds of resources:  http://www.whitefeet.com/Hummingbird/

And keep sending messages and posting stories about what you are doing.

Hummingbird3

Hummingbird2

Hummingbird5

A new version has been posted to the Food4Rhino site http://www.food4rhino.com (search for “hummingbird”) This version installs for both Revit 2014 and 2015 (even if you don’t have them on your computer.)

There are some useful documentation and sample files at http://www.whitefeet.com/Tools/ in the Hummingbird – Rhino to Revit Translation section. (You will need to create an account and agree to the license agreement but you can use Hummingbird without buying a WhiteFeet Tools license.)

This update exposed a number of issues that need to be fixed.  We are also working on a Revit –> Rhino upload option.  So stay tuned for another update.

And keep sending messages and posting stories about what you are doing.

Periodically I fix little things that users encounter.  For example, today I realized that the Revit ModelBuilder was not setting double parameter values correctly.  I fix these and repost the updates to the www.whitefeet.com/Tools/ site.  Sometimes it takes a while for them to get to the Food For Rhino site. There is an Excel file on the WhiteFeet site that lists the versions:Image

 

Since the process has changed somewhat this is a revision of my previous post.

Image

The Revit Model Builder add-in acts as a layer between the Revit modeling environment, including the Family Editor, and a .CSV text file. (The Revit environment can include Vasari; however, this has not been tested.)

The text file, which can be viewed in Excel for study if necessary, creates a bridge to other applications. There is no restriction on these other applications since the Model Builder is only aware of the text file. Most of the work to date has been done with data generated from either Rhino-Grasshopper or a special C# Model Builder Tool which is a Windows program that serves as a template for custom computational projects. Ports have been proposed for other applications such as Processing, AutoCAD, ArchiCAD, or other applications. If these other applications are used, they will need to customized to create the .CSV output based on their own geometry or other algorithm, and a .DLL library is provided to make this easier.

The primary workflow is for one of these applications to output an Excel worksheet that follows the conventions described in the next section. Then, from an open Revit session, the Model Builder tool reads the Excel data and creates new geometry in Revit.

A secondary workflow is to create geometry in Revit, and then use the Model Builder to export data to a text file. This is useful as a means of creating sample data, which can be edited and then imported to generate new geometry. It can also be used as a way of transferring geometry from Revit objects as drafting or model lines into the Family Editor or another view. In the future this output may be used to create geometry in the non-Revit applications.

Follow

Get every new post delivered to your Inbox.

Join 58 other followers