Skip to content

MIKE+ 2026 Release Notes

Contents

  • Introduction
  • System requirements
  • Installation
  • Licensing
  • Product invocation
  • Support
  • Important note about import of MIKE URBAN projects
  • New features and fixed issues

Introduction

Welcome to MIKE+ 2026 Update 1.

In this Release Notes, you will find information about new features, improvements and fixes, and what you need to know to install and get started with MIKE+ 2026 Update 1.

MIKE+ is our new, flexible system for modelling and designing water distribution networks and collection systems for wastewater and storm water, as well as for modelling river networks and 2D surface flooding.

MIKE+ is offered in two versions:

  • MIKE+
  • MIKE+ ArcGIS

With MIKE+ you get:

  • GIS-based model building and data management
  • Powerful hydraulic simulation engine that supports parallel processing
  • Integrated water quality, fire flow, real time control, flushing, multi-source tracing and hydraulic simulation (water distribution)
  • Integrated water quality, control rules, LID and soakaway, rain dependent inflow and infiltration (collection system and river network)
  • Long-term statistics (collection system)
  • Integrated 2D hydraulics and water quality, dynamic interactions with collection system and river networks, surface flows visualisation (2D overland)
  • Full undo and redo capability in all editors
  • Thematic mapping and integrated results visualisation
  • Open data models - easy integration with other applications
  • Instant data checking and validation

With MIKE+ ArcGIS you get:

  • Sophisticated GIS capabilities and smooth integration with ArcGIS Pro. MIKE+ embeds ArcGIS/ArcGIS Pro software for GIS-based model building, data management and result presentation.

System requirements

Supported Operating Systems

The supported operating systems listed below have been tested in accordance with MIKE’s Quality Assurance procedures. DHI’s warranty, as set out in the General Terms and Conditions (Schedule 1) for MIKE software and Software Maintenance Agreement (Schedule 4), only apply when MIKE software is installed and used on these supported systems:

  • Windows: Windows 10 Pro version 22H2, Windows 11 Pro version 24H2 & 23H2, Windows Server 2022 version 21H2
  • Linux (engines only, but not all MIKE+ engines): Ubuntu: 20.04 LTS, 22.04 LTS, 24.04 LTS, Red Hat Enterprise 8 and 9.

Any operating system not listed is considered unsupported. Installing or using MIKE software on an unsupported system is at Licensee’s own risk and DHI provides no warranty, no maintenance coverage, and is not obligated to offer support or troubleshooting.

The supported Linux distributions are those that have been tested and verified by DHI for MIKE 2026 Update 1. Other distributions may, or may not, work and are not recommended. However, past versions of MIKE Software have been successfully installed on other Linux distributions, including CentOS, Ubuntu Kylin, Galaxy Kylin (V10), AlmaLinux and Debian (all 64-bit).

Note

Even if an operating system is listed as supported, it will be considered unsupported if MIKE software is run in a virtualized environment, e.g., a guest operating system or a Docker container.

Minimum hardware/software requirements

Item Requirement
Processor compatible with x64 instruction set architecture, 2.2 GHz or higher *
Memory (RAM) 4 GB or higher **
Storage 64 GB or higher **
Display resolution 1024 x 720 (Full HD 1920 x 1080 recommended), 24-bit color (true color)
Graphics adapter 64 MB RAM (256 MB RAM or higher recommended), 32-bit true color ***
Software requirements Microsoft .NET Desktop Runtime 8.0.0 or a later patch release.

* MIKE+ is developed, built, and tested using Intel® technology on Intel® processors.

** The actual required amount of memory and disk space depends on the usage (application, model setup, size of data files etc.)

*** MIKE+ utilizing GPU for 2D overland simulations requires a Nvidia graphics card with compute capability 7.5 or higher. Please note that some of these graphics’ cards have varying performance in single compared to double precision calculations. The GPU functionality is based on version 13.0 of the Nvidia® CUDA® Toolkit.

Installation

To install MIKE+:

To install MIKE+, please go to the MIKE+ product folder and execute the setup.exe file from the downloaded, un-zipped installation files. Press the ‘Install’ button to begin installation.

The setup program will automatically install all necessary files and folders on your computer. Additionally, an entry is created in the Start Menu for MIKE+.

To install MIKE+ ArcGIS:

To install MIKE+, please go to the MIKE+ product folder and execute the setup.exe file either from the downloaded, un-zipped installation files. Press the ‘Install’ button to begin installation.

The setup program will automatically install all necessary files and folders on your computer. Additionally, an entry is created in the Start Menu for MIKE+.

Please choose ArcGIS Pro’s "ArcGISPro.msi" to install ArcGIS Pro separately. This version of MIKE+ comes with ArcGIS Pro 3.6.2. You find the installation of ArcGIS Pro in the folder "Prerequisites\ArcGIS Pro 3.6". Other versions of ArcGIS Pro might also work with MIKE+ but are not covered by warranty and software maintenance agreement conditions.

Optional installation of PostgreSQL/PostGIS:

Both MIKE+ and MIKE+ ArcGIS are installed with SQLite/SpatiaLite. If you wish to use the alternative database option, PostgreSQL/PostGIS then please install the two products found in the "Prerequisites\PostgreSQL 18.3" and "Prerequisites\PostGIS 3.6.1" folders.

For more information about the installation process, we recommend that you read the MIKE+ installation guide here.

A separate installation guide for MIKE+ for Linux is available here.

Licensing

With Release 2026, we are introducing a new licensing system for MIKE software.

For on-line users, the new Internet License Server is more secure and robust, and less dependent on a stable internet connection. This should significantly increase the overall reliability of the Internet License Server.

For off-line users, the main difference is that dongles and license files are replaced by a Network License Server that is locked to specific computer. Just like the old dongles, a Network License Server can distribute licenses across a local network.

The new license system is managed using an application called “DHI License Management 2026”. Older versions of the license system (pre-2026) are managed using an application called “DHI License Management”.

The pre-2026 license system will be phased out by the end of 2026. We will communicate more details of this phase-out to users of the pre-2026 system in Q2 2026.

In the new system, - Every company needs an Administrator to manage Entitlements. This person will be created automatically by DHI’s Customer Care team. - The Administrator can add Users in their company’s Webportal. - The Administrator can set up Local License Servers for off-line usage. - Users can configure their connection to the Internet License Server or a Local License Server from the new desktop DHI License Management 2026.

All the required files will be installed during the MIKE Software installation. The details of the installation, configuration and connection to your License Server are described in the documentation for DHI License Management 2026.

Note

Starting any MIKE Software without a valid license will cause the program to run in demo mode. When running in demo mode, the software has access to all editors, computational engines and editing facilities. The restrictions that apply to saving setups and executing simulations are product specific.

Product invocation

Launch MIKE+ from the Windows Start menu.

Support

For general support, please refer to our Customer Care Portal.

If you experience any difficulties, or if you have questions, please contact our Customer Care team at mike@dhigroup.com.

You can also contact your local Customer Care team for support in your local language. A list can be accessed here.

Important note about import of MIKE URBAN projects

MIKE URBAN is officially no longer supported or maintained, and compatibility with newer operating systems cannot be guaranteed. Running legacy products in modern environments can be complex, and as a result, we cannot ensure reliable performance on all operating systems. Factors such as your operating system version, hardware configuration, and third-party software, may impact functionalities.

Additionally, ESRI has announced the retirement of ArcMap, which is required for MIKE URBAN installations. See related article here.

As a consequence, MIKE+ 2026 (and its future updates) is the last version supporting the 'Import from MIKE URBAN model' functionality. The next major version of MIKE+ will no longer support importing model setups from MIKE URBAN.

New features and fixed issues

Every new release of MIKE+ consists of new modules, new features and/or corrections to problems or significant inconsistencies discovered in previous releases. Please find below short descriptions of the most significant news.

Release 2026 Update 1

Warning for 2D overland projects update

The storage of 2D overland model data in the database has been changed in this new version. This major change of database structure can e.g. break previous configurations made for importing 2D boundary conditions data in the 'Import and export' tool, therefore requiring updating the import configuration accordingly. Former projects containing 2D alternative scenarios may also get several additional 2D alternatives created during the upgrade to the new version: even though these new alternatives may not be used by any scenario, they are necessary to maintain compatibility with previous versions. Refer to the description of 2D overland new features in the table below for additional information. It is recommended to evaluate the consequence of this change on existing 2D overland models before upgrading them to this new version.

New features

Module/type New feature
General It is now possible to customise units for display of results. These custom units are defined in the 'User preferences' window. They apply both when working on an opened project database and in results viewing mode (without any database opened). They are configured for the local computer and will apply to all projects on that computer, but their configuration can be saved to a file to quickly share and change settings. See Figure 19 below.
General For 'Rivers, collection system and 2D overland flows' projects, a new option allows to automatically load intermediate results while the simulation is running. This allows displaying and analysing the current status of the results without having to wait for a long simulation to complete. Opened time series plots, result layers on maps or result tables are automatically refreshed to show the latest results (every 2 minutes). This new option is available in the 'User preferences' window. See Figure 20 below.
General The former background maps provided by Google Map and Open Street Map are replaced by a new and single source powered by MapTiler, which offers significantly more map themes. These new online maps also allow to be combined with other maps obtained from WMS or WMTS web services.
General Labels shown on the map can now be customised by combining multiple fields together. This is enabled using the new 'Custom expression' type of label in the symbology editor. This custom expression is edited in the expression editor which allows defining labels on multiple lines using a new NewLine() function. See Figure 21 below.
General Labels shown on the map can now be shown using a halo / contourline, for improved visibility. See Figure 21 below.
General 2D layers like DEM, 2D overland meshes or 2D result files can now be displayed with a color palette automatically updating to local minimum and maximum values shown on the screen, when zooming in and out and when panning. This is enabled by selecting the new option 'Auto-scale palette to visible data' in the symbology editor. See Figure 22 below.
General New keyboard shortcuts have been added:
- Alt+E activates the 'Identify' tool
- Alt+D activates the 'Open layer editor' tool.
Refer to the chapter 'Keyboard and mouse shortcuts' from the user guide to access the complete list of available shortcuts.
General Result maps now maintain the current zoom level when unticking or re-ticking a layer, and when updating a layer's symbols, instead of resetting the zoom to full extent.
General The design of the flags used on the map to control the profile plots' paths has been improved to enhance their visibility.
General The display of the file paths has been improved in various editors and tools, so that the file name itself is always visible.
General The performance of the 'Import and export' tool has been significantly improved when working with a model setup stored in a PostgreSQL database on a distant server.
General The time required to copy data from a MIKE+ table to the clipboard has been significantly improved when working with a model setup stored in a PostgreSQL database on a distant server.
General Warning and errors from the 'Import and export' tool which are shown in the file msg.log when it's executed from the user interface, are now also saved to a file when it's executed from command lines.
General The constraints on default result files defined in 'Rivers, collection system and overland flows' mode have been relaxed. It is now possible to e.g. rename them, change their spatial extent or even delete them from the 'Result files' editor.
Collection System In the 'Generic shapes' editor, a new button allows recomputing processed data for all or selected shapes.
Collection System HTML summary files created during simulations can now also include a summary table for boundary conditions. This can be activated with the new 'Boundary conditions' check box in the 'Network summary' editor. See Figure 23 below.
Collection System and Rivers Sensors defined with a variable expression now support expressions with more than 255 characters.
Collection System and Rivers A new 'Apply' check box has been added to the 'Sensors' editor, allowing to ignore a sensor in simulations, for example when it is defined on a structure which is also ignored.
Collection System and Rivers For catchments described with land uses, it is now possible to save some catchment results at the land use level, including e.g. runoff, depth on surface, losses, infiltration and evaporation results. These new result items can be selected in the 'Result files' editor, in a new group called 'Land use results' in the 'RR items' tab. See Figure 24 below.
Collection System and Rivers The result item 'Control rule no.' is now saved per control rule, and not per controlled structure anymore. This allows saving results for all controls even when multiple control rules are applied to the same structure (typically when controlling both the start level and the stop level of a pump).
Rivers The 'Create flood raster' tool, introduced with MIKE+ 2026 and which compares flood water levels from 1D and 2D results with a detailed DEM to create a single raster of water depths, has been improved with a new option to extrapolate river results beyond the river bank. This new option extrapolates water levels computed in the 1D river model within a user-defined maximum distance beyond the cross sections' extent, and compares them with ground levels from the DEM to map the water depths. This allows filling in gaps that may exist along river banks when there is a misalignment between the river model and the 2D domain, or allows extending the mapped area of a pure 1D model when cross sections do not cover the entire flooded area.
This tool is still under development and additional enhancements are planned in future versions to better control the mapping. For example, in this first version:
- The tool can only map water depths based on water level, but e.g. not current speed.
- Water levels from storages on river network are not considered and cannot be mapped on the DEM.
- Water level from a cell / element of the 2D domain is considered uniform within that cell / element, i.e. the raw water level result from the cell / element is used to compute the water depth in all pixels of the DEM within that cell / element. While this is suited for areas with small water surface slope and/or with small cells / elements, it may lead to discontinuous water depths mapping in areas where a significant difference of water levels is computed between neighboring cells / elements.
- The tool will not map 1D results if the model setup and its result file contain mistakes in placement of cross sections' markers (i.e. if the cross sections markers are not defined in the correct order for some cross sections). The solution is to correct markers location in the 1D result file, either by correcting the model setup and re-running the simulation prior to running the tool, or by executing an existing Python script which needs to be requested via the MIKE Support hotline.
See Figure 25 below.
Rivers New derived result items are available, providing the difference between the computed water level in a calculation point and its bank levels. Result item 'Left bank exceedance' provides the comparison with marker 1's level (left bank), 'Right bank exceedance' provides the comparison with marker 3's level (right bank), and 'Maximum bank exceedance' provides the maximum of the two. These new items can be selected while loading a result file, along with former derived results. See Figure 26 below.
2D overland The option to import 2D culverts from shape files using the 'Insert from file' button has been reviewed and improved for long culverts. It now allows importing both longitudinal lines and end section lines from different shape files.
2D overland The storage of model data in the database has been reorganised to split data related to 2D boundary conditions from other 2D data, so that the data group '2D boundaries data' in the scenario manager now covers all types or 2D boundary conditions. This allows defining more independent alternatives for 2D boundary conditions and for 2D domain and structures.
NOTES: this major change of database structure can break previous configurations made for importing 2D boundary conditions data in the 'Import and export' tool, therefore requiring updating the configuration accordingly. Updating 2D overland models with scenarios to this new version may also create additional alternatives to support backward compatibility, although some alternatives may not be used in any scenario.
2D overland While selecting the coordinate system for a project (either from the 'New model setup' window or from the 'Coordinate system' editor), the 'Select file' button now allows picking the coordinate system used in a .mesh or .dfs2 file. This typically allows to quickly apply the same coordinate system in the project database as in the file used as 2D domain.
SWMM Connections between conduits (typically surface conduits with a 'Street' shape) and inlets are now shown on the map. These new connection lines can also be refreshed with the button 'Refresh connection lines' in the ribbon, e.g. after importing conduits and inlets data with the 'Import and export' tool or after upgrading a model created with the previous version of MIKE+.
SWMM It is now possible to define alternative scenarios for data from the 'Streets' and 'Inlets' editors. These editors are controlled by the data group 'Network data' in the scenario manager.
Water Distribution Additional result items 'Pump speed' and 'Valve opening' are now saved during Water Hammer simulations.
Water Distribution A new editor for 'Advanced Metering Infrastructure' has been added to the 'Online analysis'. It supports automatic updating of water demands based on physical water meters (AMI) data, for MIKE+ models used online through Water Distribution Online or WaterNet Advisor.
MIKE 1D engine Item descriptions in the 'Predefined options' tab of the MIKE 1D engine configuration window have been updated. Some default values have been modified.
MIKE 1D engine The MIKE 1D engine parameter 'Velocity distribution coefficient (Alpha)' has been split so that different values can be defined for River and Collection System modelling.

The new options for customizing display units for results, in the user preferences (available from the File menu)

Figure 19 – The new options for customizing display units for results, in the user preferences (available from the File menu)

The new option for loading intermediate results during simulations, in the user preferences (available from the File menu)

Figure 20 – The new option for loading intermediate results during simulations, in the user preferences (available from the File menu)

The new options to display labels based on custom expressions and using halos on the map

Figure 21 – The new options to display labels based on custom expressions and using halos on the map

The new option to automatically re-scale color palettes to current view for rasters and 2D overland layers

Figure 22 – The new option to automatically re-scale color palettes to current view for rasters and 2D overland layers

The new option to get a statistics table for boundary conditions in the HTML summary file

Figure 23 – The new option to get a statistics table for boundary conditions in the HTML summary file

The new result items computed per land use in catchments

Figure 24 – The new result items computed per land use in catchments

The new option to extrapolate 1D river results beyond lateral extents of cross sections in the ‘Create flood raster’ tool

Figure 25 – The new option to extrapolate 1D river results beyond lateral extents of cross sections in the ‘Create flood raster’ tool

The new overbank spilling derived results for river networks

Figure 26 – The new overbank spilling derived results for river networks

Fixed issues

Module/type Error/Inconvenience
General The time series plot wrongly displayed 0-values in empty time steps, when displaying data from a .dfs0 file.
General Parallelisation settings for simulations (defined in the 'Parallelisation settings' window in the ribbon) were unexpectedly controlled by the scenario manager. Specified settings now apply to all scenarios.
General The 'TrimStart' and 'TrimEnd' functions available in the expression editor unexpectedly removed any sequence of characters from the string to be deleted. They now only remove the entire requested string.
General The 'Identify' function did not work when MIKE+ was configured to use another language than English.
General While editing a color palette for 2D raster or mesh layers in a project with a US unit system, the break values of the palette had to be specified in SI units.
General The 'Show histogram' button in the symbology editor returned an unexpected error.
General An unexpected error occurred when trying to save and reload the symbology for a TIF layer from a file.
General An unexpected error occurred when leaving the ID field blank in the 'Plots and Statistics' editor, which caused MIKE+ to stop working.
General Some performance criteria were wrongly computed in the 'Plots and statistics' editor, when the measured time series was a .dfs0 file containing values in a different unit than the one shown in 'Plots and statistics'.
General Invalid characters used in the project sometimes corrupted the .mupp project file, leading to the error "Invalid pfs node" when trying to reopen it.
General After sorting an overview table based on a user-defined column of results, the table displayed all records even if the option 'Show selected' was active.
General MIKE+ could not open projects properly when setting language to German.
General MIKE+ could not work properly on operating systems using Turkish language.
Collection System Field Calculator sometimes failed with the error "Some of MUIDs to be validated do not exist in table" while unticking the 'Apply' column for multiple nodes.
Collection System Customisation of unit for the field 'HX' from the 'Generic shapes' editor offered a very limited list of units.
Collection System Undefined LTS initial conditions and LTS global parameters were not identified and reported as an error.
Collection System MIKE+ did not respond after executing and trying to close the 'Submodel manager' without having generated updated boundary conditions.
Collection System Sensors with type 'Pump ON/OFF' wrongly reported the selected pump ID as invalid when the pump was not set to be controlled with advanced regulation.
Collection System Profile plots sometimes failed to show pipe levels for pipes defined with generic shapes of type 'HW Open'.
Collection System Profile plots wrongly displayed a ground level line along natural channels, interpolated between upstream and downstream connected nodes.
Collection System Profile plots sometimes failed to properly display water levels in natural channels, when the plot also included closed pipes.
Collection System and Rivers Profile plots failed to properly display filled water levels at junctions between rivers and pipe network.
Collection System and Rivers Loading a .lsf symbology file for Catchments sometimes corrupted the symbology options with an invalid list of fields to pick from, to select the source unique values.
Collection System and Rivers Water quality simulations stopped with an unclear error message when WQ boundary properties were defined with a type incompatible with the selected WQ component type.
Collection System and Rivers Water quality simulations sometimes stopped with an unexpected error message "An item with the same key has already been added".
Collection System and Rivers Missing dispersion parameters for Advection-Dispersion simulations were not reported as an error.
Collection System and Rivers Simulations with control rules sometimes stopped with an unexpected error message "The given key was not present in the dictionary".
Collection System and Rivers Simulations stopped with an unclear error message when boundary conditions were defined with a .dfs0 file containing items with an undefined item type.
Rivers Open culverts automatically inserted on structure links showed an invalid river name, in case the structure link had been renamed.
Rivers The 'Insert all rivers' button in the 'Boundary conditions' editor sometimes returned an unexpected error.
Rivers The tool 'TS from map' did not allow to plot result time series in storages.
Rivers An unexpected error was obtained in the 'Cross-sections' editor when the coordinates of the cross sections were set to be the same for the start and end points, leading to a zero length.
Rivers Profile plots failed to properly display water levels in closed cross sections.
Rivers When exporting the cross sections layer to a shape file, exported cross sections were wrongly located when the model projection's unit was US feet.
Rivers Mapping a river result file on a DEM using the 'Create flood raster' tool sometimes returned the error "Index was out of range".
Rivers Importing a MIKE 11 model setup with control rules sometimes failed, when the operating system was set to use the comma as the decimal separator.
Rivers When importing a MIKE 11 model, storage areas defined on link channels were imported twice.
Rivers When importing a MIKE 11 model, storages imported from link channels were sometimes imported without their geometry table.
Rivers When importing a MIKE 11 model, the original .xns11 file from the MIKE 11 model was overwritten if it had the same name as the MIKE+ database and if both were saved in the same folder.
Rivers When importing a MIKE 11 model, initial conditions in storages created from link channels were not imported.
2D overland In the 'Exclude rivers' tool, the table used with the 'Channels from table' option sometimes failed to show the list of channel IDs.
2D overland An unexpected error was obtained when trying to apply a symbology based on unique values, for 2D culverts.
2D overland When trying to start a simulation involving a SWMM network coupled to 2D overland from a command line, only the SWMM network simulation was executed.
SWMM Diversion curves were incorrectly imported from and exported to .inp file, leading to a syntax error when starting the simulation.
Water Distribution Unexpected results were obtained at flow-controlled variable speed pumps, when the program was not able to find a solution if the pump speed range was too wide.
Water Distribution Friction loss was incorrectly computed with Chezy-Manning formula in steady-state simulations.
Water Distribution In the ‘Pipes’ editor, the ID selector window used to pick a roughness value from a list of pre-defined materials failed to pick the correct value according to the head loss model selected in the project.
MIKE 1D engine Flood mapping calculations now limited to bank markers in cases where cross-section information is available outside of bank markers.
MIKE 1D engine Flood raster calculation now excludes closed cross-sections.
MIKE 1D engine Fixed error in parallelization settings (TT66361).
MIKE 1D engine Added error message when routing branch located downstream of HD branch.
MIKE 1D engine Removed inconsistent use of SI and US units in log file (TT66587).
MIKE 1D engine Enabled use of orifice gate minimum (maximum) settings greater (less) than orifice top (invert) level (TT65402).
MIKE 1D engine Removed obsolete error message regarding flow regulation in links (TT63509).
MIKE 1D engine Enabled writing to html summary when running data assimilation and assimilating water level and discharge measurements on the same branch (TT66691).
MIKE 1D engine Fixed water balance error at structure links (TT66665).

Release 2026

New features

Module/type New feature
General For projects of type 'Rivers, collection system and overland flows', it is now possible to start simulations as a standalone process, independent from the opened MIKE+ window. This is achieved with the new button 'Run detached' in the 'Simulation setup' editor. This typically allows running multiple simulations simultaneously from the same MIKE+ project. It also allows closing MIKE+ while the simulation is running, to release the license seat for MIKE+ which can then be used by another user or computer (note that the option to continue the simulation in the standalone window is still offered when closing MIKE+, in case the simulation has been started with the 'RUN' button). See Figure 1 below.
General It is now possible to save lists and bookmarks in folders, in the 'Selection manager', 'Bookmark manager', as well as in the bookmark manager of Time Series plots. See Figure 2 below.
General A new option has been added to the 'Topology repair' tool to repair links geometries so that the ends of the links match the locations of connected nodes on the map. See Figure 3 below.
General The tool formerly called 'Combine DEM tiles', available in the 'Tools' tab of the ribbon, has been renamed 'Combine and convert rasters' and offers the following improvements:
- It is now also accessible in Water Distribution project type
- It now supports overlapping tiles
- It supports ESRI ASCII grids with cell-center definition.
General The performance of the 'Field calculator' tool has been significantly improved when updating special fields supporting different units, when working with a distant PostGIS database.
General A new option to swap data from X and Y axes in scatter plots has been added. It is available from the context menu of the plot. See Figure 4 below.
General The table at the bottom of the profile plot window can now be removed, when all its items are deselected from the Properties window. See Figure 5 below.
General The default title of new profile plots now describes the start and end locations of the profile.
General When exporting the profile plot to a CAD file, the default file name of the output file is automatically named according to the profile plot window's title.
General Changes to the profile plot's toolbar settings (hiding / showing buttons) are now persistent after saving the project.
General From the 'Add layer' window used to add a new layer to the map, the default behavior while browsing feature layers is now to show all supported file types (.shp, .xyz, .dwg, .dxf), instead of a single file type.
General In 'Versions management' tools, the 'Update' tool has been improved so that in case the former model version used a property of the former asset data unchanged, and this property has been updated in the new asset data, this property is no longer always updated in the new model version. A choice is now offered between two possible actions: keep the former property unchanged, or update with the new value from the new asset data. See Figure 6 below.
Collection System In the 'Nodes' editor, manholes can be defined with a new cover type 'Displaceable cover', for which the opening of the manhole gradually increases with the pressure in the node, following a user-defined relationship between the pressure and the opening. This allows modelling manholes which function as sealed covers at the start of the simulation, and which can be displaced by pressure during the simulation, at which point they transition to a partially or fully open spilling cover. The resulting opening percentage can also be saved to the result file for further analysis. See Figure 7 below.
Collection System A new derived result item 'Water minus pipe top level' is available on links. It is calculated as water level minus pipe top level, no matter if the water level is higher or lower than the top of the pipe. It is identical to the link pressure when the water level is higher than the top of the pipe, but provides negative values when it's lower. See Figure 8 below.
MIKE 1D engine Added support for including boundaries in the .html summary, including global rainfall and evaporation boundaries (TT64378). Note: This feature requires a run-time script to activate. If you’re interested in using it, please contact MIKE Support.
MIKE 1D engine Enabled conical assumption when computing basin volumes. The default assumption is for basin volumes to expand linearly with area (i.e., that the area is rectangular with a fixed edge). The conical option assumes that volumes expand assuming a circular area. The conical option can be activated by inserting a custom engine parameter called “BasinAreaInterpolation”, and setting the value to False.
Rivers Boundary conditions of type 'Network rainfall' and 'Network evaporation' can now apply to storages. Each boundary condition can be applied to either all storages, a list or an individual storage. See Figure 9 below.
Rivers Flags added to the map to draw a profile plot now snap to nearest cross sections to easily use cross section locations as start or end location of the plot.
Rivers Two new options are offered while exporting cross sections to shape file from the 'Layers and symbols' tree:
- It is possible to export only selected cross sections
- It is possible to export the extents of active cross sections (from marker 1 to marker 3). See Figure 10 below.
MIKE 1D engine Enabled new .xns11 output showing final breach cross-section when applying a limiting cross-section when using the energy equation method in a dambreak structure on river (TT66320). The .xns11 output file can be read using the MIKE IO 1D Python package or in a blank MIKE+ project.
Data assimilation Added estimation of lateral correction volumes when assimilating water level measurements.
Data assimilation Improved the installed example to demonstrate the assimilation of discharge measurements.
2D overland A new 'Create flood raster' tool is available in the 'Results' tab of the ribbon. This new tool compares flood water levels from 1D and 2D results with a detailed DEM to create a single raster of water depths, saved either in .tif or .dfs2 format. For 1D rivers, the ground level used to compute the water depth can alternatively be obtained from the cross sections instead of the DEM. This is the first version of the tool, and additional enhancements are planned in future versions to better control the mapping. For example, in this first version:
- The tool can only map water depths based on water level, but e.g. not current speed.
- Water levels from storages on river network are not considered and cannot be mapped on the DEM.
- Water level from a cell / element of the 2D domain is considered uniform within that cell / element, i.e. the raw water level result from the cell / element is used to compute the water depth in all pixels of the DEM within that cell / element. While this is suited for areas with small water surface slope and/or with small cells / elements, it may lead to discontinuous water depths mapping in areas where a significant difference of water levels is computed between neighboring cells / elements.
- 1D results cannot be extrapolated beyond the extent of the cross sections.
- The tool will not map 1D results if the model setup and its result file contain mistakes in placement of cross sections' markers (i.e. if the cross sections markers are not defined in the correct order for some cross sections). The solution is to correct markers location in the 1D result file, either by correcting the model setup and re-running the simulation prior to running the tool, or by executing an existing Python script which needs to be requested via the MIKE Support hotline.
See Figure 11 below.
2D overland The 'Compare' function in the 'Results' panel, which is used to create a result file of differences between two input result files, has been improved for 2D result files to compare differences of spatial extent of results. In former versions, this 'Compare' function created a single 2D output file containing numerical differences only in cells / elements flooded in both source files. This is now supplemented by a second output file containing differences in cells / elements flooded in only one of the two source files. The output value is a positive value matching the result from the first file, in cells / elements which are dry in the second file, and is a negative value matching the result from the second file in cells / elements which are dry in the first file. See Figure 12 below.
2D overland When a .dfs2 file is loaded on the map, the 'Identify' tool now shows the J and K indices of the selected cell in the property view, J and K being respectively the cell indices along the X and Y axes of the grid. See Figure 13 below.
2D overland Changes to the settings controlling the inactive areas in the '2D domain' editor, when the 2D domain is defined using a rectangular grid, are now saved in scenarios.
SWMM SWMM engine has been updated to version 5.2. The corresponding new features described below, released with this new version, are also enabled.
SWMM It is now possible to model runoff on streets and its capture by inlet drains. This is achieved using:
- A new 'Streets' editor to define streets' cross sectional shapes
- A new conduit shape type 'Street', to apply the street cross section above to a conduit
- A new 'Inlets' editor to define the type and the dimensions of inlet structures capturing the street runoff
- A new 'Inlets' tab in the 'Conduits' editor, to connect an inlet to a street conduit and connect them to a sewer node.
See Figure 14 below.
SWMM Four new pre-defined geometry types are available for nodes of type 'Storage unit': Cylindrical, Conical, Parabolic and Pyramidal.
SWMM A code selector window has been added to the 'Conduits' editor to ease the selection of culvert codes. It is opened using the '…' button next to the 'culvert code' field. See Figure 15 below.
SWMM A new "Type 5" pump type has been added to the choice of pump types in the 'Curves and relations' editor. It is a variable-speed version of the Type 3, where the Head versus Flow curve shifts position when control rules change the pump's relative speed setting.
SWMM The LID type 'Rain barrel' now has a new 'Covered' status, which prevents it from capturing direct rainfall when active.
SWMM In the 'Climatology' editor, it is now possible to select the temperature unit used in the selected external temperature file.
SWMM It is now possible to apply a local infiltration method per catchment. The default infiltration model selected in the 'Simulation setup' editor can be overridden by a local one selected in the 'Catchments' editor, in the 'SWMM infiltration' tab. See Figure 16 below.
SWMM A new 'Events' tab has been added to the 'Simulation setup' editor, to limit computation of full dynamic hydraulics to relevant periods of time.
Water Distribution It is now possible to model pressure relief valves in water hammer simulations, using a new 'Pressure override limit' setting. This is specified in the 'Water hammer' tab of the 'Valves' editor. See Figure 17 below.
Water Distribution It is now possible to add unsteady flow friction calculation to water hammer simulations. This option is enabled in the 'Water hammer' tab of the 'Simulation setup' editor.
Water Distribution A new 'Aggregation sensors' editor has been added to the 'Online Analysis' module. It allows defining fictional sensors from actual sensors, which can be used e.g. to compute zone water balance, sum up values from multiple flow sensors to get the total pump station flow, and similar.
Water Distribution A new option has been added to the 'Repair tool' to correct the 'Is active' status of junctions according to the 'Is active' status of connected links. See Figure 18 below.
Water Distribution The 'Comparison table' field in the 'Comparisons' editor used with 'Online analysis' module now supports table IDs with more than 40 characters.
Water Distribution The performance of the simulations executions has been significantly improved when working with a distant PostGIS database.

Running a detached simulation in ‘Rivers, collection system and overland flows’ mode

Figure 1 – Running a detached simulation in ‘Rivers, collection system and overland flows’ mode

Organising selections in folders, in the Selection manager

Figure 2 – Organising selections in folders, in the Selection manager

New option to repair links geometries in the 'Topology repair' tool

Figure 3 – New option to repair links geometries in the 'Topology repair' tool

Swapping X and Y axes data in scatter plots using the new option in the context menu

Figure 4 – Swapping X and Y axes data in scatter plots using the new option in the context menu

Hiding the table below the profile plot by deselecting all its items

Figure 5 – Hiding the table below the profile plot by deselecting all its items

New choice to keep values unchanged in Update tool, when the former model version used a value from the asset data which has been updated in the new asset database

Figure 6 – New choice to keep values unchanged in Update tool, when the former model version used a value from the asset data which has been updated in the new asset database

Applying the new ‘Displaceable cover’ type for manholes displaced with pressure

Figure 7 – Applying the new ‘Displaceable cover’ type for manholes displaced with pressure

The new derived result item 'Water minus pipe top level', available on Collection System networks

Figure 8 – The new derived result item 'Water minus pipe top level', available on Collection System networks

Boundary conditions of type 'Network rainfall' and 'Network evaporation' can now apply to storages

Figure 9 – Boundary conditions of type 'Network rainfall' and 'Network evaporation' can now apply to storages

Exporting cross sections to shape file now creates an additional shape file with extents of active cross sections

Figure 10 – Exporting cross sections to shape file now creates an additional shape file with extents of active cross sections

The new ‘Create flood raster’ tool used to combine 1D and 2D results in a single raster of water depths

Figure 11 – The new ‘Create flood raster’ tool used to combine 1D and 2D results in a single raster of water depths

The ‘Compare’ function now creates a second output file showing differences of flood extents, when comparing 2D results

Figure 12 – The ‘Compare’ function now creates a second output file showing differences of flood extents, when comparing 2D results

The 'Identify' tool now shows J and K indices of the selected cell, when identifying .dfs2 files

Figure 13 – The 'Identify' tool now shows J and K indices of the selected cell, when identifying .dfs2 files

New SWMM inlets allow connecting street conduits to the sewer network

Figure 14 – New SWMM inlets allow connecting street conduits to the sewer network

A new code selector helps selecting culvert codes in the 'Conduits' editor

Figure 15 – A new code selector helps selecting culvert codes in the 'Conduits' editor

The default infiltration model selected for the simulation can be overridden by a local model in selected catchments

Figure 16 – The default infiltration model selected for the simulation can be overridden by a local model in selected catchments

Modelling pressure relief valves in water hammer simulations, using the new 'Pressure override limit' setting

Figure 17 – Modelling pressure relief valves in water hammer simulations, using the new 'Pressure override limit' setting

The new option in the 'Repair tool' used to correct the 'Is active' status of junctions according to the status of connected links

Figure 18 – The new option in the 'Repair tool' used to correct the 'Is active' status of junctions according to the status of connected links

Fixed issues

Module/type Error/Inconvenience
General Alternative pipe geometries defined in scenarios were sometimes not properly restored with the scenario.
General Alternative pipe geometries defined in scenarios were sometimes not properly imported from MIKE URBAN setups.
General Polygons from shape files were in some cases not recognized by MIKE+, neither to display them on the map nor in the 'Import and export' tool.
General In the 'Selection Manager' window, updating the content of a list using the button 'Update from map' unexpectedly focused afterwards on another list, looking as if the wrong list was updated although the update was correct.
General Georeferenced .tif images added to the map were not restored at the correct location after closing and reopening the project.
General The 'Network simplification' tool returned an unexpected error message when trying to simplify a network containing parallel pipes (with same start and end nodes) and/or with pipes abnormally connected to the same node at its two ends.
General Model's 'Title' and 'Description' texts from the 'Description' editor were not saved in the database but in the .mupp project file, and were lost if this file went missing. They are now saved in the database too.
General An unexpected error message was sometimes returned from the 'Model and result report' tool when using the 'Joins' function.
General The Root Mean Square Error reported in the 'Statistics' tab of the 'Plots and statistics' editor was incorrect.
General When trying to create a new time series by importing external data (e.g. from text or Excel file), the window to configure the import failed to open up, preventing from importing the data.
General Special characters were not properly imported from some external data when using the 'Import and export' tool.
General The 'Catchment delineation' tool stopped without a clear error description when delineation is impossible due to a locally flat topography. It now reports the reason and the ID of problematic nodes.
General An unexpected error occurred when trying to display a profile plot with results, in case the result file was stored in a folder with an apostrophe in the path name.
General The 'Line style' setting used for lines symbols on the map did not work properly, and dashes and dots were not clearly visible.
General Exporting model data to a geodatabase using the 'Import and export' tool was abnormally slow and appeared as not progressing.
General User-defined status values (e.g. used for nodes and pipes descriptions) specified in former versions of MIKE+ were lost after updating to MIKE+ 2025 Update 1.
General The shape file with differences created by the 'Results differences' tool contained unexpectedly empty fields when the Operating System was set to use comma as decimal separator.
General Wrong connections to measurement stations were shown on the map after copying and pasting data into the 'Measurement stations' editor.
General Connection lines to measurement stations which are shown on the map can now be updated with the 'Refresh connection lines' tool in the ribbon.
Collection System While adding LTS results to a profile plot, the custom title defined in the 'Add item' window was not used in the result layer name added to the plot.
Collection System LTS extreme statistics results disappeared from profile plots after changing display settings in the 'Properties' window.
Collection System A new validation error reporting missing values in the 'Materials' editor has been added.
Collection System New validation errors reporting missing values in the 'LTS global parameters' editor have been added.
Collection System New validation errors reporting missing start/stop levels and acceleration/deceleration times in the 'Pumps' editor have been added.
Collection System Discharge sensors for control rules defined in valid pumps wrongly reported an error message.
Collection System Water level filling was not displayed in the profile plot view, in the pipe next to a pump.
Collection System When importing a MIKE URBAN model using the Sediment Transport module, local initial sediment depths were not correctly imported and therefore not correctly considered in later MIKE+ simulations.
Collection System When importing a MIKE URBAN model, the Event ID newly introduced in MIKE+ 2025 Update 1 remained undefined and had to be specified manually after the import.
Collection System and Rivers After closing MIKE+ while a simulation was running, and when continuing the simulation in a standalone window, this window failed to show the simulation progress for a 1D simulation (without coupling to 2D overland).
Collection System and Rivers When a simulation end time was set before its start time, the 'Simulation setup' editor did not highlight which simulation contained the error.
Collection System and Rivers Catchments were exported in two duplicate layers during the export to ArcGIS Pro using the tool 'ArcGIS integration'.
Collection System and Rivers An unexpected validation error was sometimes reported in the 'Curves and relations' editor for a 'Control rule time series' curve.
Rivers When trying to create a cross section plot in results viewing mode (without a project database opened) with multiple .res1d result files loaded, an unexpected error message about a missing 2D domain file was returned, preventing from creating the plot without opening a database.
Rivers When including a '2D map' result file, the simulation sometimes stopped during initialisation with an error saying that the 2D map result file from a previous simulation was still in use.
Rivers Bed roughness values of 0 were not reported as an error when using the 'Multiple zones' distribution.
Rivers When comparing results only on a selection of rivers, the 'Results differences' tool reported differences only from parts of the rivers (from their start chainage down to the intersection with the first tributary).
Rivers The 'Discharge through section' tool stopped with an unexpected error when the cross section was crossing rivers or pipes where discharge results were locally not saved.
MIKE 1D engine Fixed error occurring when applying a limiting cross-section when using the energy equation method in a dambreak simulation (TT66320).
MIKE 1D engine Fixed bug related to generation of water at collection system locations with bottom level discontinuities (TT66175).
MIKE 1D engine Added warning message informing users that cross section marker locations must increase monotonically in the x direction from left to right (TT65910).
MIKE 1D engine Corrected error in interpretation of time series wind direction inputs (TT66234).
MIKE 1D engine Fixed units error in interpretation of time series valve opening inputs (TT60127).
MIKE 1D engine Fixed error in Muskingum-Cunge routing (TT66117).
MIKE 1D engine Fixed bug creating water balance errors at structure link connections (TT66163).
MIKE 1D engine Fixed sign error in application of gridded evaporation to river network (TT66365).
MIKE 1D engine Fixed indexing error occurring when setting initial conditions for a setup with routing reaches (TT66340).
MIKE 1D engine Corrected unclear warning message occurring when head loss table incomplete (TT66339).
MIKE 1D engine Fixed error in accounting of contributions from spilling nodes in .html summary (TT65052).
MIKE 1D engine Fixed error preventing use of Data Assimilation module in collection systems without a river license (TT66147).
2D overland The 'Discharge through section' tool has been improved to better report the computation progress, to allow deleting multiple sections at once, and to save output time series one at a time.
2D overland An error "Shapefile is invalid" was returned when trying to execute the 'Create flood map polygons' tool with an invalid time step containing only dry elements. This is now reported with a clear error during the time step selection.
2D overland The 'Exclude rivers' tool sometimes stopped with an unexpected error "Operation does not support Geometry Collection arguments".
2D overland An error was sometimes reported in the 'Result files' editor for MIKE ECO Lab results, even when the MIKE ECO Lab module was not active.
2D overland During generation of flexible meshes based on shape file layers, mesh arcs created within a polygon from the shape file were ignored, i.e. the resulting element faces did not align with the arcs.
2D overland In some cases, MIKE+ stopped working after applying a polygon feature layer as inactive area, for the generation of a 2D domain with a rectangular grid.
2D overland The error message has been improved in the '2D infrastructures' editor, when the selected feature layer doesn't include any valid field to identify the zones.
2D overland The 'Validate' button in the 'Simulation setup' editor is only used to validate collection system and river network data, and has been disabled for standalone 2D simulations to avoid the unclear error message obtained with that simulation type.
2D overland The 'Insert' button in the '2D boundary conditions' editor failed to create an open boundary condition on the map, when using a 'Rectangular grid' as 2D domain.
2D overland When plotting vectors from a .dfs2 result file on the map, vectors were always shown in all cells even when selecting the style 'Interpolated on structure grid'.
2D overland When using the 2D infiltration type 'Varying in domain using capacity' with the source type 'MIKE+ 2D infiltration layer', the infiltration parameters were not correctly used in the simulation.
2D overland When running simulations from the 'Batch simulation' editor on computers with multiple GPUs, only the first simulation of the batch used the GPU selected in the 'Parallelisation settings' window, whereas subsequent simulations always used the first one.
SWMM Validations of data in the 'Ground water' editor have been added.
SWMM In the 'Nodes' editor, a new data validation has been added to check that Invert level is below Ground level.
SWMM The 'View log' and 'View summary' buttons failed to open corresponding files for simulations involving the 2D overland module.
SWMM The 'Surcharge depth' value from storage unit nodes was wrongly imported from .inp files.
SWMM The 'Element status' field is now available and editable from the overview grid in the 'Conduits' editor.
Water Distribution The data validation reporting an error about inconsistency between measured and computed item units in the 'Plots and statistics' editor has been relaxed, to accept additional valid units in the measured time series.
Water Distribution MIKE+ sometimes stopped working with an unexpected error message after attempting to display a tank head time series using the tool 'TS from map'.
Water Distribution Bulk-editing the 'Is active' status for pipes using the Field Calculator failed to update the 'Is active' status for connected junctions accordingly.
Water Distribution Unexpected straight lines were sometimes added to the map for water hammer link results layers.
Water Distribution The filter 'Item can only connect if' did not work as expected when connecting demand allocations with the 'Connection tool'.
Water Distribution An unexpected error occurred when exporting the pipes layer to shape file from the 'Layers and symbols' tree, if some pipes fields contained empty values.
Water Distribution Special characters in rule IDs were not properly imported from EPANET .inp file.
Water Distribution Controls' clocktimes were not properly imported from EPANET .inp file when defining a non-integer number of hours.
Water Distribution Rules defined with a non-unique ID in EPANET .inp file were skipped during the import in MIKE+. They are now renamed with a new unique ID.
Water Distribution Import of water demands from EPANET .inp file was sometimes wrong when demands were defined in both [JUNCTIONS] and [DEMANDS] sections in the .inp file.