Let’s face it, we’re living in the future, right? We have self-driving cars (sort of), phones that can practically read our minds, and we’re sending…
Here’s what happened when I challenged an AI to model the complex structure of King’s Cross Station in Revit. No Dynamo, just raw C# as a Revit macro.
Ephany is a standardized framework for your asset data that you can own, extend, and build upon. Your organization can finally own your data and the source code to boot.
Capacity Planner is a conceptual design tool built for merchandising workflows. It seeks to help with site feasibility studies, macro planning, and everything in between. Starting with a building shell, users are able to generate a floor plan with department capacity and merchandise categories as the main focus.
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?
We have all been there. You receive a model from a consultant or a partner firm, and it is absolutely weighed down by hundreds of…
With the emergence of AI as a coding partner, I’ve found myself leaning back into the Revit Macro Manager. The barrier to entry for text-based coding has nearly vanished, and the results are cleaner, faster, and more robust than anything I could “wire up” in Dynamo.
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…
Over the years I’ve spun up a handful of blogs, each tied to its own project: Now that I’m focused on Triple Zero Labs full-time,…