What if Revit families were backwards compatible? Could we use AI and a little C# coding to force Revit 2024 to talk to Revit 2022?
Most organizations treat naming conventions as a manual chore, which is why their catalogs eventually become a mess of “2-Sided” vs “Two-Sided” inconsistencies. I decided to stop fighting that battle by hand and used AI to build a logic-based “wrangler” script, then used the Ephany API to push those standards across our entire catalog in seconds.
This post contains a collection of code snippets and examples that demonstrate how to use the Ephany Framework API. As the project evolves, I’ll continue…
When attempting to open an IFC model in Revit, I received the following warning which caused the model to not open properly. I noticed the…
When working with BIM data using the Revit API, one common step is retrieving parameter values from elements. Whether your goal is to extract or…
How to build clean, professional dialogs inside Revit add-ins If you’ve ever built a Revit add-in, you know the quickest way to talk to your…
Start with a clean vector file. Ensure you have a file that is in a vector format such as AI, PDF, EPS, or other that…
Last week, I received the most vague licensing error in Revit 2019. I was presented with the error message above which states nothing more than…