Share
 
 

Release Notes for InfoDrainage 2025.5

This document lists product fixes included in InfoDrainage 2025.5 and InfoDrainage 2025.5.1.

InfoDrainage 2025.5.1

Entry Loss Audit
An issue with calculated angles between connections displaying incorrectly has been resolved.
Flow Path
An issue causing a crash when duplicating a Flow Path has been fixed.
Inflows
An issue with the pollutant calculation that resulted in rapid drop off was corrected.
Results Summary
Resolved an issue where Max. Outflow was not matching the maximum value of Total Outflow in results forms, when multiple outlets used at outfall
Sump Depth
Surcharged and flooded status at junctions is now correctly handled when a sump depth is specified.
Land Use in Inflow forms
An issue causing the software to crash when checking or unchecking land uses in inflow forms has been resolved.
Hydraulic Simulations Engine
An issue impacting flows through porous structures has been resolved.

InfoDrainage 2025.5

Static Runoff
Fixed a crash that occurs when using Chinese Rainfall from the Rainfall ribbon.
Culvert Design
More specific outlines provided to engine for Arch and Ellipse connections. Corner Splay no longer incorrectly attributed to Arch and Ellipse connections.
MDX Export
An issue with MDX export where an outlet with a flow control discharging to an outfall has been fixed.
Rainfall Viewer
An issue in the rainfall viewer when switching between ARR temporal patterns has been fixed.
2D Validation
Validation form is no longer displayed if there are no 1D/2D validation issues.
Land Uses and Soil Types
Correct icon displayed when changing template of land use objects regardless of translation.
Fixed a crash when files created or round tripped with IDCAD.
Foul Catchment
Fixed a case where flow is not calculated correctly for Main Drainage catchments.
IDCAD
Inflows exported by IDCAD do not have the cache set up.
Duplicate Selection
An issue where duplicating multiple items selected in the plan view was causing InfoDrainage to crash has been resolved.
3D View
An issue where '&' in a label crashed the 3D view has been resolved.

Was this information helpful?