A blog dedicated to tidbits of software information related to the AEC industry. Most tips and tricks are roughly 60 seconds because, "Hey who doesn't have 60 seconds".
*The views and opinions expressed in this blog do not reflect those of my employer.
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
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.
