In development pyRevit extension written; first run against a real Revit install is still ahead.
Role
The redline round-trip: Revit families and detail assemblies into MarkupClaw, edits back to Revit.
Revit family → vector symbol → markup → Revit
The redline round-trip: Revit families and detail assemblies into MarkupClaw, edits back to Revit.
Revit family → vector symbol → markup → Revit
How it connects to MarkupClaw
- Export Detail Assembly from the DetailClaw tab in Revit, then Tools › Families › Import assemblies in MarkupClaw.
- Family provenance rides on every placed markup, so the edit knows where it came from.
What we are working on
- Bring-up on Revit 2019+ (not LT) with pyRevit 4.8+. Work on copies: older libraries upgrade permanently on open.
- The reverse trip — pushing edited details back into the family.
What it is not
Not an IFC synthesiser. Not a C# add-in; it is a pyRevit extension.
Not an IFC synthesiser. Not a C# add-in; it is a pyRevit extension.