Build a complete EPANET model in the app - Draw pipes the way you sketch them: with the Pipe tool, each click on empty space adds a new junction and continues from it, and a right-click adds a bend (vertex). Length follows the drawn path in the network's units, and each pipe is one undo step. - Network ▸ Network Options… sets flow units (all values are converted, so the network stays the same), the head loss formula and the simulation times. - Tanks can have a volume curve, and GPV and PCV valves their curve, chosen or created from the inspector. Analysis ▸ Curves… now lists every curve, and a curve still used by a tank or valve cannot be deleted. - Network ▸ Controls… creates and edits simple controls and rule-based controls, checked the same way EPANET checks them. The inspector shows the controls of the selected element. Network QA - Network ▸ Network QA opens a panel under the map that checks the model and, after a run, its results: a color for each part of the network (network, junctions, tanks and reservoirs, pipes, pumps, valves, patterns and curves, simulation) and the cause of each finding. Click a finding to select its element on the map. It only points things out; it never changes the network. - Network ▸ Export QA Report… saves the same findings as a PDF. Closer to EPANET - Fix: in version 1.3, saving a network whose valves or pumps came before its pipes in the file could change the simulation results. Saving now keeps the order of the file, and the words you did not edit (status, speed, overflow). - IDs with accents or ñ in older (Latin-1) files now get their results, including in Water Loss. An element the engine cannot find is reported instead of showing 0. - Numbers are saved with full precision, so a saved file reads back to the same values, without extra digits after converting units or creating a curve. - Files are read the way EPANET reads them: long lines, IDs in quotes (an ID with a space is saved in quotes), controls on elements with names like "Tank", and abbreviated keywords. - Some damaged or unusual files that could close the app now open with a clear error. - When a file asks for a time-averaged report, the simulation report says so; FlowAnalyzer still shows every time step. Other fixes - File ▸ Open… now always asks before discarding unsaved changes, and opening another network clears the selection and the inspector. - The File ▸ Export to .inp… sheet uses its full width again.

Demands, charts and results - Junctions can have several demands, each with its own base value, pattern and category, read and saved the way EPANET does. - Curve and pattern editors now show a chart, and the inspector shows the time series of the selected element (pressure, tank level or flow). - Create a pump curve straight from the inspector with New… next to Head Curve. - New Valves tab in Results, and exported CSV files now say which network and simulation they come from. - Results use the reporting times of your file, including a report start time other than 0:00. Finding your way - View ▸ Find Element… (⌘F) centers and selects a junction or link by its ID. - When part of the network is cut off from every source, the engine warning names the affected junctions and the map circles them in red. - Parallel links between the same two junctions are drawn apart, and clicking picks the nearest one. - A pattern still used by a junction, a pump, energy or sources cannot be deleted by mistake. Water Loss - The calibration now takes every demand category into account. Calibrations saved with an earlier version for networks that define demands in a [DEMANDS] section will show as out of date the first time you open them. Run the calibration again to update them. About - About FlowAnalyzer now includes the license of the EPANET engine (MIT).

Work on many elements at once - Select several elements with Shift- or Command-click, or drag a rectangle with Shift. Press Esc to clear the selection. - Edit them together: demand and pattern for junctions, diameter and roughness for pipes, in a single step you can undo. - Delete several elements at once, with a notice of what else is affected. Projects - Open and save FlowAnalyzer project files (.json), the same format FlowAnalyzer Web uses. Inspector and map - Junctions show the base demand from the file separately from the demand calculated at the selected time. - Before you run a simulation, results show "–" instead of zeros. - When you color the map by a pipe property, junctions keep their own colors and the legend says what is colored. - Curve and pattern editors are easier to read. Water Loss - On networks that cannot be calibrated, the calibration stops sooner and tells you why. - Each pipe shows its modeled leakage and its share of the total, when the calibration is reliable. Engine - Pressures, flows, tank levels and units are now tested against the EPANET engine on a wide set of networks. Help - Help ▸ Video Tutorials opens the video tutorials in your language (English or Spanish).

Edit and save your networks - Save: write your network back to an EPANET .inp file. Before saving, the app tells you what will not be kept from the original file (such as comments and section order). - New Network: start an empty network from scratch. - Network Browser: browse your network files and open one with a double-click or the Open button. - The last network you worked on reopens when you launch the app. - Edit in the inspector: pipes, tanks, reservoirs, pumps and junction demand patterns. - Delete elements with a notice of what else is affected, and undo it. - Units: SI options including pressure in bar and kPa. Water Loss - Clearer warnings: when a result is not reliable, the app says so instead of showing a figure. Engine - Fix for tank mass balance in the EPANET engine, so tanks no longer gain or lose water they should not. - Results are shown as the engine computes them; the app no longer replaces values it considered invalid.