update – Trimble Business Center v3.01 or v3.10

Depending where you look there is an update for Business Center HCE v3.

Here are the release notes:

Business Center – HCE Patch v3.01
Warning: This version, and v3.00 before it, are not supported on Windows XP – Some components in Business Center – HCE require Microsoft® .NET Framework 4.5, which is not supported by the Windows XP operating system. To run this version of Business Center – HCE, you must use a later operating system.
Select this to download program files that include these enhancements:
· Make a multi-segment surface slice – In the Surface Slicer View, you can now hold [Control] or [Shift] to draw a polyline as the slicing line; this enables you to see a multi-linear cross-section of one or more surface in the view.
· Skip the hole check on LandXML import – When you import a surface in a LandXML file (.xml), you can now disable the check for holes in the surface (this should only be done when you know that the surface does not contain holes). In the Import pane, selecting No in the Check for holes setting makes importing faster. If the surface has holes, but no check is done, surface triangles are formed across the hole outside the surface edge breakline.
· Export surface slope arrows – Slope arrows shown on surface triangles are now included when you export a surface to a CAD file (.dxf) (if the arrows are set to visible for the surface).
· Use 3D lines as drill hole vectors – You can now create drill holes from single-segment 3D lines and linestrings when you add drill holes to a Manual drill plan. This enables you to create drill holes from lines imported from other software applications that export drill plans as DXF files.
· Drill Hole Quality Report headings – When you output a Drill Hole Quality Report to Microsoft Excel, the first row and column on the Data tab are now frozen so that the headings stay visible when you scroll the report horizontally or vertically.
· Import fill boundaries from vector PDF – A new option has been added to the
Import Vector PDF Data command:
· Include fill boundaries – Check this box to include fill linework as part of the imported vector data. Fill objects are listed as “PDF Fill…” under Layers in the View Filter Manager.
And bug fixes for cases in which:
· An exception was encountered when entering a coordinate when creating or editing a linestring, while running Microsoft Windows 8 or 8.1, with the operating system’s regional settings for a decimal set to use a comma.
(Control Panel > Region > Additional settings > Numbers tab > Decimal symbol = , )
· An exception (Arithmetic operation resulted in an overflow.) was encountered when importing a PDF file while running the program on a Windows 8 or 8.1 operating system.
· An exception (Object reference not set to an instance of an object.) was encountered after you deleted a linestring while using a snap command to add a VPI.
· An exception (Serial number 1153 is not in the concordance.) was encountered when you deleted a linestring after selecting it in the Offset Line snap command.
· An exception (No actual segment correspond to the given element index. Breaking the Linestring at this element is not supported yet.) was encountered when deleting a linestring segment that uses a PI-based arc.
· An exception was encountered when using the Along Line Snap to extract an elevation from a draped line.
· An image that is draped on a surface was not refreshing properly when the project file was reopened.
· The Mass Haul Diagram did not display properly when the vertical alignment was shorter than the horizontal alignment.
· When digitizing contour lines, the contours did not close even though the digitized line end points were within tolerance (and the box to close the contours was checked).
· When imported, CLIP vertical alignments files (.alz) that include an “F” curve option were off by a factor of 100.
· A linestring with interpolated segment end point elevations had those elevations set to zero when the linestring was exported to a CAD file (.dwg).
· When editing a linestring’s vertical component, the Line Intersection method of placing a VPI did not work when the intersection was in 3D/the lines did not physically intersect.
· In the Alignment Geometry Report, an invalid tangent was being reported when an arc’s delta was greater than 179 ̊.
· In the Identify Site Takeoff command, some valid closed regions were not identified as such.
· In the Takeoff Report, earthen material volumes were inaccurate (excessively long/15 digits) in German installations.
· When creating a corridor drill plan, drill holes were not added in shallow areas of fill that should have been handled by “max distance above rock” setting (to account for potential inaccuracies in the shape of the rock surface).
· When creating a corridor drill plan, split hole were created where the tie slope was too shallow.
· When creating a drill plan based on a reference line, blast holes that were not on the centerline had an incorrect orientation.
· When creating various types of drill plans, split holes were not using the ‘Maximum distance above rock’ tolerance.
· When creating a boundary drill plan, split hole numbering was skipping some holes. The drill plan now properly checks split hole lines that cross a boundary with arcs.
· In the Drill Hole Quality Report, the station and offset columns were in an illogical place; now they are next to easting, northing, elevation.
Additional changes:
· The definition for a Boring log discovery tolerance has changed: Specify the distance within which boring logs will be grouped and used to calculate strata at a preceding station. To determine strata for a particular station, the next upstation boring log is found. Any subsequent upstation boring log that is within the discovery tolerance is added to the group of preceding, grouped boring logs to calculate/interpolate the strata for the aforementioned station.