DrH 1.0.0 dynamic tool library for Autodesk hosts
DrH is not a fixed pack of add-ins. It is a live library: tools are published, your panel picks them up on the next update, and every Autodesk year from 2021 to 2027 is matched to the right runtime for you. When something is missing, Pro users ask for it and it gets built.
Windows installer, 60 MB. The manager is free forever. Pro is $100 per user per year; Max is $375 a year for a 5-user pack.
Illustration of the DrH workflow
01 hosts
Each host keeps its own conventions. DrH sits inside all three with the same panel, the same import flow and the same naming, so a tool behaves the same way wherever it runs.
One ribbon entry for both LISP routines and .NET tools, instead of two separate loading habits.
For production drafting, utility automation and corridor work.
Import a package and DrH reads the .addin file beside it to work out which commands to expose.
.addin sidecar detectionFor BIM utilities that would otherwise need a manual add-in drop.
Keeps custom review and coordination plugins reachable from a dedicated panel in Navisworks Manage.
For clash, review and coordination tools kept in-house.
02 features
The library is wider than this, but these four are the ones people licence DrH for. Each removes a step that normally means redrawing something by hand, or exporting through a third package just to get a file another consultant can open.
DROPMH
Where an incoming pipe lands too high above the outgoing invert, this builds the backdrop properly — vertical leg, bend and connection back into the chamber — as real network geometry that still schedules and still reads in profile.
high inlet → scheduled backdrop structure
DRYNET
Builds a full dry utility run as a pressure network straight from an alignment — ducts, bends and fittings placed along the corridor with cover respected. The run stays tied to the alignment, so a late route change redraws itself instead of costing you an afternoon.
alignment → pressure network, still dynamic
C3D2RVT
Rebuilds Civil 3D gravity and pressure networks as native Revit pipework you can tag, schedule and clash — not a mesh in a linked file. Invert levels carry across, and sizes map to your own Revit pipe types.
gravity + pressure → native Revit pipes
NWC2DXF
Navisworks has no DXF export of its own. This writes the model, a selection or a search set out as DXF — 3D geometry, or flat 2D linework from any section plane or saved viewpoint — with layers taken from the selection tree.
federated model → 2D or 3D DXF
DrH exists to shorten the distance between writing a tool, handing it out and using it — with enough diagnostics that a failure is traceable rather than mysterious.
Add a package straight from a folder on the workstation into the managed DrH structure.
browse → validate → registerPull from the shared library, with separate feeds for LISP routines and DLL packages.
library / lisp library / dllPackages are filtered by the Autodesk host version and the runtime channel it expects.
2021–2024 FW 4.8 2025+ .NET 8A matching PNG becomes the tool icon and a Revit .addin supplies the commands. No extra wiring.
Updating the manager leaves your installed tools where they are, so an update is not a redeployment.
update ≠ resetImport, load, update and run activity is written to a log on the desktop you can actually open.
why did this tool not load?The same DrH presence in all three hosts, so a tool is found in the same place every time.
consistent across hostsSmall icons, short menus and a list that refreshes the moment something is added or removed.
instant list refresh03 library
Most add-in packs ship a fixed set of commands and then age. DrH works the other way round: tools are published into a shared library, and your panel picks up whatever is new the next time you press Update. Nothing to reinstall, no IT ticket, no waiting for the next release cycle.
Civil 3D, Revit and Navisworks tools sit in the same catalogue, tagged by the host and the years they are published for.
filter by host · type · yearPress Update in the panel and anything published since your last check is there, already matched to your host year.
publish → update → runPro users describe a task they repeat by hand. If it fits, it gets built and published — for you and for everyone else on the plan.
request → build → libraryA new host year does not strand your tools. Library packages are republished against it as part of the licence, not as a paid upgrade.
2021 → 2027, one panel04 workflow
Pick a tool from local storage or from the online DrH library.
DrH checks the host type, the supporting files and the runtime path.
Launch the command from the DrH panel, inside the Autodesk product.
Update, remove or replace a tool without touching the rest.
— the case for it
the usual arrangement
after install
.addin go through one import flow05 plans
The manager costs nothing and always will — import your own packages, load them into any host year, read the log. A paid licence is what opens the maintained library and lets you put requests into it: Pro for one engineer, Max for a firm.
Run the tools you already have, properly.
.addin packagesEverything in Free, plus a library that keeps growing.
Everything in Pro, run centrally, for firms. A fixed pack of 5 users, $75 per user per year.
Exactly 5 users. Invoiced yearly.
06 install
Run the installer on a workstation that already has the Autodesk products installed. DrH attaches to the hosts it finds.
Civil 3D DrH panel on the ribbon Revit DrH panel on the ribbon Navisworks DrH panel in Manage log file DrH log on the desktop
Download DrH_Setup.exe from this page.
Run it on the workstation where Civil 3D, Revit or Navisworks is installed.
Open the Autodesk product and confirm the DrH panel is there.
Use Add, Update, Remove, Settings and About to manage your tools.
07 download
The installer is served directly from the DrH download domain, so the button starts the file straight away rather than sending you through a preview page. Install it once; from then on the panel updates itself.
08 faq
Civil 3D, Revit and Navisworks. Package families target host versions from 2021 to 2027.
Yes. Civil 3D covers LISP routines and .NET DLL tools. Revit and Navisworks focus on DLL tools, with Revit add-ins handled through .addin sidecars.
From a folder on the workstation or from the online DrH library. Both use the same import flow, and LISP and DLL packages have separate library feeds.
No. Updating the manager leaves the managed tools in place, so an update does not force a redeployment.
Packages are organised by runtime channel. Use the family that matches the host you are loading into, and several Autodesk versions can sit on the same machine without colliding.
A file sitting next to a package that DrH picks up automatically. A PNG with a matching name becomes the tool icon; a Revit .addin file supplies the commands to expose.
The desktop log. Import, load, update and run activity is written there, so a failure can be traced instead of guessed at.
The manager is free forever, including importing and running your own tools. DrH Pro is $100 per user per year for one named user, and DrH Max is $375 a year for firms, as a fixed pack of 5 users. Both add the maintained online library, every update published during your year, and the ability to request new tools. Billing is yearly.
Yes — that is the point of Pro. Describe the task you repeat by hand and, if it fits the library, it gets built and published. It then shows up in your panel the next time you press Update. Send a request.
One named person, across as many workstations as that person uses. A desk machine and a laptop are one licence, not two.
Yes. Replacing the same R2 object while keeping the filename DrH_Setup.exe keeps the download link on this page unchanged.
09 support
Write with the host version, the DrH build number and the relevant part of the desktop log. That is usually enough to identify the problem on the first reply.