Hummingbird

Information

Hummingbird is a set of Grasshopper components that facilitate the creation of Revit native geometry. This process utilizes a simplied pseudo-language in Excel to describe many properties of the Revit BIM geometry. Translating Rhino primative geometry to Revit has been vastly simplified without the need for linking or reference objects. This allows for the downstream Revit model to be modified and adapted for the project duration

Website: http://ghhummingbird.wordpress.com/
Location: San Francisco
Members: 98
Latest Activity: May 12

Discussion Forum

Hummingbird and Revit2013 in Windows 8

Hello all!Anyone tried to use WF ModelBuilder on Windows 8 + Revit 2013, and was successful at that?For all I researched, it seems like a dead end, due to .NET 4.0 which comes pre-installed with…Continue

Started by Daniel da Rocha Mar 25.

Hummingbird Update - New Level Component

New updates to the Hummingbird component set have been published. The update includes one new component:LevelThe Level component will generate Revit Levels based on the given height and name. The…Continue

Started by Tim Meador Dec 11, 2012.

Chicago Facades + Innovation 1 Reply

Hello Mario and Tim, I recently saw you guys mentioned in this workshop (see below.) 3. FACADE PATTERNING: Translation from Grasshopper into Revit This workshop will introduce a variety of patterning…Continue

Started by Matthew Owens. Last reply by Tim Meador Dec 4, 2012.

Hummingbird Update - Topo surfaces and Mass Families 1 Reply

New updates to the Hummingbird component set have been published. The update includes two new components:TopoSurfaceMassFamilyTopo surface will generate a Revit topo surface from a list of points in…Continue

Started by Tim Meador. Last reply by first1 Nov 29, 2012.

View All

Comment Wall

Comment

You need to be a member of Hummingbird to add comments!

Comment by Mario Guttman on July 27, 2012 at 3:54pm: Updated files "WfRevitModelBuilder" (Revit2012),
and "WhiteFeet.RevitModelBuilder (Revit 2013),
Adds option to offset placement.

Comment by CongChien on July 24, 2012 at 10:08am: Thanks Mario

Comment by Mario Guttman on July 24, 2012 at 9:42am: CongChien: Everything in Revit is represented internally in decimal feet. We do not make any conversions in the core Hummingbird tools. You need to make the conversions yourself, either in Grasshopper or in Excel.

Comment by CongChien on July 23, 2012 at 7:54pm: Hello all

I want to convert units from (1 mm) Rhino = (1 mm) Revit how to do?
Example: As shown, the (1 mm) Rhino = (609.6mm) Revit
Thanks very much for your help

Comment by Mario Guttman on July 22, 2012 at 4:42pm: Updated files "WfRevitModelBuilder" (Revit 2012), "WhiteFeet.RevitModelBuilder (Revit 2013), "WhiteFeet.RevitModelBuilderUtility" (Rhino-GH-Hummingbird) today. Various small fixes.

Comment by Mario Guttman on July 19, 2012 at 12:20pm: Just posted updated versions of "WfRevitModelBuilder.dll" (R2012) and "WhiteFeet.RevitModelBuilder.dll" (R2013). These enable modes to control the deletion of existing Revit elements when new ones are created.

Comment by Mario Guttman on July 19, 2012 at 10:43am: Definitely a bug on the RH-GH side. Let me work on it. thanks for the clear explanation. (I'm assuming this output worked in Revit; it just substituted a line for the arc; is that right?)

Comment by Jacob Gay on July 19, 2012 at 10:25am: Mario, I see what you're saying about circle objects and closed splines and how Revit cannot create those. However, i'm more interested in arcs which should be easier to deal with.

I can send along files later on today if its helpful, but what i'm describing you can see in this screenshot. If I create a similar shape (3 polyline segments and one arc) in the Revit environment and export it using ModelBuilder it makes 3 draw:line rows and one draw:arc. In Rhino/GH however, the Hummingbird floor component doesn't seem to be able to process the arc segment.

Comment by Mario Guttman on July 19, 2012 at 9:15am: Jacob. Not surprising about Excel. We might switch to a text file. One of the reasons for using Excel is that it is a good place to study how the program works by manually manipulating the data. For example, in the examples you mention, the circle and the closed curve, Revit can't represent these. You can explore this by trying to draw them in Revit. What you probably need to do is split the closed shapes into two curves, for example two arcs for the circle. In the case of the improper output can you send me a simple example that illustrates the points in Rhino-GH and the output and I'll do some debugging to see if there is somethign wrong with the component.

Comment by Jacob Gay on July 18, 2012 at 7:54pm: Hi guys, I tried to get this running at work earlier today and it seems it doesn't work with Excel 2007 (component threw this error). I'm now at home testing it out with a trial version of Excel 2010 and it seems to be working ok.

What doesn't seem to be working is the floor creation routine with anything besides polyline curves. I've tried it with a circular curve (circle) and a closed planar curve (polylines with an arc) with the same failing result in the 'out' of the floor component - "Unknown Rhino PolyCurve curve type: ArcCurve". I also tried it with a periodic planar curve (3point nurb curve) but the points going into excel look clearly incorrect. Am I doing something wrong?

Exciting stuff Tim & Mario, thanks for making it public.