MetroX ONLY issues in MetroScan 5.8.5

Support & Feedback Issues
1

I wanted to start a topic to capture issues, specifically to MetroX, users have seen in the most current RevoScan 5.8.5. I have not wanted to downgrade to 5.8.4 because the tracking is much better in the new version and capture is quicker. Purpose is to make sure all know issues get captured for the Dev Team to address in the next version. Please list hardware you have and issues you have encountered.

Computer: Dell Precision 7560, CPU-Intel Xeon W-11855M, GPU- Nvidia RTX A3000, 64 gb ram

I have seen:

  • Random software crashing, more common with higher frame counts
  • Blue screen of death crashes.
  • Laser shutting off. Have to restart software and unplug/plug back in scanner
  • Freezing, seems to happen more commonly in Parallel line mode
  • Not saving Rename of Global marker scan. Have to go in and do it two times.
1 Like
2

I haven’t experienced any issues with 5.8.5. I had some issues a few versions ago though. It seems to be dependent on various user computer setups mostly. They must have to try to account for all the different setups out there when developing I suppose.

Computer: Windows 10 pro, CPU- Ryzen 7 3700x, GPU-RTX 2060 super, 32gb ram, 1tb m.2 ssd, Spacemouse.

MetroX from kickstarter that was recalibrated with 5.8.5.

Some scans I have done to push the software for operatablility are as follows: Cross line mode 3 total scans of just over 25k frames each and then merged and meshed. Parallel mode 2 scans over 20k each and merged. Full field feature and marker tracking with over 1600 frames. No turntable tries.

So at least for a system like mine there haven’t been any issues but that doesn’t mean much as they have said they know some bugs. Just wanted to throw this into the mix as another data point for revopoint.

3 Likes
3

I have had the same issues with the “Silent Crashing” I haven’t tried other modes yet but for me, its laser scanning. Gets to about 15000 frames and just closes. I have had this issue before, it seems every other update fixes it, then on the next update it comes back.

Processor AMD Ryzen 9 5900HX with Radeon Graphics 3.30 GHz
Installed RAM 48.0 GB (47.4 GB usable)
Storage 954 GB SSD SAMSUNG MZVLB1T0HBLR-00000, 954 GB SSD SAMSUNG MZVLB1T0HBLR-00000
Graphics Card NVIDIA GeForce RTX 3080 Laptop GPU (16 GB), AMD Radeon™ Graphics (496 MB)

4

I’ve had similar problems with version 5.8.5 laser scanning in CPU mode. This version is significantly better and much faster but it is very sensitive when it comes across areas that might not have sufficient markers. Previous versions would just give you a warning but this version has a nasty habit of just crashing. On some occasions it has saved the scan to the time of crashing but on some occasions I found that it lost the whole of the session. It would be nice if this issue was addressed so that a warning is given without crashing.

5

This is true, it does seem to happen more often when the i get to an area that may be sparse in markers. I have not lost any scans yet. When I start it back up I have the scan at the point it was before the crash. I havent had good luck going back in to the scans and collecting the rest of the data. I usually have to start over. If its at a point that was close enough I’ll just keep it.