Product

Leica Cyclone 9.0

Date

1st September 2014

From

Bill Wallace, Senior TLS Software Product Manager

These release notes provide important information about the contents of the Cyclone 9.0 product
release.

Contents
1.

INTRODUCTION ................................................................................................................................................... 2

2.

NEW AND UPDATED FEATURE SETS...................................................................................................................... 2

2.1
Registration Workflow Enhancements ................................................................................................. 2
2.2
Roadway Mapping, TOPO Mapping and 2D Drafting Workflows ....................................................... 15
2.3
Extrude Shape (by 2 picks) Steel Fitter .............................................................................................. 20
2.4
Miscellaneous Enhancements ........................................................................................................... 23

3.

BUG FIXES ....................................................................................................................................................... 23

4.

KNOWN ISSUES ................................................................................................................................................ 24

5.

WORKING WITH OLDER COMPUTER SYSTEMS ....................................................................................................... 24

6.

INSTALLING CYCLONE 9.0 .................................................................................................................................. 24

6.1
Upgrading to Cyclone 9.0 from Cyclone 8.1.3 6.0.x ........................................................................ 25
6.2
Upgrading to Cyclone 9.0 from Cyclone 5.8.x or earlier ..................................................................... 25
6.3
Compatibility with Cyclone 9.0, and Earlier Versions .........................................................................25
6.4
Updating and Optimizing Cyclone 5.4 or Previous Databases to Cyclone 9.0 ................................... 25
6.5
Updating Cyclone 5.5 through 6.0.4 Databases to Cyclone 9.0 ......................................................... 25

hds.leica-geosystems.com
e-mail: support@lgshds.com
euro-support@lgshds.com
1-(925) 790-2300 (ph), 1-(925) 790-2309 (fax)

Leica Geosystems HDS LLC

4550 Norris Canyon Rd
San Ramon, CA 94583 USA

1.

Introduction

The Cyclone 9.0 release delivers a wide array of new capabilities and significant improvements in
productivity and ease of use in many of the most important Cyclone workflows. Users will notice an
entirely new approach to the registration process with automated tools, as well as a whole host of
productivity enhancing features.

2.

New and Updated Feature Sets

2.1 Registration Workflow Enhancements

Every scanning project requires the user to register data. This can range from a simple process on
smaller jobs to a long and complex workflow for larger, more diverse projects.
Cyclone REGISTER has always provided the industry leading solution with more options and unlimited
project size capacity. Now, several new and related features provide highly productive workflows, as well
as improvements to traditional workflows currently supported.
2.1.1

The New Workflow

A new workflow for registrations is supported by a very large set of tools and functionalities in Cyclone,
which are described later in this section. It should be noted that these new tools, features and workflows
do NOT replace any previous tools or workflows. These new options will provide a better starting
workflow, and users may choose to use their expertise and existing tools with these new approaches.
The basics of this new workflow include the following:

2.1.2

During import, the user selects the Auto Align Scans feature
New scan matching algorithms attempt to pre-align all scans to prepare for Cloud-to-Cloud
registration
Cyclone places these scans into Groups; the final goal of this process is to get all scans into one
group which is ready to be registered, but the system may not be able to get 100% of scans into a
single group
The user manually updates, corrects and finalizes the groups using the new Visual Registration
tools
Once the user has succeeded in getting all the scans into one group, they run the final
registration
Auto Align Scans

Cyclone 9.0 introduces a new Auto Align Scans feature. This feature is used on project data to provide a
starting point for doing a registration. It is set of algorithms that compare scans from different scanner
locations during or after import. It first identifies overlapping areas and then provides an initial alignment
of the scans. This is not a complete automated registration but a rough, automatic alignment which
prepares the scans for Cloud-to-Cloud registration.
Scans that have been initially aligned are added to a Group, which is existing element in Cyclone but now
is common in workflows. You can read the following section in this document for a more complete
description on groups.
With good overlapping positions and sufficient density, the Auto Align Scans feature should provide 100%
alignment initially of all scans in the project into one group, known as Group 1.

2/26

If the algorithms are unable to identify 100% of the connections, this feature will align multiple groups of
scans. For example, it may place scans 1-4 in Group 1 and scans 5-8 in Group 2.
If the algorithms are unable to align some of the scans, such as scans 9 and 10, it will leave them in an
ungrouped status along with Group 1 and Group 2.
In each scenario, once the Auto Align Scans feature is complete, the user should review the groups as
described below to ensure that the scans are associated and grouped correctly. These new tools should
be used to verify groups and finalize them into one group for final Cloud-to-Cloud registration.
2.1.2.1 Details
Use the steps below to run the Auto Align Scans feature.
Auto Align Scans runs on the following formats of imported scan data:

C5/C10
P15/P20
ZFS
Ixf (Optech)
Fls (Faro)
PTX
e57

1. Open Cyclone and create a database

2. Select the database. From the top menu in the Navigator, select File and choose Import
(select scanner type) from the drop-down menu, or for separate scan files, choose Import as
Auto Align Project

3/26

3. The import dialog box appears. For Scanner Project files, the Auto Align Scans check box is
selected by default. The user can also select the Generate Scan Thumbnails option, which is
explained later in the document.

4. After import, a Registration window will appear with the 2D Scan Thumbnail window.

4/26

2.1.3

ScanWorld Grouping enhancements

The Group object in Cyclone has gained new prominence in this release due to the new Auto Align Scans
feature and Visual Registration tools. The Visual Registration Tools are described in more detail in
another section of this document.
A group is a container for aligned and/or pre-registered scans. Groups are highly valuable, as they
contain final sub-registrations inside the large registration. Scans grouped from the Auto Align Scans
feature are pre-aligned, meaning that they are very close to a proper location but not yet finalized. Groups
may also contain visually aligned scans by the user with the new Visual Alignment tools.
Groups work with targets using the Create Groups with Targets command. Groups created by any
method can take advantage of the new grouping tools to speed up the registration process.
The groups are represented in the following manner:
In this example, groups were created by the Auto Align process. Once this process is finished, it is
common to have more than one group.

5/26

Groups can be managed using the following commands:

1. Visual Registration (see the Visual Registration section for a full description)
2. Merge ScanWorld Groups: this command is used to merge groups together using a set of
existing selected constraints or selecting only the groups without selecting constraints. A
group may also be merged to a single ScanWorld.

3. Optimize ScanWorld Group: this command is used to pre-register a group to find out if it is
valid before continuing with the remaining registration. This very important command allows
the user to know if the group created is valid after editing. Before this command, the only way
to perform this check was to run a Register command on the whole registration.
4. Create ScanWorld Groups from Auto Alignment: this command resets groups to the
original state after importing. Use this command to reset groups without re-importing scan
data.

2.1.4

Visual Registration Tools

In addition to the new Auto Align Scans feature and enhanced group functionality, Cyclone 9.0 introduces
a new set of Visual Registration Tools.
2.1.4.1 2D Scan Thumbnails
One of the key elements of the Visual Registration Tools is the new object called 2D Scan Thumbnail,
which is generated during the import process along with the Auto Align Scans process. Thumbnails
provide a top-down specialized view of each ScanWorld. This top down view is utilized as a key part of
the Visual Registration process. As users work with groups to align the entire project, they use these scan
thumbnails to visually recognize various scans for commonalities to identify overlapping areas.
The 2D Scan Thumbnails are generated using these tools and can be customized by doing the following:
The 2D Scan Thumbnail window is used to visually inspect the scans and decide if a match exists
between a pair of ScanWorlds. After selecting the Scan Thumbnails, users can further inspect them by
opening them in the Image Previewer for a larger view.

6/26

2D Scan Thumbnails can be generated during or after import of scan data.

1. During import, check Generate Scan Thumbnails in the Import dialog.

2. After import, select a project folder or individual ScanWorlds, and in the top Navigator menu,
select the Create drop-down menu and choose the Re/Generate Scan Thumbnails option.

7/26

3. The 2D Scan Thumbnail window can also be opened from the Registration window by
selecting Visual Registration in the top menu and choosing 2D Scan Thumbnails from the
drop-down menu.

4. Right click on the selected thumbnail and choose Re/Generate Scan Thumbnail from the
menu.

8/26

5. Select thumbnails by clicking on the first one and then SHIFT + left click on the second one.
Next, click the Open in Image Preview button to view the thumbnails in the Image Preview
window.

6. Inspect scans in further detail using the Image Preview window.

9/26

10/26

7. Cycle through the images by clicking the arrow buttons.

8. To align a pair of scans in the Visual Alignment window, click the Open in Visual Alignment
button.

11/26

2.1.4.2 Visual Registration Process

The Visual Registration process is used to visually match scans and align them using Cloud-to-Cloud
registration. The user looks through the 2D scan thumbnails in the various groups and ultimately selects
two scans to align. If two scans can be aligned from two different groups successfully, those groups will
collapse into a single group, inheriting the smaller number of the two groups.
For instance, if the user sees a scan in Group 2 which looks like it matches to a scan in Group 4, they
would load those two scans into the Visual Registration tool.
If they are able to visually determine that they do in fact overlap each other, they will visually align them in
the Visual Alignment tool. If they accept this alignment, Group 4 would be added to Group 2, and any
groups after Group 4 would have their numbers updated with Group 5 now becoming Group 4 and so on.
The Visual Registration Tools are accessed and used in the following manner:
Scans can be sent to the Visual Alignment window by selecting them in the registration window or through
the 2D Scan Thumbnail window. Once in the Visual Alignment window, scans can be moved and rotated
together and finally joined by Cloud-to-Cloud registration.

1. Scans start out viewed in plan view. Only the blue scan can be moved. The default tool
allows movement in the XY plane. Start out by moving the scan together. Usually a common
corner or obvious point is selected.

12/26

2. Next the cloud can be rotated into place using the rotate tool. Left click and hold to pinpoint a
rotation point. While still holding the mouse button down, drag away from the rotation point
and then rotate the blue cloud into place.

3. Once the cloud is aligned in the XY, switch to the elevation view and align the elevation of the
blue cloud to the orange cloud.

13/26

4. When alignment is complete, Cloud-to-Cloud can be run on the scans.

5. When complete, a dialog box appears where the user can select to use the cloud constraint
to merge groups. Selecting yes will merge the scans into one group.

14/26

6. If the scans were part of a larger group, the two groups will merge into one. In this case,
Scans 5 and 1 were joined. Scan 1 was in Group1 and Scan 5 was in Group 2. After Visual
Registration of Scan 1 and Scan 5, Groups 1 and 2 merged into Group 1.

2.2 Roadway Mapping, TOPO Mapping and 2D Drafting Workflows

Cyclone 9.0 introduces several new 2D drafting and 3D surface creation tools.
2.2.1

Roadway Alignment Drafting

The Roadway Alignment Section Manager has been significantly updated to provide a much more robust
and productive set of tools for drafting roadway maps and surfaces using a cross section methodology.
The new workflow works in the following manner:

Users can now import LandXML-based roadway alignments or use simple polylines created in, or
imported to, Cyclone
Cyclone now understands sophisticated elements of alignments, such as spiral curve elements.
Users have a new set of template tools to create cross section templates using feature codes
Users define a template at a given station/section location
Users can turn on and adjust Vertical Exaggeration to assist in seeing the topology of roadways
with subtle changes in elevation
When moving to the next section, a user can copy the template forward as an option
If the template is copied forward, the user can visually adjust the template to fit the roadway
condition at that location
After defining cross sections along the alignment, and having used feature codes, the user now
has line work created between the cross sections along the roadway
This newly created linework can be used for a variety of purposes
o Used as breaklines for surface meshing in Cyclone
o Exported for use as breaklines in external systems
o Exported for use as 2D map/drawings in external systems

15/26

The new Roadway Alignment Drafting tools work in the following manner:
1. Alignment/Station Manager can be accessed from the location of the old
Section Manager by selecting Tools from the top navigation, choosing
Roadway Alignment & Station from the drop-down menu and
Alignment/Station Manager from the submenu.
2. Within the Manager, users can Import or Create Alignments.
3. Next, users create the Extents of their cross section and station spacing.
This process is similar to the old way but is now accessed under the
Stations tab. See Figure 1.
4. Once the Stations have been created, a secondary Plan View window will
open displaying the alignment, cross section location, and stations. See
Figure 2.

Figure 1

Figure 2

5. Now the user has the ability to create a feature coded template, which can be saved and used at
a later date or on another project. See Figure 3.

Figure 4

Figure 3

6. The template can also be copied automatically to each adjacent station, allowing the user to
quickly adjust the points individually or the template as a whole to match the point cloud cross
section.
7. Once templates are at all stations, users can create or export COGO Points, Cross Section Lines,
and Breaklines under the Objects/LandXML tab. See Figure 4.

16/26

8. The user can now see all objects created in the ModelSpace View. See Figure 5.

Figure 5

2.2.2

SmartPicks

Cyclone 9.0 introduces familiar features that were originally introduced in Cyclone II TOPO and some
CloudWorx versions. The SmartPicks feature can work in a standalone manner or add Osnap-like
functionalities to any point selection process used for modeling, drafting, or other workflows. SmartPicks
are also deeply integrated in the Points-on-a-Grid feature.

SmartPicks are active filters that allow the user to ask the system to analyze their current cursor location
in order to find the best point cloud pick point that matches the current filter. These include the following
available filters:

Closest point: this is the closest point and is an actual point on the point cloud.
Highest point: using a downward looking viewpoint and a specified radius, the filter finds the
highest actual cloud point within that area.
Lowest point: similar to the highest point pick, the lowest point returns the lowest actual cloud
point in that area.
Ground point: it also uses a downward-looking aspect, but unlike the previous two points, it
returns a point at the exact X and Y coordinate and calculates Z (elevation) by doing a patch on
the lowest cluster of points found in the area by assuming it is the ground. This is an interpreted
point, not necessarily an actual measured cloud point.

SmartPicks are useful in many conditions and are most commonly used in conjunction with Points-on-aGrid, which is described later in this document.
When used in a standalone manner (not part of Points-on-a-grid), the SmartPicks feature provides an
optional secondary window that displays a zoomed viewpoint of a clipped area to assist in visualizing
where the filtered point in being projected.

17/26

SmartPick tools are accessed and used in the following manner:

1. SmartPick Viewport can be accessed from the top navigation in the View
menu by selecting SmartPick Viewport
2. The user chooses a SmartPick method in Viewport window. See Figure 1.
3. In the Viewport, the user can hover the cursor in the upper corners for
zoom control and in the lower corners for rotating. They can also use the <
and > keyboard buttons as hotkeys to rotate the point cloud.
4. With one of the pick modes selected, the display in the Viewport will follow or pan with the cursor
location in the main screen, which works with any Cyclone function that requires a pick. See
Figure 2.

Figure 1

2.2.3

Figure 2

Points-on-a-Grid

Cyclone 9.0 now includes Point-on-a-Grid, a feature common to other Leica HDS software products. Most
useful for doing ground surfaces, this feature is also useful for other purposes, such as moving the UCS
to the face of a building.
This feature allows users to place ten, hundreds or even thousands of survey points on a grid in a matter
of a few seconds.
The basic workflow for the Points-on-a-Grid feature includes the following steps:

Set the orientation and location of the grid using the UCS tools
Outline an area of interest by rectangular or polygon fence
Select a SmartPick type (optional)
Upon launching the process, Cyclone places survey points at all appropriate locations on the grid
following the SmartPicks rules
Export these points or use them to create a mesh in Cyclone with the option of including
breaklines or other points

Points-on-a-Grid is accessed and used in the following manner:

1. Select tools in the top navigation and Points On Grid from the menu.
2. The Points On Grid dialog box opens with the Reference Plane tab displayed.
See Figure 1.
3. Manually move and rotate the reference plane in the display or use the rotate
and placements tools in the Reference Plane tab. Orientate the reference
plane and set the grid size, which is where the points will be placed. See
Figure 2.

18/26

4. Select the Points On Grid tab in the dialog box and choose the SmartPick Method, COGO Point
number, and Feature Code name. See Figure 3.
5. Fence an area to select where points are placed. See Figure 4.
6. Preview or place points. Once points are placed, the vertices will be set. See Figure 4.1.

Figure 2

Figure 1

Figure 4.1

Figure 4

2.2.4

Figure 3

2D Drafting/Building Section Assistance

Cyclone 9.0 introduces a new Quick Slice tool, which is most useful for setting up a
slice for doing 2D drafting of building footprints or sections. Previously, a user would
have to take multiple actions to setup a building drafting section, including setting a
UCS to align the building to the viewport, setting a slice location and thickness,
adjusting the viewpoint to be downward-looking to zoom in, and turning on a
workplane for drafting. The new Quick Slice tool reduces these actions to one or two
picks using the following workflow:

The user picks one or two points on the face of a building

These points represent the face of the building

This tool is accessed using the following steps:

1. Select a pick point as the center of the slice. The slice thickness is one meter. Pick two points to
control the slice thickness. The first pick point is used to grow a surface on the wall to which it will
square the reference plane. See Figure 1.
2. From the top navigation, select Tools and choose Quick Slice from the drop-down menu.
3. In the display, view a slice of the point cloud rotated to the building face where the pick point was.
The reference plane is also active in this view, which can be put into drawing mode. See Figure 2.

19/26

4. Users can now draw the building footprint. All linework will be projected to the reference plane,
and all cutplane tools will apply to the slice.

Figure 1

Figure 2

The new quick slice tool can also be used to QA/QC how well a registration has come together.
1. Use Quick Slice as described above.
2. Open ScanWorld Explorer, select all scans, and click the
image. Apply ScanWorld Colors to
Scans. See Figure 1.
3. Turn off the Reference Plane and zoom to area with multiple overlap point clouds. See Figure 2.

Figure 2

Figure 1

2.3 Extrude Shape (by 2 picks) Steel Fitter

Cyclone 9.0 introduces a new feature Extrude Shape (by 2 picks). The initial implementation of this
feature only offers to extrude steel shapes, but it will extrude other shapes in future versions.
This feature currently allows users to place steel shapes that are automatically aligned to the point cloud
by simply providing two picks along the length of any appropriate steel member. It supports the following
shapes:

Wide flange
Channel
Angle
Tee
Rectangular tube

Cyclone requires the user to select an appropriate catalog of shapes from the provided catalogs, such as
AISC Steel Shapes, or from any custom catalog developed by the user. Unlike previous Steel Fitting
methods that try to fit a steel item to the entire available cloud, this feature does NOT require the user to

20/26

isolate a portion of the cloud that only contains the steel object of interest. Users can work in congested,
huge clouds and simply provide two picks on the member of interest.
The new Extrude Shape (by 2 picks) tool is accessed in the following manner:

1. Open a point cloud ModelSpace with steel shapes, such as Wide Flanges, or angles contained
within it.

2. Select two picks on the extents of the steel shape as shown below.

Picks on steel

3. From the top menu in the ModelSpace, select Create Object from the top navigation and choose
Extrude Shape (by 2 picks) from the drop-down menu and a steep shape from the submenu. In
this example, Wide Flange is chosen.

21/26

4. In the Object Preferences dialog box, check the Catalog/Parts Table to use a parts catalog for the
steel type selected and to select which table by country the steel fitter should use.

5. The steel fitter will now open a parts catalog table where any size steel can be selected if the
current selection is not desired. Click OK to accept the current selection and fit.

6. The steel will be created and shown in the modelspace.

22/26

2.4 Miscellaneous Enhancements

In addition to major feature sets, Cyclone 9.0 also introduces enhancements to features below.
2.4.1

Import and Unify Improvements

1. Cyclone includes a new option to relax some of the automatic backup safety features during
the Unify process, offering significant increases in process speed. It also uses multi-threaded
processing during import and unify, which further improves speed. Cyclone can now use up
to 64 GBs of available RAM for import and unify, making both faster.

Use the steps below to access the new Import and Unify options:
Unifying
1. Open any ModelSpace.
2. Select a cloud to unify and choose Unify from the Tools menu accessible from the top
navigation
3. Two options for unify are available
a. Unify with Recovery file (standard method that Cyclone has always used)
b. Unify without Recovery file (new way that is more risky but faster)
4. Unifying without a recovery file means that in the rare event of a database failure, there will
be no way to recover the database. Users MUST make a backup copy of the database before
using this command.
Import
1. Import as normal
2. All single scan clouds with less than two billion points (each) will be sped up during import.
3. Cyclone can now use up to 64 GBs of available RAM to improve import time.
2.4.2

Preset views: top, down, back, front, left, right, retain zoom depth

In the ModelSpace and the Visual Alignment window when using the Preset views, the depth of the view
is retained. For example, zooming in to see a building in plan view and then switching to a side view does
NOT apply zoom extents, as the view changes to the side view at the same zoom level.

3.

Bug fixes

CLM licensing bug fix to reduce occurrences of frequently dropped licenses

CLM licensing bug fix to enable borrowed virtual licenses to be returned
CLM licensing bug fix that caused excessive delay in product startup
CLM licensing bug fix where AutoCAD crashed upon prompt for license server
Fixed bug where when attempting to append a plyline to an alignment (created from an arc)
caused an unrecoverable error
Fixed bug where two face target scan failed during import into Cyclone
Fixed bug where a Survey license did not support import of zfs and zfprj
Included .NET 4.0 in installer, which is required by older operating systems to successfully import
P20 data.
Fixed bug to allow limit box modification with Basic license
Fixed bug where point numbers were not recognized from TXT import
Fixed bug where Azimuth Angle and Elevation Angle measurement tools don't work on object
with Axis=(0,0,1)
Fixed bug where C10 / P20 data failed to import on Windows 8 Italian operating system
Fixed bug where PTX with malformed lines caused Cyclone to crash

23/26

4.

Fixed bug where preference setting to Treat (0,0,0) colors as missing was not properly applied
when publishing TruViews
Fixed bug where changing center of rotation when using move/rotate tool caused Cyclone to
crash
Fixed bug where when importing TXT files, the option to create line segment between pairs of
vertices did not work
Modified all Cyclone progress bars to display integer percentages with no decimal precision
Fixed bug where a snap handle on the corner of grouped geometry could not be picked
Fixed bug where import of XML file took extremely long
Fixed bug where image object naming was wrong when importing E57 data
Fixed bug where column in cloud constraints wizard could not be adjusted

Known Issues

There is a CLM licensing bug where license usage either does not appear in the CLM
Administrator tool, or incorrect information is displayed. Although this tool is required to complete
other tasks like license activation, there is another utility that can be used to accurately report
license usage. The utility is called lmtools.exe and is located in the following folder:
C:\Program Files (x86)\Common Files\Leica Geosystems\License-Server

5. Working with older computer systems

If using older computer systems with Microsoft Windows 32 bit OS (XP or Windows 7), there may be
stability and memory issues while using certain functions. We recommend the following settings to offset
these issues:
1. Turn off Advanced Rendering from the Initialization tab in Preferences
2. Set the Load and Display setting for pcE data to three million under the Point Cloud tab in
Preferences
CYCLONE DATABASE MANAGEMENT RECOMMENDATION
To avoid possible database inconsistencies or corruption, we recommend the following:

Locate each .IMP file in its own folder

When copying, moving or backing up databases, we recommend backing up the complete

database folder, the PCESet folder, and the eventlog and recovery folders and files

The eventlog records administrative events and critical errors

The recovery file keeps databases consistent, avoiding data corruption that may happen in rare
situations

A warning dialog is displayed if a databases recovery folder cannot be found when it is added to
the server. Push the More Info button for more information.

6. Installing Cyclone 9.0

You must have Administrator-level privileges on your workstation to correctly install Cyclone software. On
Vista and Windows 7, run the installer using the Run as Administrator launch option found in the right
click context menu.

24/26

6.1 Upgrading to Cyclone 9.0 from Cyclone 8.1.3 6.0.x

Run the Cyclone 9.0 installer and follow the directions to proceed with the installation. Note any warning
message about the compatibility of databases from earlier versions. The installer will provide information
about any prerequisites as it sees fit depending on your current installation.
6.2 Upgrading to Cyclone 9.0 from Cyclone 5.8.x or earlier
Because the Leica Geosystems Cyclone 7.0 and later versions installer no longer include the CloudWorx
or COE products, it is recommended that earlier Cyclone installations first be uninstalled before installing
the latest Cyclone. Then, install CloudWorx and COE products using the latest installers, as necessary.
Run the new Cyclone installer and follow the directions to proceed with the installation. Note any warning
message about the compatibility of databases from earlier versions.
NOTE: If you are upgrading to Cyclone 9.0 from Cyclone 5.6 or earlier, your hotkey and toolbar
customizations will be reset during the upgrade. Before upgrading Cyclone, first export your
customizations, and after upgrading, import your customizations into the new version.
NOTE: If you are upgrading to Cyclone 9.0 from Cyclone 5.6 or earlier, your configured databases,
scanners, shortcuts, and preferences will be reset during the upgrade. You will need to manually reconfigure these items after upgrading Cyclone.
6.3 Compatibility with Cyclone 9.0 and Earlier Versions
Cyclone 9.0 databases are NOT backward compatible with any previous Cyclone version. Therefore,
databases that are updated using this version of Cyclone cannot be used with earlier versions. If you
need to work with your data in older versions of Cyclone, make an archive copy of your databases prior to
upgrading.
6.4 Updating and Optimizing Cyclone 5.4 or Previous Databases to Cyclone 9.0
Cyclone 5.4 and previous databases can be opened by Cyclone 9.0 only after being updated and
optimized to be compatible. Since it can take some time to update and optimize Cyclone databases, we
recommend that you optimize your databases overnight, particularly when multiple databases are
involved.
6.5 Updating Cyclone 5.5 through 6.0.4 Databases to Cyclone 9.0
Cyclone 5.5 through 5.8.1 databases can be opened by Cyclone 9.0 only after being updated to be
compatible with this version. Database optimization may be required.

25/26

7.

CLM Operating System Support (Client and Server)

CLM 1.4
Client OS

OS
XP (32bit / 64bit)
Vista (32bit / 64 bit)
Windows 7 (64bit)
Windows 8 (64bit)

Supported
No*
No*
Yes
Yes

Licensing Server
(Both Local and Remote)
OS
Supported
XP (32bit / 64bit)
No
Vista (32bit / 64bit)
No
Windows 7
Yes
Windows 8
Yes
Windows Server 2003 / 2003 R2
No
Windows Server 2008 SP1 SP2
No
(32bit / 64bit)
Windows Server 2008 R2
Yes
(Only 64bit available)
Windows Server 20012 / 2012 R2
Yes
(Only 64bit available)

* Although both XP and Vista are not supported by CLM 1.4, users are not blocked from installing
Cyclone on these machines as clients. A side effect of running the installer on XP is that the user will be
prompted with a series of dialogs when license components begin to install as shown below (four prompts
for 32bit and eight for 64bit operating systems). The user must make click though each of these dialogs
when installing on XP. Licensing issues that result from installing on these operating systems will not be
addressed since they are not supported by the CLM licensing system.

26/26