Register 360 Performance degradation and rendering issues
-
- I have made 30-40 posts
- Posts: 31
- Joined: Mon May 27, 2019 8:17 am
- 4
- Full Name: Thomas Madlberger
- Company Details: PORR AG
- Company Position Title: Execution Digitalisation Support
- Country: Austria
- Linkedin Profile: No
- Has thanked: 2 times
- Been thanked: 9 times
Re: Register 360 Performance degradation and rendering issues
Hello,
since the last update (which was obviously horrible) I've been waiting patiently for version 1.1, sadly just to get disappointed one more time.
What really makes me wonder is the fact everytime they implement something new also something "good" old gets destroyed.
Few Examples: Version 2021.1.0 greatly increased the speed of cleaning pointclouds because limit boxes started working the intended way. In the same update they completely obliterated the "suggest links in bundle" function. "We increased the performance for big projects" - LMAO, literally. Am I supposed to manually add every link for up to 2000 setups? Also the rendering is just awful, it worked so good in previous versions and now you have to wait every time until everything gets displayed. The undo/redo button is a meme to me, cant restore a delete command but if you manage to accidentally destroy your sitemap structure don't worry, we implemented a button for it.
Sry for this being kind of a rant, but since version 2021.0 I'm gone to good old cyclone. Not as pretty, but doing what it's supposed to do. Makes me a bit sad cause I was a big fan of R360 initially.
EDIT: I saw some claims in this forum that leica does alpha and beta testing. No offense, but if it takes me 10 mins to figure out key issues in both versions the quality of that testing is questionable at best.
since the last update (which was obviously horrible) I've been waiting patiently for version 1.1, sadly just to get disappointed one more time.
What really makes me wonder is the fact everytime they implement something new also something "good" old gets destroyed.
Few Examples: Version 2021.1.0 greatly increased the speed of cleaning pointclouds because limit boxes started working the intended way. In the same update they completely obliterated the "suggest links in bundle" function. "We increased the performance for big projects" - LMAO, literally. Am I supposed to manually add every link for up to 2000 setups? Also the rendering is just awful, it worked so good in previous versions and now you have to wait every time until everything gets displayed. The undo/redo button is a meme to me, cant restore a delete command but if you manage to accidentally destroy your sitemap structure don't worry, we implemented a button for it.
Sry for this being kind of a rant, but since version 2021.0 I'm gone to good old cyclone. Not as pretty, but doing what it's supposed to do. Makes me a bit sad cause I was a big fan of R360 initially.
EDIT: I saw some claims in this forum that leica does alpha and beta testing. No offense, but if it takes me 10 mins to figure out key issues in both versions the quality of that testing is questionable at best.
Last edited by tmad on Wed Jun 16, 2021 2:05 pm, edited 2 times in total.
-
- 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: Register 360 Performance degradation and rendering issues
Yeah the show suggested links are just broken, especially for RTC360 setups...
- stevenramsey
- Global Moderator
- Posts: 1937
- Joined: Sun Aug 12, 2007 9:22 pm
- 16
- Full Name: Steven Ramsey
- Company Details: 4DMax
- Company Position Title: Technical Specialist Scanning
- Country: UK
- Skype Name: steven.ramsey
- Linkedin Profile: Yes
- Location: London
- Has thanked: 30 times
- Been thanked: 72 times
- Contact:
Re: Register 360 Performance degradation and rendering issues
Great to see others banging the show suggested links drum, been a bug bear of mine since pre beta. it's the major issue holding me back from using REG360 for the odd job that really lends it self to the REG360 workflow
-
- 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: Register 360 Performance degradation and rendering issues
what i've got from our sales rep "why do you have so much links on that sitemap."stevenramsey wrote: ↑Wed Jun 16, 2021 3:51 pm Great to see others banging the show suggested links drum, been a bug bear of mine since pre beta. it's the major issue holding me back from using REG360 for the odd job that really lends it self to the REG360 workflow
i said:" i just want to have that function work as it should."
other one which is bothers me from 1 years ago import smart align by time function cannot sort the setups correctly.
hdr colouring notification which blocks the export if you miss that...
- stevenramsey
- Global Moderator
- Posts: 1937
- Joined: Sun Aug 12, 2007 9:22 pm
- 16
- Full Name: Steven Ramsey
- Company Details: 4DMax
- Company Position Title: Technical Specialist Scanning
- Country: UK
- Skype Name: steven.ramsey
- Linkedin Profile: Yes
- Location: London
- Has thanked: 30 times
- Been thanked: 72 times
- Contact:
Re: Register 360 Performance degradation and rendering issues
here here" i just want to have that function work as it should."
-
- I have made 30-40 posts
- Posts: 36
- Joined: Thu Dec 20, 2018 5:19 pm
- 5
- Full Name: Daniel Jansson
- Company Details: Teodoliten Mätteknik AB
- Company Position Title: Reality Capture Consultant
- Country: Sweden
- Linkedin Profile: Yes
- Has thanked: 7 times
- Been thanked: 6 times
Re: Register 360 Performance degradation and rendering issues
My spec is similar to yours but with 8 core i9 and RTX4000, what other IT magic do I need to fix to run the software as it should? The usual suspects are already there: software updated, graphics updated, NVidia settings are set, SSDs everywhere, no NAS, split temp folders and project folder, a lot of free disk memory, switched from 5k to 4k images.pburrows145 wrote: ↑Wed Jun 16, 2021 1:21 pmSeemingly IT issues...? I have seen huge improvements in the latest versions using my 3 year old laptop (64GM ram, twin SSD's, Quad core XEON, 16gb VRAM on P4000). Please talk to local support and log all cases, this allows San Ramon to see all issues and address them accordingly. Thanks!daniel.jansson wrote: ↑Wed Jun 16, 2021 8:11 am We have noticed a lot of performance issues overall...
I have 64GB of RAM so not super much but should still be enough for OK results. The previous version we had around 300 seconds, my latest import my highest number in the logs were 7000 with medium scans 4k image import. I will try balanced instead in the future, maybe this is what causing the issues with extreme import numbers I do see RAM usage around 80% so might be some swapping done in between my checks. I will also try to uncheck any compression in the scanner, even though I think we don't use any of that already. Thanks for the suggestions.badam wrote: ↑Wed Jun 16, 2021 9:02 amhow many ram do you have, doesn't it start to overflow and do swapping? As i wrote earlier balance is faster or not that much slower but uses way less resources, and more stable... I've seen 1500-2000 seconds with fast (usually high res, rtc360 where memory issues can arise) but with balance it is faster to import 1 setup but has less multithreading.The import times are and have always been pretty bad I think. But in this latest release, we are getting crazy numbers in the log files, 1600 seconds/setup. I am not sure if it could have something to do with the new distance filter during import that is highly ineffective.
I think the new "compressed" 40 % "better" compression can have performance implication during import, if you are using rtc360...
-
- I have made 30-40 posts
- Posts: 36
- Joined: Thu Dec 20, 2018 5:19 pm
- 5
- Full Name: Daniel Jansson
- Company Details: Teodoliten Mätteknik AB
- Company Position Title: Reality Capture Consultant
- Country: Sweden
- Linkedin Profile: Yes
- Has thanked: 7 times
- Been thanked: 6 times
Re: Register 360 Performance degradation and rendering issues
badam wrote: ↑Wed Jun 16, 2021 9:02 amhow many ram do you have, doesn't it start to overflow and do swapping? As i wrote earlier balance is faster or not that much slower but uses way less resources, and more stable... I've seen 1500-2000 seconds with fast (usually high res, rtc360 where memory issues can arise) but with balance it is faster to import 1 setup but has less multithreading.The import times are and have always been pretty bad I think. But in this latest release, we are getting crazy numbers in the log files, 1600 seconds/setup. I am not sure if it could have something to do with the new distance filter during import that is highly ineffective.
I think the new "compressed" 40 % "better" compression can have performance implication during import, if you are using rtc360...
I just tried a super small 2 scan project, medium with 4k images on balanced. Might been a small improvement or just luck but I still got 1100 seconds/scan.
These 2 steps are by far the biggest culprits during import:
Import::ReadAllImageData, 20.3, GB, 33, GB, 245, seconds
HandleMainScanData::BuildScene, 15.6, GB, 38.6, GB, 733, seconds
-
- 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: Register 360 Performance degradation and rendering issues
How many threads is it using for importdaniel.jansson wrote: ↑Thu Jun 17, 2021 10:08 am I just tried a super small 2 scan project, medium with 4k images on balanced. Might been a small improvement or just luck but I still got 1100 seconds/scan.
just search for the string cubemapsize in the log file
But those numbers looks ugly... I think there is some swapping in the background, if it uses more than one thread to import set it to safe mode instead of balanced...
In our machine with 64GB ram it uses 1 thread... Yesterday i tried to import just for testing nothing has changed, there is no performance gain nor degradation in import... Of course we are not using FW4.0 version. I'll upgrade if everything is working as expected in 2021.X.X.
here is the result. it is very similar to what we see in previous versions. the first one is 4k imagery the second one is without image. Checkbox disabled in the import menu, however in real life we never gonna use that feature... (small resolution) And both the source and the project located on the EXACT same NAS with 1 gbit connection and that low powered machine mentioned in the first post... (I just included this last part for leica)
PS: do you use any import functions? like target extraction, filtering, etc?
You do not have the required permissions to view the files attached to this post.
-
- I have made 30-40 posts
- Posts: 36
- Joined: Thu Dec 20, 2018 5:19 pm
- 5
- Full Name: Daniel Jansson
- Company Details: Teodoliten Mätteknik AB
- Company Position Title: Reality Capture Consultant
- Country: Sweden
- Linkedin Profile: Yes
- Has thanked: 7 times
- Been thanked: 6 times
Re: Register 360 Performance degradation and rendering issues
It used 2 threads for balanced on the small project, I tried again with a project with 9 scans and then it only used 1 thread.badam wrote: ↑Thu Jun 17, 2021 10:24 amHow many threads is it using for importdaniel.jansson wrote: ↑Thu Jun 17, 2021 10:08 am I just tried a super small 2 scan project, medium with 4k images on balanced. Might been a small improvement or just luck but I still got 1100 seconds/scan.
just search for the string cubemapsize in the log file
But those numbers looks ugly... I think there is some swapping in the background, if it uses more than one thread to import set it to safe mode instead of balanced...
In our machine with 64GB ram it uses 1 thread... Yesterday i tried to import just for testing nothing has changed, there is no performance gain nor degradation in import... Of course we are not using FW4.0 version. I'll upgrade if everything is working as expected in 2021.X.X.
here is the result. it is very similar to what we see in previous versions. the first one is 4k imagery the second one is without image. Checkbox disabled in the import menu, however in real life we never gonna use that feature... (small resolution)
import_reg360_2021.1.1.PNG
And both the source and the project located on the EXACT same NAS with 1 gbit connection and that low powered machine mentioned in the first post... (I just included this last part for leica)
PS: do you use any import functions? like target extraction, filtering, etc?
These are the results I got, I also went back in old log files for November 2020 to compare. I have gotten between 2-4 slower import times on the same machine. I also checked some 5k image imports in 2020 and it used 2 threads instead of 5 but the total import time / scan didn't really change much:
You do not have the required permissions to view the files attached to this post.
-
- 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: Register 360 Performance degradation and rendering issues
These are not very good numbers, where are the sources are kept during import, just to sort it out try to copy the source files to-from the source and project directory in windows explorer and see how fast it can read/write...daniel.jansson wrote: ↑Thu Jun 17, 2021 10:08 am These 2 steps are by far the biggest culprits during import:
Import::ReadAllImageData, 20.3, GB, 33, GB, 245, seconds
HandleMainScanData::BuildScene, 15.6, GB, 38.6, GB, 733, seconds
Code: Select all
###############################
RTC360: Job 214- stp002 Import time 235.381 Seconds total
Note, Used, GB, Available, GB, Delta, Seconds
Import::Initialize, 4.31, GB, 50.4, GB, 0.015, seconds
Import::ReadAllImageData, 9.67, GB, 48, GB, 71.5, seconds
HandleMainScanData::ReadScanInfo, 9.82, GB, 47.8, GB, 7.72, seconds
HandleMainScanData::WriteArchiveFile, 9.85, GB, 47.8, GB, 1.6, seconds
HandleMainScanData::BuildScene, 11, GB, 46.7, GB, 140, seconds
HandleMainScanData::ScrubScanDataPoints, 11, GB, 46.7, GB, 0.025, seconds
HandleMainScanData::Create Thumbnail, 11, GB, 46.7, GB, 2.29, seconds
HandleMainScanData::Rotate Points, 11, GB, 46.7, GB, 0.0686, seconds
HandleMainScanData::ProcessScanPoints, 11.1, GB, 46.5, GB, 1.9, seconds
HandleMainScanData::CreateCubemapsForWayPoint, 11.8, GB, 45.9, GB, 3.01, seconds
HandleMainScanData::ColorizePoints, 11.9, GB, 45.8, GB, 0.293, seconds
HandleMainScanData::WriteToPointCloud, 12.1, GB, 45.6, GB, 2.37, seconds
HandleAllSubScanData::Done, 11.9, GB, 45.8, GB, 0.029, seconds
Import::FinalizePointCloud, 11.6, GB, 46.1, GB, 3.51, seconds
Done, 4.36, GB, 53.3, GB, 0.749, seconds
###############################