Importing Register 360 data into Cyclone Core. Why is cloud unified?
-
- I have made 10-20 posts
- Posts: 18
- Joined: Thu Feb 15, 2018 9:07 am
- 6
- Full Name: Hobbitfoot
- Company Details: OMA
- Company Position Title: Technician
- Country: Finland
- Linkedin Profile: Yes
Importing Register 360 data into Cyclone Core. Why is cloud unified?
I've just registered a project of over 200 scans in Register 360 but now I need to do a little additional editing in Cyclone Core before working with the data as an .rcp file. I am wondering why the completed registration is a unified (single) cloud? Is there a way, during the import process, that I can keep it as separate clouds, for control purposes or do I need to fully re-register it in Cyclone core. Thanks in advance
-
- V.I.P Member
- Posts: 916
- Joined: Tue May 11, 2021 5:36 pm
- 2
- Full Name: Adam Berta
- Company Details: InnoScan 3D Hungary Kft
- Company Position Title: unknown
- Country: Hungary
- Linkedin Profile: No
- Has thanked: 52 times
- Been thanked: 297 times
- Contact:
Re: Importing Register 360 data into Cyclone Core. Why is cloud unified?
How did you imported? From register360 database? Or you exported and then imported? If the latter then what did you export?Hobbitfoot wrote: ↑Tue Mar 14, 2023 6:29 am I've just registered a project of over 200 scans in Register 360 but now I need to do a little additional editing in Cyclone Core before working with the data as an .rcp file. I am wondering why the completed registration is a unified (single) cloud? Is there a way, during the import process, that I can keep it as separate clouds, for control purposes or do I need to fully re-register it in Cyclone core. Thanks in advance