In 30% of project i scan, i get "point cloud fusing failed for some, not all of the scans. ive had this occur on 2 different comptuers, im using metroy ultra
I can open the point cloud data for those directly without any issue. I have literally no idea what the pattern is for why this happens, but its incredibly annoying as i can’t merge those scans easily.
The point cloud also can’t be exported from directly in the project
Hi @bxp
If the point cloud is not generated proper it can’t be exported .
Please contact customer@revopoint3d.com for technical assistance
You can I include a link to this thread as reference
I am not exactly sure what is happening , if you run out of RAM due to high fusing settings or anything else but that is not a normal behavior .
Try to fuse the raw data manually and see if that project is fine and if that issue happens only with the batch processing , if you can please monitor the RAM usage while fusing , with Metro Ultra the files may get very big and consume all system RAM but that is only my guessing , the technician will check out your logs to see the real issue so I am not going to speculate here on that .
fusing cannot be done manually, the progress bar immediately goes to 100% then it shows error
Hmmm that is a problem here , the project may be corrupted somehow , please contact customer@revopoint3d.com
The office is open right now and technicians available
You can even zip up the troublesome project and send it with your email for faster response . Plus include link to this thread as reference. Also if you can screenshot the error you got would be helpful , screenshot option is available also in the software .
Please let me know if you were take care of successful, by the support.
What services can you access? The data would exceed the email size limit.
I normally use Google DRIVE
If you do , remember to set the permission to Access" Everyone with the link " then share the link
AI Used To Rephrase & Format
**
I had this exact issue with Google Drive and Revo Metro/Track scans - here’s the fix that worked for my captured data.**
I believe the root cause was saving my project folder to a Google Drive-synced location. Every time I started my computer, I’d get this Google Drive warning.
It said files couldn’t be synced and were moved to the “Lost and Found” folder. In Revo Metro/Track, the raw point clouds would preview fine, but fusion would often fail or go straight to 100% with an error - exactly like you described.
Close Revo Scan/Metro/Track completely first.
Click “Review files” on the Google Drive popup (instead of “Move all to Desktop”).
You’ll land in the Lost and Found folder, which looks something like this:
It contains several large .dataset files (usually named frames (long-number).dataset) plus a small lost_and_found_data.txt.
Open lost_and_found_data.txt in a text editor and stretch the window very wide. Each line shows a pair of paths separated by a comma.
For each affected project:
Once all the frames have been restored to their proper project folders and renamed, reopen your project in Revo Metro/Track. You should now be able to fuse and mesh normally.
If you don’t get the Google Drive popup on startup, just search your computer for frames*.dataset to locate the moved files.
This recovered all my scans without data loss. Hope it works for you too.
Also, If I set my project folder to a non-synced location, I don’t have this issues. I believe I could also pause Google Drive from syncing during my scanning process to prevent this, but I’m still testing that.
-Jeff
Hi @Jeffrey
Thank you for your detailed reply but that is not what we discussing here or have any problem with.
My mention of Google drive was only for saving zip file for sharing and absolutely not using as a project location in Revo Metro.
An active projects should be not saved to any other locations than the main system hard drive .
Hi PUTV, I do get where his idea with GDrive stems (might not be the case here, but still), I also had forgotten about a certain folder being synced at one point. If not properly set up, it could try to sync both ways and it would corrupt files at one point… 
MS Defender can also be a B… sometimes when not excluding applications or folders with high volume data applications - might be worth to take a look at MS Defender exclusions, as those can corrupt files which are being altered a lot in a single place - talking from experience with different CAD systems unfortunately 
That is true , that why I don’t use any other folders to save my projects until they are not finished , after that I store them on my backup HD , however they should be copied back to your system when reused for best performance .
I have 3 machines running without any issues ever , even a portable HD was an issue so I keep new projects where they belong until they can be closed and archived.
The workflow is simple but not everyone follows it , saving the projects on external source will automatic limit the capacity including processing , scanning etc .
I made that mistake 4 years ago and learned from it the hard way , looking for fixing other things not knowing that all the issue was simply external HD .
Hi @PUTV ,
The exact issues @bxp described 100% matches with what I was dealing with. Some would fuse and others would fail. For me, saving my project to a local hard drive location that will then be synced by Google Drive was the issue. I’m not claiming that is what bxp has happening, just how I was able to locate my missing/corrupt frames.dataset and how to move them to the correct location and save the work I already did.
-Jeff
Hi @Jeffrey
Yes but @bxp did not used Google Drive , I only mentioned it so he can share his zipped project with the customer service .
Maybe @bxp use another location where the projects are interpreted like OneDrive or other external drivers but he did not mentioned anything of it, but it was not Google Drive , however your explanation my help someone else in the future .
Thank you !
thanks! This helped me solve the issue.
The frames dataset for the problem scans were for some reason saved as frames-.dataset , and then a very small “frames.dataset” file was in the same folder.
All i did was follow your advice, remove/rename the small-filesize frames.dataset to something unusable, and then also rename the very large file, frames-.dataset to simply frames.dataset.
And this fixes the fusing, which then works correctly.
