Tuesday, 11 September 2018

Levels and Grids

Recently I received an email from Autodesk with Revit tips. One tip caught my eye right away: Turn all Level and Grids off in linked models in your entire project
Although the tip is fine and well explained I must say I do not favour this methode. For many years I tell, and many others, to Revit users, not to use Worksets for visibility purposes.

If you want to turn of Levels in a linked file you can do this with a filter. If the models are properly setup than you can use these parameters to filter upon.
Building Story and Structural are good parameters to use.
So basically you will turn of levels based upon parameter values:
Grids do not have this option, Grids only have few parameters. I tested what happen if would assign levels and grids to a scope box in the host model.  I could only get it to work if the filter setup was: See image below.
If I was filtering for a specif Scopebox name only found in the host model it would not work.(bug???)
What does work but is less elegant:
If you change the name of your levels and grids slightly you can filter on that. (In the example below I added DGi to the name of the levels and grids)
So the filter option might be a bit more tricky to get it to work for you but it when done right you only have to set it once. You don't have to traverse 20 linked files.... 
Put the filter in a view template and you are flying!

Friday, 7 September 2018


Over the summer I have been developing Dynamo scripts based upon the CivilConnection package developed by Paolo Serra from Autodesk. We are helping a customer creating and updating views for a tunnel project. 

  • The alignment is not yet fixed in position. 
  • The tunnel segments need to be modelled in Revit. 
  • The sections and floor plans have to follow the alignment. 
The CivilConnection package allows us to directly read the information from the Civil 3D file and work with that information in Revit. (We read the corridor information and use the baseline.)

In the movie below I test the scripts on a different dataset and it works. When the alignment changes, the views update and all the annotations remain. Below a screengrab movie of the script on a different dataset.

The OTB nodes won't allow us to read the Civil 3D information and the OTB nodes tend to recreate the sections and so loose all the annotations. 

Wednesday, 22 August 2018

Dynamo Scripts

If you develop scripts like me then after a while al lot of nodes are showing their results. (Dynamo < 2.0)
(Image from dynamoprimer)
When it's time to tidy up you might want to close them all and that could become a tedious job when you have a lot of nodes. Since you are automating. Open you script in a text editor like Notepad++ and do a find and replace on: isPinned="true" and change it to isPinned="false" 
For Dynamo 2.0 and higher it seems all you have to do is change this to first open to close:

Next tip: Packages (Dynamo < 2.0)
If you are missing a package and you do not know which one. Do a search on Function=
Quite often you will be able to see which package it is in the text close to function. 
For Dynamo 2.0 and higher Find: ConcreteType
Look for stuff that is not DynamoCore

Tuesday, 27 February 2018



Most of the time I like to write about something that I got to work. This time it's slightly different. So far I don't get this thing to work. I am looking into this node called move by vector. It allows for moving elements in Revit by a vector. The vector can be created using two points. I wanted to experiment with this node after a tweet from Luke Johnson about shared coordinates. we need to change Shared Coordinates.

the reason for wanting to move all these elements is to see if I could fix a file whose shared coordinates have been set up incorrectly. Why do I want to fix a file when there are OTB functionalities for  making things appear they are in the right location? Well, I just want to know what is possible.

I wanted to test to see if I could move all the elements in a file to a new location. A small test on furniture worked just fine. But that are simple point families. I got walls to move as well which is nice as these are line based families. But then the real test came let's try ducts....
So far the only thing I got is a complete mess. I tried to move all the elements that are connected to ducts. The flex ducts do not seem to want to behave. The ducts them self also seem to take directions into their own hand. See below.

The duct fittings don't want to go either. I suspect that it has to do in the order that things get moved. Now I am moving stuff per category. Let's try to move elements per system. Or maybe I am simply expecting to much of this node and is the translation of elements rather complicated.

the script so far that does not want to work.

Let's try one system at the time. The system I want to move is coloured red. To ease selection I use the select model elements node to select all the elements from the same system.

After the translation, and 23 errors I got this. It's seems to me to me that this Element.MoveByVector moves one element at the time and in between tries to maintain all kind of constraints which it obviously can't do.
So far no luck. I'll have a chat with some colleagues first and see if it is possible.

Friday, 5 January 2018

Spiral Staircase

A little while ago, during a Dynamo training, I showed how you could create a basic spiral stair. Later I decide to play a little bit more with it to see what is possible. I like to share some of the results.

Notice that the staircase is widening towards the top. I haven't bother checking whether the stairs comply to any stair rules. I just felt like playing with the sliders.

There are still a few things that need to be fixed. But it has been good fun to tinker with staircase.

Now I just need someone to print this in 3D

Friday, 29 December 2017

Dynamo geometry turn of preview

Small tip: Have you been creating a lot of nodes and you find yourself having to turn of previews? Don't! Try this:

Open your DYN file in notepad++ and do the following replace:

isVisible="true" to isVisible="false"

save your dyn file under a new name. Just to be sure you didn't break anything.

open it again and all nodes should be have their preview being turned of.

Thursday, 2 November 2017

Dynamo group colours

When you create a group in Dynamo you have only a few colours to choose from. It would be nice to have a few more or make them a little bit more distinctive. The interface won't let you but it is possible to do.
Dynamo dyn files can be opened with a text editor. There all kind of interesting things you can modify but let's focus on the colours:
The group called FUNCTION can be found. (in my dyn file) by the header: Dynamo.Graph.Annotations.AnnotationModel

but more practically look for the text you filled in! At the end of the line you should see: backgrouund (yes with nice typo)

it's all about backgrouund="#FFFF0000"

FFFF0000 = are hex codes for colours. The formatting is: ARGB (#AARRGGBB) meaning the first two define the transparency and the other 6 are the colour.

Hex Opacity Values
  • 100%=FF = Fully Opaque
  • 95%=F2
  • 90%=E6
  • 85%=D9
  • 80%=CC
  • 75%=BF
  • 70%=B3
  • 65%=A6
  • 60%=99
  • 55%=8C
  • 50%=80
  • 45%=73
  • 40%=66
  • 35%=59
  • 30%=4D
  • 25%=40
  • 20%=33
  • 15%=26
  • 10%=1A
  • 5%=0D
  • 0%=00 = Fully Transparant

For picking a colour I found this website to be nice: rgb-to-hex
copy the Hex code and put it in.
so 50%red =  #80FF0000

Be aware even if you put these colours in manually you can't select them from the UI. If you want specific groups to use this colour you are going to have to copy the group and add or remove nodes to it.

Google+ Badge