Common issues, what they mean, and how to resolve them.
The plugin did not load. HydraStorm loads automatically when Civil 3D starts — no manual loading step is required. If the command is unknown:
%ProgramFiles%\Autodesk\ApplicationPlugins\HydraStorm.bundle (default install) or %AppData%\Autodesk\ApplicationPlugins\HydraStorm.bundle (if you chose "Install for me only"). If it is missing, re-run the installer.The window may be off-screen on a previously connected monitor. Reset its position by deleting any saved layout state in %LocalAppData%\HydraStorm\ or move the C3D window so the WPF child can re-center.
Loops in storm drain networks are not supported. Open the Network Issues dialog (toolbar) to identify the offending pipe. Common cause: a pipe whose From and To structures cross over a confluence creating a circular flow path.
The normal-depth solver could not find a stable depth within the iteration limit. Causes:
If none of the above resolves it, capture a diagnostic bundle (see below) and send it to support — the iteration limit and convergence tolerance are internal engine settings, not currently user-adjustable.
Surcharge has reached or topped a structure rim. The compliance check flags this when HGL Cover (configured in Project Settings) is violated. Resolution: enlarge upstream pipes, increase slope, or adjust the structure rim.
HEC-22 / iSWM / municipal loss equations are evaluated dynamically. If the upstream geometry produces a K value the published table can't represent, HydraStorm marks the cell yellow in the Excel export and writes the literal computed loss instead of the lookup. The number is correct — the spreadsheet just can't round-trip it.
Most often a locked drawing — another command is running or the document is read-only. Check the Civil 3D command line for the underlying error. If a single pipe fails, the rest of the batch still applies; check the calculation messages banner.
Confirm the pipe and structure label styles are configured in Project Settings > Output, then run Output ▾ > Apply Label Styles from the toolbar. See Profiles & Labels.
HydraStorm hides data-shortcut'd networks (typically water/sanitary) from the analysis dropdown to avoid accidentally analyzing them. They are still loaded for crossings detection. To analyze a referenced network, promote it to a local network in Civil 3D first.
Basin names in HydraLink and structure names in C3D differ enough that even fuzzy matching can't bridge the gap. Open the HydraLink import dialog to manually map basins to nodes. The matcher applies a 5-tier strategy (exact → normalized → fuzzy → spatial → manual) — try renaming for cleaner future imports.
The watcher detected an edit on disk. Click the prompt to reload, or ignore it if you're staging changes. The reload re-runs basin matching but preserves your manual overrides.
Yellow highlight marks cells where HydraStorm overrode the spreadsheet's formula with a computed literal. This happens when:
The literal value is the correct hydraulic answer. If you re-edit the spreadsheet, that cell will not auto-recompute.
HydraStorm strips macros from the embedded template at save time. If you see this error, send the file to support with the project file (.hsp) attached for diagnosis.
For any unresolved issue, run Help > Run Diagnostic (HSDIAG) from the toolbar. This generates a Markdown dump of your project state, network topology, and calculation output. Email the resulting file to support@bezaleldesignlab.com.
Email support@bezaleldesignlab.com with the diagnostic bundle and a description of what you were doing.