| Issue | |
|---|
Import Shapefile to Line Modification Unhandled Exception
| When importing polylines from shapefile to the Line Terrain Modification, the features were not properly saved. Therefore, if you attempted to immediately edit the line, an "Unhandled Exception" error message was shown. |
Missing Individual Gate Group Flow and Opening Line Series in Hydrograph Plot
| Normally you could plot an individual gate group's flow and opening in the Hydrograph plotter by selecting the appropriate gate group in Options → Variables. However in 6.6 the individual gate groups did not appear in this list. |
Hydraulic Property Table Plot Crashes
| Normally pressing the hydraulic property table plot button on the main HEC-RAS window will show a cross section plot along with conveyance and area property tables. In 6.6, if the current plan's geometry did not have a terrain associated with it, the hydraulic property table plot button will not work. |
Classification Polygons Disappearing After Doing "Generate New Classification Layer"
| The "Generate New Classification Layer" tool takes an existing classification layer, such as a landcover layer, and makes a new classification layer, with options to clip, change cell size, and rasterize classifications polygons. Users who do not rasterize classification polygons will have the polygons from the source classification layer brought over to the new classification layer. The classifications polygons in the new layer were disappearing after closing and re-opening RAS Mapper. |
Importing Mesh Takes Too Long
| Sometimes it may took longer than expected to import a mesh using the Import Mesh feature introduced in version 6.6. For reference, 500,000 cell mesh should take about 2-3 seconds to import. |
Cannot Import Meshes from Results/Older Versions of HEC-RAS
| Trying to import a mesh using the Import Mesh feature introduced in version 6.6 did not work with plan results files, and older geometry files. Older geometry files did not work because they were mistakenly labeled as HEC-RAS Results for the file type attribute on the root of the file. |
| Pipe Networks (beta) - External and Culvert Openings must have 0 Base Area | A bug was found in the creation of property tables for External and Culvert Opening node types that have non-zero Base Area. This caused pipe networks to go unstable at the start of the simulation. |
| Pipe Networks (beta) - Downstream nodes with multiple upstream and 0 downstream conduits | A downstream pipe node that had multiple conduits entering and none leaving caused an error preventing the simulation from starting. |
| Pipe Networks (beta) - Drop Inlets were interfering with 2D Internal Boundary Condition Flows | When a pipe network Drop Inlet was connected to the same 2D cell as an Internal 2D Boundary Condition Line, flows entering the cell from the boundary condition were negated. |
| Pipe Networks (beta) - Error in Drop Inlet Inflow Calculations | Drop Inlet inflow calculations (weir and orifice flow) were being calculated incorrectly allowing too much water to enter the pipe network. |
| Pipe Networks (beta) - In some instances drop inlet calculations were allowing flow into the system before surface water arrives. | A bug in in the drop inlet calculations is, in some circumstances, was allowing small amounts of flow into the system prior to the surface water head exceeding the drop inlet elevation. |
| Pipe Networks (beta) don't work with models in metric units | When using pipe networks in metric unit models, surface connection elevations were incorrect causing bad results in the model. |