Release Notes | Cyclone REGISTER 360

Archive

What’s New

The 2025.0.1 version is a minor release of Cyclone REGISTER 360 PLUS that introduces a new option for B&W target extraction, along with a range of general bug fixes.

Important: Starting with version 2025.0.0, Administrator privileges are required for installing Cyclone REGISTER 360 PLUS and Cyclone REGISTER 360 PLUS (BLK Edition) to meet new security requirements.

Support for Configurable B&W Target Diameter in Links Settings

The Links settings now include a new option for specifying the B&W target diameter. It allows users to define the diameter of B&W targets that have to be extracted.

Bug Fixes

• Fixed an issue where, after merging two projects, cleaning the merged point cloud was not possible.

• Fixed an issue where panoramic images were missing from structured E57 files after exporting structured data using a standard Cyclone REGISTER 360 PLUS license.

• Fixed several issues with RCP (Setup) exports where panoramic images were either missing or displayed in low resolution after being reimported into Cyclone REGISTER 360 PLUS or opened in ReCap.

• Fixed an issue where cloud points were not displayed in the SiteMap and Bundle Cloud views after exporting data in the E57 format with enabled Export structured E57 in compatibility format and For ReCap export options and importing the resulting file in a new project.

• Fixed an issue where Setups from the same scanner project were not imported into the same Cyclone REGISTER 360 PLUS project during the second import session. Now, additional Setups can be seamlessly added to the existing SiteMap in a subsequent import session.

• Fixed an issue that prevented manual extraction of targets after importing a dataset without enabling the Auto B&W Target registration option.

• Fixed an issue where Control points were imported with the units set in General settings instead of the units selected specifically under the Control points by rule option. Now, when importing Control points by rule, the selected units correctly take priority over those defined in General settings.

• Fixed an issue with incorrect length values when importing Control points by default or by rule in US Survey feet.

• Fixed an issue where exporting point clouds to LGSx or LAS did not support US Survey feet and used International feet regardless of the selected length unit. Now, LGSx and LAS exports correctly reflect the chosen unit, supporting both International feet and US Survey feet as expected.

• Fixed an issue with the Cyclone REGISTER 360 PLUS installer that prevented Cyclone REGISTER 360 PLUS from launching after installation.

• Fixed an issue where the default Cloud-to-Cloud generation radius for structured data was set incorrectly after upgrading to version 2025.0.0 or when using several software versions on the same computer. Now, the default values for the Setup Cloud-to-Cloud generation radius and WayPoint Cloud-to-Cloud generation radius settings are configured properly to ensure stable link generation and updates.

• Fixed an issue where some tags attached to BLKG2 data were not imported into Cyclone REGISTER 360 PLUS after being downloaded via BLK Manager.

• Fixed an issue where GNSS coordinates embedded in BLK360 data were missing when downloading the dataset via BLK Data Manager and then importing it into Cyclone REGISTER 360 PLUS.

• Fixed an issue where image assets were missing after importing BLK360 data into Cyclone REGISTER 360 PLUS directly from the scanner.

• Fixed an issue that prevented the import of text GeoTags into Cyclone REGISTER 360 PLUS after importing BLK360 data downloaded from BLK Data Manager.

• Fixed an issue that prevented GeoTags with file assets from being positioned correctly when importing BLK2GO data into Cyclone REGISTER 360 PLUS either directly from the scanner or by importing downloaded data from BLK Data Manager.

• Fixed an issue that caused GeoTags with video and audio assets to be imported with a file size of 0 KB after importing BLK360 data into Cyclone REGISTER 360 PLUS directly from the scanner.

Known Issues

General Issues

• Some new dialogs will not have translations.

• F1 contextual help will not work with the Microsoft Edge browser as the default browser. The workaround is to set Chrome or Firefox as the default browser.

• Non-ASCII characters are not allowed in the following conditions:

  • Import temp path

  • On computers with non-Latin user names. The user will not be able to create any project if the source data is stored anywhere under the user profile name. This issue will manifest itself in Japanese, Chinese, or any other language containing special non-Latin characters in the user name.

  • The SiteMap name cannot have non-Latin (Japanese, Chinese, etc.) characters for publishing to TruView Enterprise or TruView Cloud.

•  Japanese OS language preference is not selected by default and causes issues with some Cyclone REGISTER 360 PLUS imports. The user can fix this by manually selecting the language within preferences:

  • On the Japanese OS machine, launch the Control Panel.

  • Select the region (地域) and click the Accept button.

  • Select the Use Unicode UTF-8 for worldwide language support check box.

  • Reboot.

Screen Resolution Issues

• Cyclone REGISTER 360 PLUS does not support display resolutions beyond 4K.

• The Project & Storage dialog in Cyclone REGISTER 360 2024.0.2 may not fully fit certain screen resolutions. As a workaround, use the highest resolution available on your display and set the taskbar to auto-hide.

Scaling Issues

• Windows scaling works best when set to 100%. Setting it to 150% or higher causes some graphical errors.

• In some cases, Setup icons are misplaced when data is published to TruView Cloud. The workaround is to set Windows scaling to 100% as there seems to be an issue when set to 150%.

• Some dialog boxes cannot be rescaled correctly and the OK button is not shown in the dialog box.

• Scaling of 175% and 200% collapses the left side panel and cannot resize after collapse.

• If experiencing problems with multiple monitors using Windows scaling higher than 100%, set the monitor running Cyclone REGISTER 360 PLUS as the main display.

• Some panels have a dialog that does not fit correctly.

Graphics Card Issues

• Cyclone REGISTER 360 PLUS will not detect the dedicated graphics card on computers with multiple graphics cards. Users must manually set the dedicated card for use with Cyclone REGISTER 360. This is done with the Nvidia Control Panel for Nvidia graphics cards, or with the ‘Catalyst Control Centre’ for ATI/AMD graphic cards.

• Some graphic card anomalies can be caused by power management software. Please turn it off by setting the power management profile to High Performance.

Data Storage and Memory Issues

• Cyclone REGISTER 360 PLUS projects located on NAS drives are NOT recommended.

• Cyclone REGISTER 360 PLUS projects located on NAS drives show <1MB on the Projects & Storage tab.

• If memory issues arise, check that the virtual memory size is set to the same size as RAM.

• 30 GB of temp space is needed for every billion points exported to a single RCP cloud.

• Using Export to Separate Setups does not use the same level of temp space. Temp space is not generally a problem when exporting separate Setups.

• Files written to the temp folder at C:\Users\(user name)\AppData\Local\Temp\Register360, will be deleted after the program closes. These files will NOT be deleted if the program freezes or crashes.

• The currently active project should not be re-named from the Projects & Storage settings. Close the project before renaming it.

• The use of LGSx files is only supported when the files are saved locally. Due to variations between network deployments, LGSx files may be unreliable when published to a network location.

Compatibility Issues

• Mac OS’s running Windows Boot Camp is not officially supported. Cyclone REGISTER 360 PLUS supports Windows 11 on Windows-native devices only.

• Virtual Machine (VM) environments are not supported.

• Importing data over a network can cause issues, especially on Windows 10. The workaround is to copy the scan data to a local disk.

• Some customers have reported Cyclone REGISTER 360 PLUS stops running when using AMD Ryzen 7 processors.

• Due to variations between network deployments, Cyclone REGISTER 360 PLUS projects may be unreliable or slow to respond when accessed from a network location.

• Remote Desktop is only supported if Cyclone REGISTER 360 PLUS is opened in the remote computer first. Trying to open Cyclone REGISTER 360 PLUS through a remote desktop is not supported.

• LGS files from Pegasus OFFICE are not supported. Pegasus OFFICE was updated along with TruView and CloudWorx products to support the special LGS file that is produced by Pegasus OFFICE. The LGS file includes a trajectory, new image WayPoints positions, and image set rendering. These objects are not supported yet in Cyclone REGISTER 360 PLUS or Cyclone CORE. Cyclone CORE can import just the point cloud, but the depth maps, special images, trajectory, and new icons are not included.

• FARO no longer shares the required SDK to support the import of FARO raw scanner files from the newest FARO Scanners. The workaround is to import into FARO Scene and export an FLS or E57 file.

CLM Issues

• When using a standalone CLM installer, some EnterpriseElite users may find that the usage file (year-month.db) normally located at C:\Leica Geosystems\CLM\LogFiles does not get produced. Please ensure your LGS.opt file (located at C:\Program Files (x86)\Common Files\Leica Geosystems\License-Server\lgs.opt) looks like this:

DEBUGLOG +"C:\Leica Geosystems\CLM\LogFiles\lgs.log"
NOLOG IN
TIMEOUTALL 240
ENABLE_DB_HISTORY 1
PATH_DB_HISTORY C:\Leica Geosystems\CLM\LogFiles

ENABLE_DB_HISTORY should be set to 1 in this file. Please copy the file to a new location, edit it, and re-save it if the file says it’s read-only.

• During the installation of CLM, users may encounter the following message. This is commonly due to a service like JetStream Enterprise running in the background.

To enable the successful installation of CLM, please follow these steps:

1. Launch the Task Manager.

2. Navigate to the Services tab.

3. Look up the process with the PID (Process ID) shown in the Close applications dialog. In this case, it is JetStream.

4. Terminate the process so that CLM can be installed.

5. After CLM is installed, click the Services button in the Task Manager and restart the service.

Note: As of Cyclone REGISTER 360 PLUS 2023.0.0, Jetstream Enterprise is no longer supported.

Import Issues

• Importing B2G files, regardless of whether they contain images, will not succeed if the Import Images option is turned off. The recommended workaround is to turn on the Import Images option in the Properties panel of the Import area when importing B2G files.

• In rare cases, when importing using Auto Cloud, Cyclone REGISTER 360 PLUS may hang. The data is imported correctly with links created. The workaround is to close Cyclone REGISTER 360 PLUS and open it again.

• When importing BLK2FLY GPS data with the Wall Aligned UCS option, it ignores the UTM/State Plane coordinate UCS. The workaround is to not use Wall Aligned with UTM.

• After importing from a BLK scanner (BLK360, BLK2GO, or BLK2FLY), if there were Setups that were not selected for import, there is a dialog box that states Failed to import on the un-selected Setups. The expected behavior is that these Setups should not be mentioned.

• If FARO scans fail to import, please contact Leica support. The scans collected from the newest FARO scanner may not be imported. Please contact Leica support for the newest FARO SDK. It may be the case that new software from FARO needs to be downloaded and installed separately.

• Once imported into 2021.0, B2G files are changed and are not compatible with older versions of Cyclone REGISTER 360 PLUS. Please make a backup copy of the B2G file BEFORE import.

• After downloading Setups from the scanner, the dialog will show if the number of Setups selected is less than the total Setups on the scanner. While correct, this dialog should be ignored.

Export Issues

• When exporting BLK2GO scans to E57 (as one file) using the Separate Setups (structured, unstructured) option, the exported E57 file does not contain WayPoints and panoramic images. The workaround is to export data to E57 as a single point cloud. This method ensures that both WayPoints and panoramic images are included in the exported file.

• To publish a unified point cloud, ensure that the Create a point cloud during finalized registration option is checked to avoid incompatibility.

• In rare cases, exports to LGS and RCP show different elevations on point cloud points than in Cyclone REGISTER 360 PLUS.

• In Cyclone REGISTER 360 PLUS 2023.1.0, structured exports, such as RCP, E57, PTX, and PTG, may include deleted points on a second export, despite settings to export only cleaned point clouds. A workaround is available to restore point cloud cleaning from version 2023.1.0:

  1. Create a shortcut to Cyclone REGISTER 360 PLUS on the desktop if one does not exist.

  2. Right-click the shortcut and select Properties.

  3. Append -support to the Target field entry, separated by a space as shown below:

d. Launch Cyclone REGISTER 360 PLUS via the shortcut.

e. Open a project that needs the cleaning restored.

f. Open the project requiring cleaning restoration.

g. In the Review & Optimize area, right-click the SiteMap with the Bundle(s), and choose "Restore Cleaning". Cleaning will be applied to all Bundles in the SiteMap.

h. Proceed to the Finalize step, then to the Report step, and generate a new Finalized Registration.

i. Export using the desired structured format.

• Project thumbnails (the image shown in the project explorer) are not preserved in the RAF export file.

• After creating a Finalized Registration with a fenced area and exporting it to RCP with applied decimation through subsampling, certain Setups are missing from the exported RCP files. Splitting Setups into different SiteMaps increases the number of exported Setups but does not completely resolve the issue.

BLK360 Issues

• When downloading scans from BLK360, progress is being made even though the dialog says 1% for much of the download.

• When the BLK360 battery is low, download is not supported. The download button will not be clickable though no warning message is given.

• When the BLK360 battery level is low, the charge percentage number is not shown.

• When a download from the BLK Data Manager is cancelled, there is an intermittent error that causes the program to hang. The workaround is to restart both the scanner and BLK Data Manager and reconnect.

• If a download is unsuccessful, a user might receive a message stating Downloaded 0 setup(s). If you receive this message, please re-download those scans.

• BLK360 scans will appear chronologically in the Download Manager while BLK2GO walks will appear in alphanumeric order.

• The temp folder may not contain non-ASCII characters.

• If there is a synchronization issue between the tablet and the scanner (which may be caused by a poor or interfering Wi-Fi connection) items created on the tablet using FIELD 360 such as links, images, and geotags may not be synced back to the scanner. The workaround here is to download the data from the tablet using FIELD 360 rather than directly from the scanner.

• In rare cases, downloading scans from BLK360 may fail. The workaround is to restart the BLK360 scanner.

• Only BLK360 projects will appear when the user connects to Cyclone FIELD 360. Cyclone FIELD 360 does not store full project data for the RTC360 / P-Series and should be imported directly from the scanner's USB memory stick.  

• The Re-import image command does not function correctly when trying to import the image(s) from a BLK360 scanner with a cable connection, i.e. via LAN.

BLK2GO Issues

• When a download from a BLK2GO scanner is cancelled, the user will not be informed.

• The Save B2G file(s) function during import from the BLK2GO scanner is broken. The workaround is to use the Data Manager.

• After the recommended firmware update for BLK2GO, in some cases, Setups are unable to be imported over Wi-Fi. The workaround is to import via USB-C cable.

• Due to the unstructured nature of BLK2GO data, E57 files created from the scanner will not be supported for import into Cyclone REGISTER 360 2021.1 or earlier. Users should save original B2G files for future use.

BLK ARC Issues

• As of version 2024.0.1, importing BLK ARC data, which includes static scans and FIELD 360 links, directly into Cyclone REGISTER 360 PLUS is not fully supported. This is because the image assets and static scans may not be fully imported. The recommended method for full data import is using BLK Data Manager 2024.0.1.

• When importing BLK ARC scans containing georeferenced data, the global coordinates may not be read upon the first import of the raw data into Cyclone REGISTER 360 PLUS. The recommended workaround is to import scans twice using specific import settings mentioned in the workflow below:

1. Download the job from BLK ARC using the Data Manager.

2. Navigate to Settings | General and define Import settings in Cyclone REGISTER 360 PLUS. Ensure SLAM recalculation upon the import is enabled by choosing one of the settings below:

a. BLK: Re-Run SLAM

b. BLK: Use Re-Observation

3. Drag and drop the job folder into Cyclone REGISTER 360 PLUS and import the data.

4. Remove the imported scan from the project or delete the project altogether.

5. Import the same B2G file again:

a. Drag and drop the B2G file into Cyclone REGISTER 360 PLUS.

6. (Optional) Use the map to visualize the scans on a satellite map.

a. Click Show Geo Image Bar to visualize the satellite view.

b. Locate precisely the environment and click Get Image.

c. Click Place by Geo Coordinates to automatically place the scan according to the global coordinates.

d. Double-click the SiteMap to centre the view.

7. Select the Coordinate System in the Import options and define other Import and Registration settings.

Note: SLAM recalculation is not mandatory this time to retrieve the GNSS data.

a. Select Auto Cloud in Import settings to automatically align multiple scans.

8. Import the data.

Publishing Issues

• There can be an issue when publishing to JetStream Enterprise with a large number of assets in the project. The workaround is to publish the project to LGS and then import the LGS to JetStream Enterprise.

Note: As of Cyclone REGISTER 360 PLUS 2023.0.0, Jetstream Enterprise is no longer supported.

• There is an issue where publishing to Cyclone ENTERPRISE may not direct users to the correct landing page. The workaround is to enter the Host Name and Port for the target server. The Host Name should only contain the top-level domain part of the URL. In some cases, a hostname may be valid for the connection test but will not work for publishing. In this case, the connection dialog will display the Project Selector. To solve this problem, edit the Host Name to remove all text after the Top Level Domain. For example, "https://mycycloneenterprise.com/abc...-////" should be trimmed to "https://mycycloneenterprise.com"

• When publishing to Cyclone ENTERPRISE fails, the following error message could mean that:

  • The server has low disk space.

  • The network drive is disconnected.

  • Invalid file path.

• RCP publish will fail if the Setup published has zero points. The workaround is to restore the points for the Setup and publish again.

• There is an issue with publishing data to TruView Cloud with Applied Control for projects created in Cyclone REGISTER 360 prior to 2020.0. The Setup icons do not match the SiteMap. The solution is to create another Finalized Registration, and then re-publish to TruView Cloud.

• In some cases, when publishing to TruView Cloud, Setups do not appear in the SiteMap view. The workaround here is to publish to LGS and import the file into TruView Cloud.

• When publishing an RCP file, the progress bar will appear and stall at a certain interval. Though the progress bar does not update, the export is progressing. Users may check the task manager to ensure that the service is still functioning.

• When publishing an LGS file, the Hue and Greyscale pano layers will show the uncleaned cloud. A workaround is to publish to E57, re-import the data, and then publish to LGS.

• The 2-billion-point limitation has been removed when publishing to RCP.

Classification Issues

• In some cases, the Classified Point Clouds seem to disappear when switching between SiteMap and Bundle Cloud View or Setup View. Selecting Show/Hide Setups twice can refresh the screen and they will be visible.

• Auto-Classification runs one Setup at a time. In case a very large point cloud is detected, the following warning will appear.

Asset Issues

• When panoramic images are turned off in a Setup view, the camera position may occasionally change and appear inverted. Going back to the SiteMap view and then into the Setup view again will fix the issue.

• Automatic image matching of imported panoramic images may not always be correct.

• On rare occasions, HDR images may appear grey with very little variation. The workaround is to open the image with the Tone Map Editor and re-save the image.

• In some cases, E57 files published from Cyclone REGISTER 360 PLUS, when imported into ReCap, may display blurred imagery when entering the Setup location sphere. This is a known issue with ReCap's handling of E57 files. RCP files published from Cyclone REGISTER 360 PLUS do not show any display issues. The E57 export using the Compatibility mode option may help with this issue.

• The zoom scale bar will be captured in the image in the Import area when using the satellite or street map.

Applied Control Issues

• If a Control file has a leading space (a space as the first character), then that line is ignored. The workaround is to manually delete the first line.

• A published RCP that has Applied Control with very large coordinates shows a black map rather than a color image. The workaround is to create another map in ReCap.     

• In some cases, if the scanner was inverted and automatically acquired targets, applying control fails. The workaround is to manually acquire the targets.

• Virtual target snaps below were clicked and the exported data has different coordinates to those in Cyclone REGISTER 360 PLUS. The workaround is to lock the Bundle before applying control.

 Target Usage Issues

• Paper Targets should not be placed on significantly curved surfaces. The workaround is to create a virtual Target rather than using the algorithm to best fit these cases.

• Inserting virtual Targets with BLK2GO data can have issues if the Pano image is on. The workaround is to turn off the Pano image and then create a virtual Target.

UCS-Related Issues

• When a Setup has a UCS created from it, the UCS must first be deleted before the Setup can be deleted from the project.

Cloud-to-Cloud Registration Issues

• The cloud used for Cloud-to-Cloud registration cannot be cleaned by the Smooth Surface feature. Therefore, the options for which cloud to clean are not available.

Point Cloud Issues

• Scans that have more than one point cloud in a Setup are not properly displayed. This can be the case when a C10 has a full 360 scan and a highly detailed window scan. The scans still exist and can be exported.

• After editing an HDR tone map, other versions created will still show the original tone map in the thumbnail but the Pano and point cloud will be correct.

Bundle Optimization Issues

• In rare cases, the Bundle will show an optimized state, but there is still an unoptimized Link in the Bundle (not shown with a dotted line). Optimize the Bundle to resolve the issue or split the Bundle into smaller Bundles and look for the suspect dotted line Link, delete this Link, and re-optimize.

Finalize Step Issues

• Hyperlinks in the master SiteMap in the Finalize area, once created, will hide behind the inserted image, but will still export to TruView, Cyclone ENTERPRISE, and LGSx properly.

SDK and Library Compatibility

To ensure exceptional performance, reliability, and security, Cyclone REGISTER 360 PLUS is regularly upgraded to incorporate new external libraries and SDKs.

Cyclone REGISTER 360 PLUS 2024.0.1

• The BLK Mobile API and BLK Mobile SLAM library are updated to 4.1.0 and 2.3.1, respectively.

• The .NET framework has been upgraded to version 4.8.1.

Cyclone REGISTER 360 PLUS 2025.0.0

• CLMnext 3.3 has been upgraded to version 7.1.0.

• pcStruct SDK has been updated to version 9.0.

Deprecated Features

Leica Geosystems strives to provide support for the widest array of operating systems and file formats possible as is reasonable given current technologies and support from third-party partners.

With each release, we review our list of currently supported formats and operating systems in line with industry trends and announce product terminations.

Leica Geosystems may add or terminate support for a file format during any release. Obsolete operating systems will be supported for six months after their announced termination or the next major software release, whichever comes first. Server products will be supported in alignment with Leica’s Client License Manager (CLM) supported servers to guard users against incompatibility.

Cyclone REGISTER 360 2020:

• TVG files are no longer published. Users should use the LGS format. If a TVG is required, users can Publish to TruView Local and run the dataset through the free utility Leica Pack&Go.

Cyclone REGISTER 360 2021:

• Windows 7, 8, and 8.1 are no longer supported.

Cyclone REGISTER 360 PLUS 2023.0.1

• FARO raw scan files from the newest FARO scanners are not supported due to a lack of availability in the FARO SDK.

Cyclone REGISTER 360 PLUS 2023.0.0:

• Publishing to TruView Local and JetStream Enterprise is no longer supported.

Cyclone REGISTER 360 PLUS 2023.0.3:

• ZFC scanner data files are no longer supported due to a lack of updated supporting MS redistributables.

• iStar Camera images are no longer supported due to the lack of updated supporting MS redistributables.

Cyclone REGISTER 360 PLUS 2023.0.3:

• This release of Cyclone REGISTER 360 PLUS will only support MS redistributables supported by Microsoft.

Licenses

All users with valid CCP for either Cyclone REGISTER 360 or Cyclone REGISTER 360 PLUS or Cyclone REGISTER, or with CCP valid as late as 1 February 2025, can run this new version of Cyclone REGISTER 360 PLUS with no new license required.

All users with valid CCP for Cyclone REGISTER 360 (BLK Edition) or Cyclone REGISTER 360 PLUS (BLK Edition) or with CCP valid as late as 1 February 2025 can run this new version of Cyclone REGISTER 360 PLUS (BLK Edition) with no new license required.

Users do not need to migrate to a Cyclone REGISTER 360 PLUS or Cyclone REGISTER 360 PLUS (BLK Edition) license in order to run Cyclone REGISTER 360 PLUS if their CCP or subscription is valid.