Hey guys,

This issue came up a couple of times in two separate offices this week and every time it did I had to scratch my head and re-figure it out, even though I think I kinda knew it from before. I hope this post is helpful to people with the same predicament but I also hope that I will finally engrave the solution deep into my brain by writing it into a blog post. Here we go.


Window displays wrong when cut in Plan view, adjusting View Range has no effect.

This can often occur with a full-height double-pane windows with an openable upper part, for example. The window might look like this when this happens.


The actual solution can be found in this Autodesk Troubleshooting page, but there are a few tricky moments when following the recipe given in the text. Here is what the suggested solution looks like according to Autodesk:

  1. Edit the family.
  2. Go to the Ref Level.
  3. In the View Properties edit the View Range.
  4. Set the desired value for the Cut Plane.
  5. Load the updated family into the project.
  6. Verify that the appearance of the family is updated.

The first part of the solution is to conceptually grasp the fact that you cannot do anything inside of the Project – everything is done inside the actual Family! This can be really confusing because, well just because View Ranges are really confusing to begin with. And so you might be thinking “Gosh, what did I screw up this time, I’m cutting in the correct level yet I am getting this weird window. I can see that all the parts of the window are there when I tab/select it but it simply doesn’t want to show! “£*”!%&&!” And you would be correct! You’ve done everything right within the Project, but you have to head to the Window Family in order to make this work.

We are now editing the family and getting to point #2 – Go to the Ref Level. The tricky bit here is figuring out what the hell is the Ref Level and how to go there – the Ref Level is the Family equivalent of the Project floor level and you select it like so:

and then you will be able to change the View Range:

Adjust the cutting plane so it goes through all the bits that need to be displayed.

And there you have it. Load the Family back into the Project and it should work fine. It is a bit controversial but I guess, like all things in Revit, someone must have had a reason to create this functionality.

Now go cut your Window like it was meant to be cut! Oh, and that works for Doors too. Cheers, folks! (I’m literarily having a Cider right now)

Greetings, folks!

Here is a quick solution to an inconvenience I was having when setting up some Window Legend sheets today. In this particular case I’ve decided to use the Phased Out Legends approach discussed many years ago in this blog post by Martijn de Riet. This is from 2012 but it’s still a valid approach in my opinion. We’ve enjoyed quite a few treats in the recent years, sadly Legends are still to get the attention they need.

The premise is that you setup your Window views as plain old Plan and Elevation views using one long long wall containing all your window types. In order to hide that in all your normal views, you place this rig inside the ‘Existing’ phase and you also demolish them in that same phase. Then you simply adjust your views to show said phases correctly. These dummy windows would remain hidden in all normal views including schedules. That’s the gist of it.

I bet there were a number of ways to automate the task of creating all the ‘mini views’ for each window type, but what I found myself doing is duplicating the same plan and elevation view as dependant views, adjusting the crop region as needed and placing them on the appropriate sheet. Tedious, tedious work.

Duplicate Views on Sheets

What came out of my frustration was a neat way to duplicate Views on Sheets. I can see how that can be quite handy in so many situations where you simply want to save some of the hustle of all the duplicating and dragging and dropping. So here you go, folks, a nice little Macro that you can use inside your Application Macros straight away (unless you need Administrative rights in which case you can go and kick your IT’s butt from me).

// Use inside the Application Macros
public void DuplicateViewPort()
	Document doc = this.ActiveUIDocument.Document;			
	Viewport viewportToDuplicate = ViewportToDuplicateFromSelection(this.ActiveUIDocument);
	View viewToDuplicate = ViewToDuplicate(doc, viewportToDuplicate);
	XYZ placementPoint = viewportToDuplicate.GetBoxOutline().MaximumPoint;
	using(Transaction t = new Transaction(doc, "dulicate viewport"))
		Viewport.Create(doc, viewportToDuplicate.SheetId, viewToDuplicate.Id, placementPoint);				
// Returns the Selected Viewport to Duplicate - promps for selection
internal Viewport ViewportToDuplicateFromSelection(UIDocument uidoc)
	var selectedViewPort = uidoc.Selection.PickObject(ObjectType.Element, "Pick Viewport");						
	var viewport = uidoc.Document.GetElement(selectedViewPort.ElementId) as Viewport;
	return viewport;
// Returns the duplicate View to be placed on the Sheet
internal View ViewToDuplicate(Document doc, Viewport viewport)
	using(Transaction t = new Transaction(doc, "duplicate view"))
		var view = doc.GetElement(viewport.ViewId) as View;				
		var duplicateView = doc.GetElement(view.Duplicate(ViewDuplicateOption.AsDependent)) 
                   as Autodesk.Revit.DB.View;
		return duplicateView;

Feel free to use it as you see fit. Ask away, if you have issues implementing it. Use the code to create Dynamo nodes of any sort or kind and generally knock yourselves out.

The wait is over and Warchart is available for download from Autodesk App Store – go right ahead and get your fresh copy of our new product and start cleaning those pesky Warnings, enjoying yourself every step of the way!

Ok, you might be thinking – wait, whatchart? Warwho? Alright, let’s take it one step at a time.

History of Revit Warnings

Warnings have always been a part of Revit’s grunt. Their existence is important in two ways.

First and probably most important, Revit is doing you a great service in telling you that something is wrong with your model. Understanding Revit Warnings, in Autodesk’s own words, is important and you would want to prioritize those areas in your project where you might be punished later down the road – for example, having “Duplicate Instances in the Same Place” might result in a misleading schedule – not ideal.

Hint: clear Warnings which lead to program implications first.

The second way in which accumulating Revit Warnings should be of interest to you is because it directly affects Model Performance. Yup, every character is a byte of information and it just adds up, slowing your model in the process. There is no hard limit as to how many Warnings is a definite no-no – I bet my BIM hat that everyone has their own opinion, my

Hint: let’s say Warning Number = N and File Size in MB = S. Then:

  • Wow: N = 0
  • Good: N < S
  • Alright: N < 2 x S
  • Poor: N < 4 x S

For example, if you have a model of 350mb, you can tap yourself on the shoulder at 350 Warnings, go ‘meh’ at 700 and feel bad about yourself at 1400. Each project is different and those values will vary.

Let’s see what Autodesk has to say:

“Ideally, all warnings should be addressed and the total number of unresolved warnings should be zero. But in reality, this is a tall order in most projects. So the pragmatic approach is to resolve as many of the warnings that you reasonably can.”

User Interface (UI)

Revit provides you with a simple but thorough UI to let you go through the different Warnings in your Model. While it has everything that’s needed to get the job done, I feel that the main problem the community has had with the default Warning Dialogue was the difficulty with which you navigate and isolate the affected elements.


After Autodesk Development Team released the Document.GetWarnings() method a number of community created alternatives came to live each attempting to give a better way of dealing with Warnings. In all fairness, the process started even before Revit 2018, but the extra step of having to export and parse an .html file made those solutions a bit .. uglier I guess is the word. GetWarnings() created a really elegant way of interacting with what was already inside Revit.

Enter Warchart

Warchart stands for Warning (Pie) Chart. The great thing about Warchart is that it builds on the fluidity of this new feature. It’s absolutely adorably interactive. It gives you an immediate feedback. That’s a really powerful feature and we can talk about gamification, dopamine release all we want but the fact of the matter is that it’s just super cool watching you eating through those Warnings like the proverbial Pacman (see what I did there?). A part of this, of course, is the Modeless WPF which allows you to keep Warchart open while you go about your business.

The other really potent feature is the ability to zero on those warnings which matter the most – because the interface is actually one big colorful pie-chart, you know the distribution of Warnings in your project immediately.

To give you a taste of what Warchart looks and feels like, here are a couple of screenshots from it.




Download Now!

With Warchart you can have your Pie and eat it too! Actually, I’m not entirely sure how applicable to Warchart this saying is, but we do have a tasty-looking image of a Pie so I couldn’t resist.

If you are burning with excitement like we do, head to the App Store and download Warchart! You’ll see how much more enjoyable your model management becomes with this intuitive and easy to use gem of a Plugin.

I hope you like our new release. If you have any questions about it or ideas on how to improve it, drop us a line – we’d love your feedback and we’d appreciate your time!


Here in Archilizer we are proud geeks! We love a bit of scripting, and a handsome spreadsheet – data speaks to us. Just give us a crisp set of algorithms on a Monday morning and we will break them and fix them by noon.

But we also remember our humble beginnings in design. We know that visualized data is worth a thousand words, so we always strive to optimize how we view those seductive masses of information we are constantly showered with. Say for instance, Warnings in Revit – nobody wants to deal with them – it is such a hassle to figure out where to start from and what is important and what is just Revit being a Diva. So we created a plugin to clean all that into a neat pie chart with built in functionality to help you get that thrilling satisfaction of reducing your Warnings!

The plugin analyses the types of warnings, presents them in a minimalist way, so you can select what you are most interested in, or what seems to be the widest spread issue and isolate it, so you can investigate and fix.

Warchart is going through final approvals by Autodesk and will be available on the Autodesk App Store soon – watch this space.

Here are some videos showing off our new little gem:




This blog has been verified by Rise: Rf7f0871f6cad38fd4a4c9ffd79aa4ae4

This is a short macro that I wrote today for a task that has always been bothering me. I spend equal amounts of time changing the first several text notes by hand, looking for an existing solution in the Revit Store as well as everywhere else (Google) and finally writing the small script up.

It is the smallest possible amount of code and you can surely make it prettier if it is your wish. You can have it up and running in no time by following these steps:

1.      Go to Manage tab ->Macro Manager -> Application

2.      Click on ‘Module’, give it a name

3.      Copy/Paste the code below right after ‘Revit Macros generated code’  (click after the last ‘, hit ‘Enter’, paste)

4.      Go to Build -> Build Solution (F8) and Ctrl+S to save it out.

5.      Close the Sharp Develop window

6.      Under the Macro Manager you should now see your new Macro named ‘Capitalize’ if you haven’t changed it

7.      Now ‘Run’ the Macro and select the Texts you want to change.

There you go. You now write Revit Macros. Congratulations!


public void Capitalize()

            UIDocument uidoc = ActiveUIDocument;
            Document doc = ActiveUIDocument.Document;
IList<Reference> selection = uidoc.Selection.PickObjects(ObjectType.Element, “Text to edit“);

if(selection.Count == 0)
TaskDialog.Show(“Error“, “No selected elements“);

using (Transaction t = new Transaction(doc, “Capitalise Text”))
foreach(Reference r in selection)
TextNote note = doc.GetElement(r.ElementId) as TextNote;

if(note != null)
note.Text = note.Text.ToUpper();

Update: Family Editor Interface was added to the Featured App category! 

On 30 May 2016, Archilizer’s first plugin got a place in the featured apps in the Revit Store. We are really happy with this fact and we hope that now the plugin will have the chance to reach and help even more people out there!


This is a special one for me because this is our first officially published Archilizer Plug-in! I am incredibly excited about the launch of this first digital toddler and I wish it all the luck and happy moments with its new users!

In this Plugin Review, I will go into detail of what the plugin does and where to download it from but first, let me give you a few words about the process of submitting a plugin to the Autodesk Plugin Store, as this might be interesting to the few of you who are thinking of sharing their programmatic work with the world. Having been through the process once, I would dare to say that it might be easier the next time around, however for a first timer, the venture sure was intimidating. In a sense, writing the plugin itself was the easier part, as following the admittedly many Autodesk sources was actually a challenge.

Your first action, after creating an account in the App Store website, is to go to the following link, read through the text and head to the bottom of the page, where you will see a little matrix with video tutorials. Watch those at least a few times. No go back and read the text again. Once you’ve gained enough courage, start the procedure of launching a new plugin and refer to the above resources as you need. Every single bit of the process can take a lot of resources. Personally, I would recommend outsourcing the logo design, because even for a seasoned graphics pseudo-designer as myself, I ended up producing a crappy logo with an even crappier resolution, for some yet unknown reason (this will be the first thing that I will be updating as well).

Challenging as it may be, don’t worry all that much. After putting everything down the way it is described, publish your work and you will have the pleasure to communicate with the IT Support team which will guide you through the rest of the process. It literally feels like a humanized bug removal tool. On every step of the way, they will report when they encounter a hurdle or an obstacle and make you fix it. From start to finish, the whole thing took about a month. I hope this gives you a feeling of what it’s like to publish a plugin to the Autodesk Store. Don’t hesitate to ask me any questions. Now let’s get back to this plugin and see why it is so adorable!

What it does.

Family Editor Interface takes only those parameters which manipulation is useful in creating an intuitive feedback on how your family is behaving and slaps them onto a simple applet that sits quietly in your work field. The simple sliders represent the values of those parameters. They give you a meaningful range of values to play with and test the mechanics of your door, window or furniture system. The plugin is conceptualized as an interactive tool that makes the process of family creation more enjoyable. The plugin is most certainly influenced by Grasshopper, Dynamo and the like and is one of those quality-of-life add-ins which you could do without but just makes your task more pleasant.

Who is it for.

Anyone who spends enough time in the Family Editor. In my practice, enough time is the time necessary for you to create a responsive, well-parametrized family which does not break in contact with regular users. A complex family has a lot of interconnected relationships between its parameters and even for its creator it is sometimes hard to intuit the internal logic of the structure. That’s when this simple interface comes really handy, as it allows you to quickly test the functionality of all your ‘important’ parameters, or in other words, the parameters which drive the family. However, once used to this extra panel, it becomes a second nature to just check your parameters and I tend to use it even for small components with just a Width and a Height parameter.

Is it free?

It is absolutely free and if there is enough interest from the community, I will open the source on GitHub, so folks can play with it and take it in the direction they want. Meanwhile, I will be taking on board any comments and suggestion in order to make the tool as user-friendly and useful as possible.

How to use:

You can find a few short video tutorials on how this plugin is used on the publisher’s website. I would like to think that the tool is quite easy to understand and use, but if you have any suggestions, please write me in the comments section below or by contacting us.

Tips and Tricks:

Use the ‘Refresh Document’ button to quickly ‘reset’ the defaults of your parameters and incrementally reach a higher/lower value.

Try it now! Test it for free! 

You can find the Family Editor Interface in the Revit section of the official Revit Plugins Store here:

When managing projects of non-small sizes, one of the tedious routines that you are required to go through is to somehow match information that is part of the project’s Sheet set and its View set. The idea of cross-referencing data between various elements is native for information management, yet Revit does not yet cover that aspect for us. Dynamo, however, does (so, in a sense, Revit does. Duh).

Traditionally, we could approach that task as follows:


  • load all sheets
  • load all views
  • for each sheet and view, see which view the sheet is sat on and finally
  • check if the corresponding parameters match and if not
  • do something (make them equal)


Now, there is one little bug that has been migrating with every update of Dynamo, and the brand new 1.0.0 (Congratulations!) version still apparently still got it – when retrieving elements by Category, the View Category will spit a message which states that Template Views are not Views. That’s fine. There is an even nicer node that simplifies the task for us:


What this node is supposed to do is to only select those Views that are place on the set of Sheets it is given. Now we can skip a step, retrieve only the Views that matter, and continue with our cross-referencing. .. but this node ,too, does not work.

That’s also fine. Here is the solution to the problem, written in python code.

.. and here is what the definition looks like:

What we did here is that we collected all the sheets in the project, using the Dynamo node of retrieving All Elements by Category, then we fed the resulting list together with a couple of shared parameters, which both the Sheet and the Views of the project use, and we executed the python code which, on one hand matched the information of those shared parameters, and on the other, gave us a handy list of ‘failed’ views. Those ‘failed’ views are simply the views that had View Templates assigned on, controlling and thus ‘locking’ the shared parameters.

While we are on the subject of python and getting instance parameters from elements, I want to point out the correct (at least for now) way of doing it.

The general syntax of this command in Python is:

element.Parameter[“Parameter Name”].AsString() – to get (can also be .AsInteger(), .AsDouble()) the parameter, or

element.Parameter[“Parameter Name”].Set – to set the parameter.

This is important to know as a lot of times Dynamo tasks revolve around Parameter manipulation and there is hardly any information out there that explains how this can be achieved in Dynamo with Python.

I hope that custom Dynamo definition can be of help to you in your BIM journeys my friends! Good night and best of luck.

Site Designer for Revit 2015/2016 R2 has been out for a while now. For those of you who may have had the chance to register its emergence and got quite excited by the beautiful video demonstrations out there (like I was) but haven’t had the time or reason to give it a try themselves, here is what you might need to know.

Site Designer is officially released plug-in, which in a way means that Autodesk supports its existence to the point of entrusting the content of this package to be part of Revit’s core installation, or at least the R2 version of Revit 2015/2016 available from the subscription center (‘Download is Exclusive to Autodesk Subscription Customers’). Once installed, the plugin comes with its own tab in the ribbon and at first glance, the amount of icons that pop out is quite impressive.

Linear workflow – this is the first thing that you notice when working with the SD is the linear workflow it follows. This is quite common for any programmatic tool and after the initial and inevitable frustration that follows every time you pick up a new piece of software, you start to get it. Following the logic of the tool equals using the icons from left to right. First, you either have to import an existing Toposurface or create one using the traditional Site tools (Massing & Site). Second, you set a surface as a base, third you start creating your elements and fourth, you simply modify them. There might have been a fifth step in which you document your work, but I did not get that far.

The problems with this type of flow come when you are already waist deep into changing and fiddling with your terrain and you realize that something major needs to be updated. There simply isn’t a way to revert to an earlier stage of your work and in this respect the workflow is quite destructive. This becomes a massive problem when you take into account the ..

Incredibly slow performance. Chances are that you are going to want to use SD on a real project where a few hectares of landmass need to be worked on. The bad news is that any sort of transformation causes SD to create a huge number of points. This leads to operations that take anywhere from a few minutes to an hour to complete. This is simply not feasible in terms of the standards of software responsiveness that we have adopted nowadays. Coupled with the frequent crashes and the destructive workflow mentioned earlier, working with SD on any sort of deadline quickly becomes an exercise of hair-pulling.

Soft terrain – really nice concept. This allows you to modify a plot of land the way you always wanted, raising it as a whole and with a certain grading to the boundaries. It takes while to complete, but I did enjoy the result when one was produced. A nifty trick that I found was that I can ‘reset’ my topography by modifying it. I doubt that was the intended workflow.

Featured line – it didn’t work.

Point Wipeout – should come really handy when you start fine-tuning your design. I couldn’t get that far.

Streets – now, this is an amazing concept, because, in theory, this should allow you to create a street network with such an ease that your CGI team will love you and buy you beer and cookies. In practice, this feature is useless as it limits you to a fairly primitive set of geometric shapes and connections, so unless your project is a small house with a single front to the highway, you wouldn’t find a good use for it.

This is the point where I started to give up. I did try curbs and retaining walls, which caused the already strained model to crash. The concepts themselves are amazing and I would have loved to implement it on a real project, but I simply couldn’t find a way to submit something that would not allow my client to alter or even use the model for any meaningful purpose. After I’ve spent a few days of hard work trying to tame this beast, I had to revert to the traditional Modelling Site tools in the ‘Massing & Site’ tab.

To me, Site Designer, at least at this stage of development, is similar to what a Barbie Kitchen Set is to a professional chef. Sure, there are hobs and ovens and mittens and plates, but you might reconsider using that particular kit for your 3 star Michelin dinner.

I think that the officiality of this release might have been a little premature, but I hope that the feedback from the community will get this project faster to the point where we can finally have something to do our landscape with. I stay positive that Autodesk would not leave something as half-baked as the current Site Designer sit for too long without taking a step to either fully integrate it within the software or leave it altogether, finding an alternative that will satisfy the needs of Landscape Architects, Civil Engineers and Architects that use Revit as their BIM platform of choice.

After a short delay, a BIM Consultancy gig in Doha and a trip in the desert (thank you Velina for organizing this amazing event and thank you once more for bringing us home in one piece), I have decided to do a short review of a really neat and useful Revit Plug-in, called ‘View Duplicator’ that I recently came across.

Without further ado, I give you the ‘View Duplicator’. View Duplicator is a great small Revit plugin that solves one of the many user experience issues that vanilla Revit has – namely, it gives you the ability to duplicate series of views in one go, or in other words, it is a ‘batch duplicating tool’. If you are anything like me, you would expect certain functionalities to come out-of-the-box with your software product of choice and indeed, I have always imagined that right-clicking on a selected number of views will allow me to duplicate said views with, perhaps, attaching a (1) prefix to preserve the imperative of name uniqueness.

In Revit 2016 this is still not the case, and so the nice people from Theptech (the P Tech?) have created an add-in that allows you to overcome this minor obstacle. And since a picture is worth a thousand words, I have prepared a series of GIF images to demonstrate how the tool works.

As with every other external plug-in, you need to first download it and install it, before you can take advantage of its immense power.

Head to https://apps.autodesk.com/ and look for ‘View Duplicator’. Download and install the plugin. This is best done with your Revit turned off, although it will probably work even if you have it working at the time of the installation. You can always uninstall the tool by double clicking on the same installer file.

Now, with that out of the way, start your copy of Revit. Revit add-ins normally occupy the Add-Ins tab on the ribbon, so on opening the tab you should be greeted by the stylish purple twin sheets of the View Duplicator icon.

The interface of the tool is quite simple – 4 panels will guide you through the whole process. The first one gives you the ability to select the views that need duplicating. A nice touch is the fact that the views are organized by types, which adds to the clarity of the exercise.

You can then choose to assign a view template, which is indeed quite handy. Finally, you can customize the naming of the newly created views in two ways – by giving a prefix or a suffix to the View Name and also to the Title on Sheet.

Yet another pleasant surprise was the fact that the author contacted us personally when we made the suggestion to incorporate a ‘Duplicate with Detailing’ toggle to allow that extra bit of control. There is obviously a round of changes coming which will hopefully incorporate that little wish of ours.

All in all, View Duplicates is a simple, yet powerful plugin that overcomes a user experience flaw. As with many other automation tools, its usefulness is fully realized when a large number of elements are affected, but from what we’ve seen so far, ‘View Duplicator’ has the potential to save you from the ‘Death by Many Right Clicks’.

Thank you for stopping by and as always, we hope it was useful.

Revit is an amazing CAD program. (And so is ArchiCAD, all right. I just happen to know and use Revit). Despite the fact that it has been around for quite some time and given the monstrosity of Autodesk as a company (therefore allowing it to push its products like no other), I feel that it has taken more than it should have to get Revit to the prestigious spot that it is now occupying. Of course, Building Information Modelling wasn’t as important as it is now, but I think that one of the reasons that made it difficult for Revit to shine (and allowed AutoCAD to still be lurking around) was the lack of sex-appeal, and I am referring to the quality of the draftsmanship it allowed us to produce out of the box.

For the majority of the architects, or at least, the ones that I know and have worked with, design expression is of extraordinary importance. So much so, that Illustrator/Corel have always been an inseparable part of all our submissions. The ability to control every bit of detail in one’s drawings is of such importance that, again, lots of people prefer to work in a 2D package than to take the world of benefits that comes with using Revit.

One instance where Revit has failed to deliver user control, where it is needed, is in the assignment of line weights for wall hatch patterns. I remember a project where we finally decided to overlay all of the walls with filled regions in order to achieve the desired look (it wasn’t my idea, but I played along).

Cutting to the chase, let me explain about the technical side of the problem. There are several system families that use fill patterns, for either their section or projection representation. The type of those patterns comes from the material of said element. So far we were able to override the color of the pattern (and indeed one of the “viable” workarounds has been to assign a grey color (to the pattern) in an attempt to give it a lighter touch). But we weren’t able to assign a different line weight to those patterns.

In theory, Revit allows you to change the default values for “all” object styles from the object style interface. For some reason, however, those hatch patterns are not among the categories that users have control over.

Here is an old thread in which the discussion revolves around another workaround in which pen 1, which is the default number for the patterns (trial-and-error) is set to the lowest possible value. And since pen 1 is the default for a lot more objects, we were supposed to beef up all the remaining values with +1. However, one immediate problem might be that, as with the hatch patterns themselves, there probably are more categories which line weight assignment has not been exposed. Furthermore, it’s one of that task that feels time-consuming in a debilitating kind of way. This is another approach, but it still doesn’t feel right to me.

The good news is that nowadays we have Dynamo! While setting up a company templates the other day, I remembered how pressured I felt trying to fix the same issue on a deadline before, so I decided to give it another go. I started by theorizing that I can programmatically increment all the line weights as described in the existing workaround. While I actually managed to achieve this, I was really surprised to find that now my hatch patterns were controlled by pen #2. It took a little bit of back and forth until I finally narrowed it down to just a few Categories that controlled those pesky infills. I was able to take control over 4 family categories – walls, floors, ceilings, and roofs. Each of those, in turn, had a surface pattern and a cut pattern property that I was able to override.

You can see this short video demonstrating the functionality of the definition. There is still more investigation that I need to do because I still have no idea how to override the values for the non-system families’ pattern infills.

Having said that, this definition can be useful to a lot of people out there just the way it is right now. You can download the Dynamo definition here. You would need to have Dynamo 0.90 installed, but that shouldn’t be a problem as it comes pre-installed with Revit 2015. If you have any questions, please feel free to contact me.