Override #Revit Interior Elevation’s Crop with #DynamoBIM

This is an update to an existing workflow previously discussed here, http://sixtysecondrevit.blogspot.com/2015/11/framing-interior-elevations-in-revit.html

Basically, it is faster and more stable!

This node takes an input search string of elevation types (interior), a line weight for all views and a Boolean to run.

Part of the reason I haven’t updated this in a while is because the workflow was a beast! Initially the node was looking for the elevation marker in every view, seeing if it exists, replacing it and finally committing the override. Now it just finds the crop region as it relates to the interior elevation (investigate the node to see what I finally realized, I won’t reveal it here).

So far I have tested this on a healthcare project that had over 350 interior elevations! It did take a moment to run, but it completed the change!

Please keep in mind that this completes this process for all interior elevations in the model. I f there is an interest, I will make a specific one that allows the user to choose sheets.

Have fun!

johnP

Rename #Revit Views with #DynamoBIM Player

Since Dynamo player launched a few weeks ago, I have been having a lot of fun with it! Mostly because Python nodes support User interface additions!
Recently, a colleague needed to rename elevations based on level and room location. Very quickly I realized this needed to be done by isolated the elevation heads (views).
That’s when I went ahead and created this little gem (now available in Rhythm).

This node allows the user to pick a category to isolate, and select objects of that category by a crossing window or individually.
And here it is in action with Dynamo Player.

Have Fun!
-johnP

Open #Revit files in the background with #DynamoBIM

I have been working on some pretty cool nodes in the background, that deal with opening Revit files in the background.

Document.BackgroundOpen is now in Rhythm. This node is really special, because it enables all sorts of cool operability with Revit files that are not currently open otherwise. Pretty much any input that takes a document can use this node.

Here it is in action, opening a project in background.

Why is this exciting? Well first of all this method can be used to Bulk Upgrade Revit files.

This process + another new node can also be used to copy elements from another project. Like wall types!

Enter, All Elements of Type in Document and the Element.CopyFromDocument Nodes

And here is that process in action

Have fun!

johnP

Get Joined Elements in #Revit with #DynamoBIM

If you didn’t know already, I really like twitter for being in touch with the Revit and DYnamo community. Every now and then a great idea is generated and it offers a great opporunity to explore a solution.

Recently this one came up on twitter.

After some investigation of the Revit API, I found this little gem.

Which lead to this workflow

Which lead to this reaction!

The new node allows user to get joined elements to the input element to allow for all sorts of fun stuff. In Aaron’s case, it wsa so his door’s code compliance can be automated.

Have fun!

-johnp

Get #Revit Beam System Members with #DynamoBIM

A question came up at my firm recently regarding how to quantify the amount of beams a beam system contains in Revit. Currently, this is not easily accessible through the UI, but luckily there is an API method for obtaining the members of the system.

This is where Dynamo and python come into play.

This node is now in Rhythm, enjoy!

-johnP

#Revit Space and Room Tag Host with #DynamoBIM

Recently I was talking with Marcello on the Simply Complex Podcast about the lack of annotation nodes in Dynamo. After a question also came up on the Dynamo forums, I decided to add these two useful nodes to Rhythm.

This enables us to do some fun stuff based on the tag elements now! And yes, these are made with Python!

-john

Rhythm - Update to 3D Room Tag Node

It was recently discovered that the 3D Room Tag node had a few bugs in it. This was after some internal testing and some comments on the following forum discussion.
http://dynamobim.org/forums/topic/a-family-with-3d-text-to-acquire-room-information/
I am happy to say that this has been fixed and is now much more stable. The primary difference is the node now places the 3D Room Tag where the room’s origin is. (Similar to tag all)




You can of course find this on Dynamo’s package manger, under the latest Rhythm update

Rhythm Cleanup and Updates for Override Nodes

Rhythm has been updated to include some cleanup of the following nodes. I have renamed them to better reflect the Dynamo naming standards. This means if you previously used these nodes they are found under a different name now.

I have also bundled in a few more nodes that I will discuss in greater detail later. But for now I need to get my RTCNA abstracts submitted!

-John

Revit- Renaming Views with Special Characters

Recently a coworker of mine discovered a weird glitch with Revit. It pertained to view naming.

If you have ever tried to rename a view with the following characters, \:{}[]|;<>? or any non printable characters. Your promptly receive this error.

He discovered that this restriction does not exist when creating a new drafting view, but has a major issue when involving the <>

I illustrate the issue below. (Just so you all know, I have sent the error previously as well.)

Revit- Keep Linework on Duplicate View

I'm not sure if this method has already been shown, but I thought it could be useful to share.

Recently we had a project where we had two different packages to be submitted. In these two packages appeared the same building elevations. Easy fix right? Duplicate the views and name with a package designation.

Here's the problem:
Our user went through the painstaking process of using the line work tool all over the elevation to add depth. These elevations looked really good and we wanted to reuse that same work for the next package while maintaining the original view.

After some trial and error we found that duplicate and duplicate with detailing won't work. The magic is in the duplicate as dependent option!

See the video below for a very simple example of this process. I illustrate how the first two options did not work then show how to "orphan" the dependent to save the linework.

-johnp