Share
 
 

Release Notes in Version 2026.0

This topic lists any bugs that have been fixed between versions 2025.5 and 2026.0 of InfoWorks ICM.

See Known Limitation and Issues for a list of limitations and any issues that we are aware of.

The fixes listed below are those that are viewed as likely to impact on users in an unexpected way, mainly changed simulation results, or differences in behaviour that might not be obvious.

Windows 11 experience

The user interface experience in Windows 11 has improved, which some buttons that were invisible now present. Some buttons on grid windows still only appear when the mouse hovers over them.

Creating TIN ground models from Shapefiles

InfoWorks should no longer crash when creating a TIN ground model from a Shapefile (SHP) containing points with null geometry.

Validation of mesh zones

Mesh zone validation errors no longer show incorrect object types and field names

Pipe full capacity

Simulation results for pipe full capacity were assuming a single barrel. The number of barrels is now correctly accounted for in the calculation.

Long-term simulations using ReFH runoff model

Simulations no longer fail when using the ReFH runoff model in simulations lasting more than three years, although the implementation of ReFH in InfoWorks is still not suitable for long-duration simulations.

Soil water content result

The soil water content is now reported correctly for simulations running on a GPU using databases of version 2026.0 and later. Previously, if the depth in the 2D element transitions from dry to wet just before results were saved, the soil water content percentage was reported as zero. This was purely a results reporting issue; the soil water content used in calculations was correct. Pre-2026.0 databases retain the old behaviour.

Cloud simulation failures with detailed rainfall

Simulations run in cloud databases with rainfall containing more than about a million profiles (e.g. from radar) should no longer fail with a segmentation fault.

Flow into buildings

A regression introduced in 2025.3 meant that buildings were not behaving in a porous way (i.e. water was not flowing into buildings) and the "flow into buildings" result reported was an arbitrary value. This has been fixed.

Results of simulations using initial states in cloud databases

Using a cloud database, when a simulation used an initial state from another simulation, then results could not be downloaded if the states-providing simulation had been deleted. This has been rectified.

Meshing with buildings

Some spurious messages in the mesh log about 2D line sources that were sometimes appearing when meshing with buildings have been removed.

Subcatchment "drains to" field

When the "Drains to" field on a subcatchment is set to an invalid value (for example due to an import), the software no longer crashes when you try to open the network.

Database update scripts

The scripts for updating Oracle and SQLServer databases from version 2025.2 to 2025.3 were missing from 2025.4 and 2025.5 installers. They have been reinstated.

Failed 2D simulations in cloud databases

An intermittent crash "SIGSEGV, segmentation fault occurred" when initialising 2D simulations on a GPU in cloud databases has been improved. The failure is due to lack of memory, and should now be reported with an accurate error message.

2D initial conditions

When using initial conditions from a different mesh, in rare circumstances the interpolation of depths was incorrect if the centroid of a 2D element is exactly coincident between the two meshes. This has been fixed for databases in version 2026.0 and later. Earlier version databases retain the existing behavior.

RDII

A crash when running simulations with a network containing RDII but no rainfall event has been fixed.

Undefined ground levels

Where a 2D zone is precisely coincident with the ground model, 2D mesh vertices on the boundary sometimes get undefined ground levels leading to incorrect results from simulations. Simulations launched in 2026.0-format databases will now fail in this situation, and simulations launched in earlier format databases will contain a warning in the log.

Copying archived networks to the cloud

When the command line archive tool has been used on a network, and the network is subsequently copied to a cloud database, in some causes the particular history of data and branches in the network can cause the network to be copied incorrectly. This has been fixed.

Performance of on-premise 2D simulations on a CPU

A performance degradation in 2D simulations run on a CPU from an on-premise database introduced in version 2025.4 has been rectified. This regression did not affect GPU or cloud simulations.

Vulnerabilities

The following security vulnerabilities have been addressed:

CVE-2023-3046, CVE-2023-4807, CVE-2024-9681, CVE-2024-9143, CVE-2024-6119, CVE-2024-4741, CVE-2024-4603, CVE-2024-2511

See the Autodesk Trust Center for details about vulnerabilities in InfoWorks software.

Was this information helpful?