BC – HCE v 3.61 – update

BC-HCE 3.61
Select this to download program files that include these enhancements:
§ The Surface Elevation column in the Points to Surface Results report no longer displays a unit of measurement following the measurement value. The report can now be copied to Microsoft Excel and the column can be used for calculations since it contains only numerical values, not text.
§ Surfaces can now be added as members to use in the formation of another surface.
· Several changes were made to the default settings of newly created surfaces when they contain point cloud data or when the number of surface members exceeds 100,000. These changes were made to improve the display performance and how the surfaces are visualized.
o Transparency 20 (You may want to adjust this on a project by project need)
o Face displacement 1
o Shading By surface color
All other display properties are turned off. If an image has been added as a surface member the Shading property of “By surface color” will display the image draped on the surface. The transparency setting of 20 will enable you to see through one surface to another.
· When creating a surface, you can now specify the color of the surface and the date the surface was measured.
· When an isopach is created the default properties for its display are turned off in order to improve the display performance. You can select the isopach in the Project Explorer and turn on the desired display properties.
· When a cut/fill map is created, the default properties have been changed to improve the display performance and to enable the transparency of the surface. The Drape property is now automatically enabled so that the surface is draped onto the Final surface. This change along with the changes made for large data sets will establish the desired properties so that a Final surface with a draped image with lightly shaded cut fill colors will be displayed.
· In order to improve the performance of volume computations, go to Project Settings > Computations > Surface > General and set the optimum Volume computation option. When computing the difference between point cloud type data select the “Track Finish Breaklines” option to minimize the amount of data and achieve faster results. The default setting of “Track All Triangles” assures that the shape of both surfaces is fully used and computes the most precise results. This option also takes the longest time and creates the most data.
· You can now export BC-HCE surfaces into industry standard formats, such as .obj and .ply files using the Capture 3D command, so that they can be imported into your CAD systems.
§ It now requires fewer actions to create new layers from the Layer combo-box within a command.
§ The UAS processing engine used for aerial photogrammetry provides faster computations and increased accuracy when generating point clouds that are more homogeneous and better represent the terrain.
§ The Map GIS Metadata command within the GIS Module now allows you to map project metadata associated with RTK vectors and total station observations to the GIS database fields so that metadata can be uploaded to the GIS databases when you upload (write) features. The command has been enhanced to allow you to map a single project property (for example, a point ID or an elevation) to multiple GIS fields or to all fields with the same name simultaneously, streamlining the mapping workflow and reducing the chance of error.
§ The Merge survey projects command has been improved to handle challenging projects more robustly.
§ You can now import files with Federal Desktop Core Configuration (FDCC) group policies applied, these are mandatory configuration settings for laptop and desktop computers owned by the United States government.
And bug fixes for cases in which:
§ Material volumes exported to TILOS included individual materials and unusable materials, when they should have only included total usable material.
§ Parts of the 3D View Settings command pane were hidden when running at 120+ DPI.
§ Intersection points were unnecessarily computed on large surfaces when the volume computation option was set to Track Finish Breaklines (Project Settings > Computations > Surface > Volume computations).
§ The Controller Manager could not access the data synchronization area/Trimble Synchronizer Data Folder.
§ Hatch patterns drew very slowly to the extent that the program appeared to have ‘frozen’ when importing them.
§ The date and time formats on the first and last pages of the Project Scan Refinement Report were inconsistent.
§ The selected menu in the Plan View became very big when you multi-selected many objects with the mouse.
§ Unchecking the Display label horizontally box in the Create Leader Line command disabled the text rotation.
§ As-built piles imported very slowly.
§ MTA residual calculations performed and reported in did not match the results as the MTA calculations performed and reported in Trimble Access.
§ You could not measure the distance between two imported GNSS points without becoming unresponsive.
§ Google Earth panorama files created from photo stations did not display correctly in Google Earth.
§ The program ran very slowly when you imported a file or deleted certain objects (e.g., a surface tie or conditional instructions) with the Corridor Template View open.
§ Parts of the Place Image command pane were hidden when running at 120+ DPI.
§ A GDI exception occurred while using the Layer Manager command.
§ A library error occurred when exporting text and lines to .dwg format.
§ Roundoff errors occurred while using alignment based surface with boundaries since the surface was built with rounded values of only the station/offset calculations. Now the surface is built with the rounded values for the boundary as well.
§ An error occurred when unchecking a compaction target box in the Edit Lifts dialog, causing all of the checkboxes to disappear.
§ An exception occurred while importing a .dwg file.
§ An exception occurred while printing some reports on A4 paper.
§ An exception occurred when running the Fillet/Chamfer command.
§ An exception occurred when using the station slider in the Corridor Template View after deleting an instruction.
§ An exception occurred while generating the Surface Information Report for a corridor surface.
§ An exception occurred when using the Detailed Cell Data Viewer.
§ An exception occurred in the Edit Linestring command when changing Segment type to Backsight deflection.
Known issue:
§ You cannot check in detachable HASP license early – A HASP network key can be configured to allow users to check out a “detachable” instance of the multi-user license for a limited period of time, allowing the user to run the software without being connected to the network. In earlier versions, a detachable license could be checked back in (canceled) early, prior to the expiration date and time, making it available for other users. However, at this time, a detachable license cannot be checked in early (a system-time error message is displayed) and is checked in only on the expiration date and time. Then it is available for use by other users. Because of this known issue, we recommend that you set the duration to a minimum amount of time.