Known Issues
Below is a list of current known issues for Hexagon GeoCloud and their workarounds, where available.
Scale values below 1 cannot be entered directly in scene editor
When setting a scale lower than 1 on a node in the scene editor, the input field validates each keystroke and may reject values that begin with 0 (for example 0.001 for millimeter scaling). Workaround: use the scale controls, or drag the text field to set the value, instead of typing it.
“Invite members” button does not work for accounts with SSO
Customers whose company account is configured with Single Sign-On (SSO) cannot invite users via the “Invite members” button on the User page (https://hxdr.app/account/users). Workaround: contact support to invite users to SSO-configured accounts.
GeoTag image filenames have duplicated extensions after LGSx import
When an LGSx file is imported, image files attached to the included GeoTags end up with their file extension duplicated in the name. An image originally named filename.jpg appears in Reality Cloud Studio as filename.jpg.jpg.
Desktop Sync application can be launched twice with “Run as administrator”
It is possible to have two instances of Hexagon GeoCloud Desktop Sync open on the same PC at the same time when one is started normally and another with “Run as administrator”. This does not affect functionality. Workaround: close one of the instances.
Category name is empty after copying GeoTags across projects
When GeoTags are copied from an asset in another project and the GeoTag’s category does not yet exist in the destination project, the Category name field is not initially populated in the category detail view.
Deviation inspection followed by point cloud classification will remove point cloud from the inspection scene
After running a point cloud classification on a point cloud that is already part of an inspection scene - the point cloud will be removed from the inspection scene, making inspection unusable. Additionally, “Inspections” tab in the scene will be disabled.
Alignment of assets with UCS might fail
Workaround: upload the data without UCS when used for alignment.
Inspection results may show inconsistent color mapping with grey patches
In some examples with full point cloud coverage - some parts of the model are grey as if no points are present. Resolution:
Update to Cyclone REGISTER 360 PLUS to 2025.0.0 or newer before exporting to LGSx.
If using an older version of Cyclone REGISTER 360 PLUS is required, it is recommended to not decimate the data before exporting to LGSx.
Auto Align, Scene Registration and Deviation analysis might fail when original Assets are stored in different HxDR data centers (regions).
If a customer uploads a point cloud asset to a project in Region EU-1 and a BIM file to a project in Region NA-1, then “copies” the model to the Region EU-1 project. Smart/Auto-Align and Deviation Analysis will not work.
Model names not available with CloudWorx
Visualization of model names used for Point Cloud Classification on GeoCloud in CloudWorx for AutoCAD, CloudWorx for BricsCAD, CloudWorx for Navisworks, CloudWorx for Revit, and CloudWorx Viewer for Revit is not available.
Some data sets fail to process completely Point Cloud Classification
This is the result of one or a combination of the following:
High Density of the Point Cloud.
High number of Classes in the chosen "Model".
The Class Models with the most classes are Indoor Construction, Rail, and Road.
High density point clouds together with one of these three Classification Models is likely to result in the failure.