Step by Step Guide – Creating My Iplex FWG Family in Revit

A lot of people ask me if I’ll give them my Iplex floor waste gully family. The answer

Titleblock Integers, Take 2 – Video Guide

A quick follow up to my previous post on titleblock integers with a little more in depth explanation for new users to Revit.

C4R – I’m Still Missing Too Many Elements! (Part 2)

So last week you went through how to fix the ‘too many missing elements’ error, but after clearing

Aligning 3D Section Boxes

A quick one that came up today.. “Ryan, how do I align a 3D section box with an

Lookup Tables and You – Part 2 – Improving Your Workflow

Now you understand how lookup tables are formatted and referenced from Revit families, let’s have a look at

Lookup Tables and You – Part 1 – Understanding Lookup Tables

Life isn’t just about Dynamo, so here is something a little different to mix things up. Earlier this year I spoke at BiLT ANZ 2017, I had the opportunity to present two separate talks of which one was lookup tables. It’s a bit of a dry topic, so stick with me. Lookup tables for pipe and

Tagging Invert Levels

Over the years, I’ve seen a lot of err.. solutions for tagging invert levels. From adding shared parameters to your pipe families through to using Dynamo and everything in between. Ignoring the fact that you can’t add parameters to system families like duct and pipework, there is a far simpler way to get what you’re

Importing DWGs to Revit While Still Displaying MTEXT Correctly

For those of you that still heavily rely on DWG based details and schematics that are bought into

Practical Dynamo – Moving Views Based on Another View

Okay, so we’re on a roll with practical Dynamo usage. Last week we looked at placing views centrally on our sheets, but what if you didn’t want the view centrally placed? What if you wanted views placed in the same location on all sheets maybe in the top left of the page? As always with

Update to MisterMEP Dynamo Package (0.1.4)

I’ve just published a small update to the MisterMEP Dynamo node package. A quick changelog: Fixed the problem