I have an Inspire2 and I’m using Revo Metro 5.8.4. I’m trying to scan an object that will scan nicely as a top and bottom view, then merge those.
I have scanned the top view, then taken it through the whole process to get a nice clean mesh from it, including cropping off many points that were outside the object. The final model on screen is a perfect scan from the top only.
The I did the same for the bottom view, and got it to the same point.
When I try to merge those models it seems to be using the results from earlier steps in the processing sequence of each and bringing back lots of blobs of data that were clipped off in the source models, making the end result a merged model that’s worse than either of the sources.
You need to have the same features in the top scan and the bottom scan to be able to merge it , they need to have the same features to be able to be merged .
Scan this object in vertical position where you can see partial top and bottom and merge it with the 2 parts you already scanned .
This way you get the needed features that the merge tab need for references and where to place exactly the scanned too and bottom parts .
It merges perfectly well when it comes to alignment, it’s just that some noise is included that wasn’t there in the top or bottom processed scans. Here are some screenshots, the first is the result.
You need to clean the merged scan after merge , remove lose points and duplicate overlapped points and then mesh it at the same GRID settings you used for Fusing .
The extra noises comes from the extra points that was not cleaned and if you used greater GRID settings than your fusing settings .
You also need to do original cleaning of the fused scans before merging … Because only fused point cloud is used for merging .
So I need to not bother cleaning up the partial scans, then only clean it up after the merge? You can see the models that went into it didn’t have anything where the extra bits have appeared, that’s why I think it’s using the point cloud or uncleaned mesh from the partial scans instead of the end result of each.
You can try to clean the merged scan and see if it cleans up nicely before meshing , if not , you need to clean the single scans and remove everything what don’t belongs to the scan and merge again then clean after before final meshing .
The merge tab using the fused point cloud , if you did not cleaned the fused point cloud it will show the extras .
It do not used the raw scan for merging , only fused point cloud .
Ah, OK. So it’s not even worth working on the mesh until after the merging, just get the point clouds as clean as I can then merge them. That makes sense, but I don’t think I ever saw it said like that before.
Thanks.
Edit: I tried cleaning it up at the point cloud level instead of the mesh and it merged much better.
I’ve had a look at a few now. The quality of the videos is very variable, more recent ones are better!
They do all stop at the point cloud now I look, but I didn’t see anywhere saying you couldn’t merge meshes. It was just a bit of a surprise that the view I saw on screen of the two partial scans was not the same things I saw merged in the end result. I know now.
That’s a common knowledge no matter what scanner you are using , for accuracy , precision and technical side meshes are never merged .
Point Cloud is one of the most important element after scanning , anything after that is processing that can lead to lose the accuracy and precision . Because of the huge size of a mesh , merging them would take a very long time and consume a huge resource of the computer , and it is not worthy losing the accuracy and precision .
