Resolved Issues

2D Bridges that were fully contained within one cell give bad results.  The computation engine expects the bridge to lie on a cell face (bordered by at least two cells).  An error message has been added and the computation engine and computations will stop.

Large 1D datasets would save slowly in RAS Mapper when stopping Editing. This was due to the computation of the cross section Edgelines layer.

Deleting cross section in RAS Mapper after deleting the river reach resulted in the software unable to delete and an error message would show. 

Models with thousands of cross sections was slow to load when comparing Geometry.  Comparison performance has been greatly improved.

Stop Editing (resulting in a file Save operation) in RAS Mapper will cause all lateral structures to change their LW HW Position and their LW TW Position value to LeftOverbank.  

6.7 Beta 4 shows an incorrect headloss computation through 2D Connections modeled as a Bridge (1D Family of Rating Curves).  The method for now correctly applies headloss to just the faces under the bridge deck.

The wave fill method for creating the Encroached Terrain (Terrain.Encr) would create large changes ("blocky" Terrain) in Terrain elevations.  Often this is due to a higher water surface upstream (acceptable) propagating to downstream areas. However, sometimes the poor terrain resulted from an unsuccessful wave fill attempt to create continuous watershed drainage (intended for rain on mesh models).

Observed Stage data for Reference Points were not plotting. 

There is a limit of 900 Junction nodes that have 3 or more conduit connections of. If this limit is exceeded, a fortran error would prevent the compute from completing. 

The Max Profile for metric pipe datasets showed incorrect values (well below the pipe invert) for the HGL.

Under high surface head, the hydraulic conditions can be outside the extent of the Drop Inlet rating curves causing extrapolation and bad HGLs in the connected pipes. This was resolved by computing flows on the fly when hydraulic conditions are outside the range of the pre-computed curves. 

Pumps that were drawing water from nodes in pipe networks were still producing water when the node was dry (provided that the pump was still on) and causing volume errors. 

USGS requests for "all" data were failing with the previous request string which joins requests for each individual data source/resolution.  The new request string for "all" data (a null request) successfully retrieves a list of terrain data.  Additionally, a filter has been added to request specific data resolutions.  NOTE: requests of 1, 2 or all data works, while requests with 3 or more do not.

Large volume accounting errors are being computed for models where a 2D cell shares both an internal boundary condition and culvert. The computation results (flow and stage hydrograph) are correct. 

If a HEC-RAS model has multiple 2D flow areas with 2D bridges, it's possible for the mapping of bridges to 2D flow areas to be incorrect leading to unstable models. When the issue occurs it is very obvious because the model becomes unstable at the 2D bridges. 

An issue with duplicate entries in Pipe Network property tables at junction nodes is causing the computations to suddenly go unstable and abort with the message: 'Pipe Flow solution went unstable in system:...'. This issue most often occurs in flat systems with large conduit cell sizes and small junction Base Areas. 

When Pipe Network geometries have multiple System defined they are connecting the surface geometry at incorrect locations due to an indexing error. 

The 2D sediment concentration was showing artificial changes due to small water volume errors in the 2D surface flow model. This is a known issue in transport models and a simple water volume correction can be computed to preserve the sediment concentration. The volume correction was accidentally turned off in the transport model. This is only an issue around wetting and drying for tracer type studies. For most 2D sediment models, the sediment erosion and deposition terms are dominant and the small errors due to water volume errors do not affect the results significantly. 

If multiple Initial Conditions Points are specified, but only some of the points are "fixed" to a stage during warmup, users may get an access violation crash during simulation.

Animation of Gated Structures is not updating within the RAS Mapper plots.

For Lateral Structures using the Normal 2D Equation computation, if the WSE in the 1D river is below the lateral structure, there would be no flow (at a given face) even when the WSE was high enough in the 2D that there should be flow leaving the 2D area and entering the river.

The 2D Bridge (1D Family of Rating Curves) was not correctly checking/using values for the unsubmerged free flow rating curve. For situations where the flow/tailwater was was such that it should be using the free flow curve, or the tailwater was below the first submerged curve, it may have been producing a bad result. 

An issue arises when Pipe Network nodes that are Culvert Openings are connected to the same 2D cell as SA/2D connection. For example, if a culvert in an SA/2D connection shares a 2D cell with a  Pipe Network Culvert Opening node, the boundary conditions to that cell will not be applied correctly. 

Floodway encroachments are broken in BETA 2.  Floodway encroachments do not get copied to the Terrain Modifications for the Encroached Terrain. 

When a 2D mesh is created, recomputing the mesh has an "unknown error" on the bottom left.  The Mesh Status on the 2D Area Editor reports an arithmetic overflow message.   

The simplified channel evolution model (used for eroding reservoir sediments for dam removals, dam failures, and flushing) is not working in version 6.6. 

The USGS decommissioned the water quality data that HEC uses for this tool.  Users can no longer download data from the USGS.  If you have the gage number, you can now download data for the gage site.

The polygons for the perimeters of 2D areas are disappearing in unique cases. Symptoms you might notice are that the mesh does not update when adding new points in an edit session, the polygon is not selectable in Mapper, or simulations failing during Writing Geometry stage. 

Model Compare tool may crash when comparing older results. Various other small issues.

Newly created meshes reporting "Unknown Error" until an editing session is stopped and saved. 

When deleting old Plans (#.p02, for example), model results for the currently open in the interface Plan (#.p01.hdf, for example) will be deleted along with #.p02 (#.p02.hdf will not be deleted).  

SA/2D Connection Data plot in RAS Mapper crashing if there were gates 

Copy and paste in RAS Mapper not now pastes profile (station-elevation data) columns

Deleting all pipe nodes in a geometry would result in software crash