I am having massive problems with Revo Metro crashing and now also making previous scan unusable because the software is constantly crashing.
Whenever I try to fuse a scan, the program will just shut down. I thought that maybe my processor wasn’t fast enough (i5 12600k) so I replaced it with a new one (i9 14900k) and the problem is still there.
Smaller scans go through the fusion process successfully most of time but will also crash here and there.
I tried fusing a project I scanned last week and after the revo metro crashed, the .revo file won’t open now. I can still open all my other projects but this particular one just won’t load into the software. No matter if I click on .revo file or say open project in the software.
Your problem is probably your RAM and nothing to do with the CPU as I use i9 14th generation myself , I have no problems processing 3 times bigger scans with 64GB on board . Actually the maximum I processed was 150 milion polygons with 64 GB of RAM
The project that you trying to open got corrupted while crashing , I advice to save your projects before each processing steps just in case to preserve the raw data at least , usually corrupted projects can’t be recovered . But what you can try is removing the ply files created from processing of fusing or meshing and try to open the project again , this way the project open at the RAW level but not always guaranteed.
32GB of RAM looks like a lot , but if you see how much the system use, your graphic card and the project/software , you have very little left .
In this case after scanning save manually the project , close the software , after that open the software again and your project and try to process again , this will give you extra free RAM for processing .
If after trying all of this , you still have issues please contact customer@revopoint3d.com
They will check the logs and let you know exactly what is happening and confirm if it is RAM or anything else going on in your system.
I have similiar specs and stuck with 32gb ram. Been waiting to see if ram was going ro come down. I’d like to go 96gb, but it’s almost the price of a laptop now.
I can scan fine, just getting crashes 80% of the time when I try to fuse the scan. I’ll reach out to the support email because the scanner is unusable with the way the software behaves currently.
I did not refered my tips to scanning but only to processing that you should know and try out .
You have minimal requirement of RAM that is needed to run the processing but not optimal , so unless the logs review some other things I don’t think it is the software issue as it works just fine with recommended system.
Yes, my computer meets the minimum requirements in one aspect and exceeds it in all others.
No matter what, the software should never just crash without notification and it should absolutely never corrupt any scan files. That’s just unacceptable.
I am sure we’ll figure it out, but this isn’t a performance issue, it’s a basic functionality issue.
slowdowns, error messages and so on are all fine, crashes and file corruption is what costs you customers in the end.
I am using a Metro Y pro and I like it so much I ordered a Metro Y Ultra. You guys are very responsive and that’s great, looking forward to seeing what you all turn the scanners and software into. Currently, you have the most compelling offers in this segment.
Yeah, I understand, I haven’t seen anyone have these issues with the recommended 64gb.
I’m not mad that it doesn’t perform to it’s max ability, when I haven’t met the recommended specs. I haven’t personally had an file corruption, so that is a bit different.
All the processing is heavily ram dependent and less so CPU and GPU. I often follow it in the resources tab. Every now and then the cpu and GPU might have a quick spike, but I have never seen them go above 9%.
Ram on the other hand stays between 70-90%.
What I’m mad about is 96gb ddr5 is $1000. When it used to be $400-450.
It was designed this way a 4 years ago and everyone disliked it very much , for the same reason the limits was removed allowing freedom , not a software in the word will warn you when your RAM is about to crash your system, not even the Windows system will warn you. You need to monitor it if you have not enough in your system .
I understand your frustrations but there is no way to make it better , minimum requirement allow you to run it but it is not fully recommended and physically it is impossible to change it other way than buy more RAM for your system.
However 5 million points are very small scans , I still suspect something else on the hand and that has less to do with the software, something is draining your system.
As I mentioned before I do not experience any of it with my recommended system so I can’t recreate your issues but from experiences from other users that used 32GB of RAM in the past , this is exactly the case.
The System need to reserve the same amount of RAM that your graphic card use , but for processing only CPU + system RAM is used , don’t forget the system also need portion of the RAM so after all you have much less available for processing and it would be never 32GB or 64GB , my system use around 20GB and only around 45GB is used for processing of a very heavy scans , the software itself sometimes use around 9GB before even processing , that why saving it and reopen release huge portion of the RAM to the system.
32GB of RAM in the system will give you around 14GB for processing what in most cases is much to low especially if you use Auto mode as it drain the RAM very fast due to high demand and higher fusing settings .
I am doing scanning and heavy 3D model processing for almost 30 years already , I know well what system can or not .
Hi @NickS big scans around 9 milion and up points, around 50-100 milion polygons after meshing
Smaller below 2 million points and below
I still believe that something is drowning your RAM as 5 million points should be still manageable with your amount of RAM but I can’t put finger on it , you need to open Manager and check it while processing what is actually happening in your system , how much you have RAM left before processing and while processing to find out precisely other way we going to talk and the problem will be never solved .