Friday, October 21, 2011

Node Based Control for Functions + Revit = ~gasp~

Is this what I think it is?
dynamo + arduino

A node based workflow for Revit? What do you say now, lovers of grasshopper? =)

Yes I know it's not fully there, but still...

Thursday, October 20, 2011

Formation of Alliances...

Something is underfoot - Frank Ghery just released 2 press releases this week announcing strategic partnerships and alliances. On the 18th, Ghery announced: "Architectural Leaders Join Frank Gehry to Form Strategic Alliance  Dedicated to Transforming the Building Industry Through Technology". The names on that list are quite impressive! Then, on the 19th a second press release announced: "Autodesk and Gehry Technologies to work Together to Improve the Way Buildings are Designed and Constructed".

Hmm... World leading architects + world leading design software company =______________

I'll let you fill in the blank, but I have to hope this leads to some really cool things happening in the near future. This is a pretty big development considering Ghery technologies uses their proprietary Digital Project so prominently. Since Digital Project is built on the same platform as Solidworks from Dassault Systems, one can't help but speculate what is going on. Ghery is dabbling in two technology pools now...

Tuesday, October 11, 2011

Elevation tags in Revit not updating...

On Monday this week I spent about 4 hours cursing at elevation tags in Revit. Last I recalled, an elevation tag in Revit is supposed to update to reflect the detail and sheet info once placed on a sheet, no matter what. Well, not this time. I could change the detail number in properties for the elevation and it would show on the sheet and in properties as having updated, but the marker itself would not update. Steve Stafford posted a great video showing this. Steve S. found that changing the elevation type would cause the marker to update and display correctly.

I also found that the marker would resume displaying updates to the detail number on a consistent basis provided it cut building geometry. If the extents of the marker view depth did not cross any geometry, it would not update the detail number if updated. So, another temporary solution would be to ensure the depth of the elevation view touches or cuts through building geometry. However, I haven't had a chance for successful testing to ensure this is the case. Like Steve S., I too am on WU2, so I'm curious if others are experiencing this under WU1 or if on WU2, if you can verify that cutting geometry ensures the tags update correctly.