I’m using ExScan Rigil 1.1.4.10, and I ran into a problem with a scan I did yesterday. The point cloud looks to be fairly good and complete, but I’m getting large, vaguely round holes in the generated mesh, irrespective of what settings I use.
This is based on a composite of 5 laser scans in different orientations. Each was done using global markers located on a turntable, no markers on the object itself. The option to fill marker holes was turned off in the meshing dialog, but it almost looks like the software is ‘detecting’ and removing markers that aren’t there. (I exported the scans and loaded them up into Geomagic DesignX, and it meshed them just fine, without any of these holes).
I went back and reprocessed some earlier scans done in the same way, but using the new software. I don’t recall having these holes previously with these scans, but I got similar results with what are much more clearly circular holes in parts of the scan, where the source point cloud looks fine.
The holes also don’t seem to correspond to the locations of any of the global markers in any of the source orientations, either. Any ideas what is happening?
Your data looks mostly good but I want to know whether you have brushed the data into total blue when you do the scanning? If possible, you can share your project to us so that we can see if we can reproduce your issue on our side. You can visit New tab and our engineers will help ASAp
Thanks, TC! I’ll send you the project tomorrow when I get back to the office. What exactly should I provide - a zip of the project group files, or is there a way to export the whole project group from ExScan?
Even if the data wasn’t great, it wasn’t ‘not great’ in exactly circular patches - and DesignX meshed it just fine. So if ExScan is protecting me from myself, it would be good if there way that I could turn that off I’ll look forward to hearing what you find out once I get the source data to you.
Just to add to this, in case anyone else sees the same thing. After more testing, it turns out that the meshing process is creating holes in the mesh as part of ‘deleting’ global markers.
This seems to be a bug, because the markers in question weren’t on the scanned part, but rather near to one of the captured views of the part, on the turntable I was using.
It seems to be projecting the markers onto nearby mesh, at the end of the meshing process - because it was also creating the holes in other aligned scans that weren’t near those global markers when scanned (since they were scanned in different orientations, on other parts of the turntable). If it had just made holes in one of the scans, and then allowed them to be filled in with data from other overlaid scans, it might not have been noticeable. But it punched holes in all of them.
I was able to confirm this, by going in and manually deleting the offending nearby global marker points associated with the scan that was causing problems. The data then meshed just fine, without any round holes being introduced.
I’ll look forward to hearing what you find out once I get the source data to you.