combining two scan with marker at different location for full mesh/texture

Suppose we would want a 3d scan with full real 3d texture (so that the marker holes are from 2 overlapping mesh instead of software marker hole filling), is it possible? We have tried the approach but the software marker hole filling/ non filling does not work. The steps to reproduce are as follow:

  1. For the same part, carry out 2 scans with marker placed in different but complementary positions

  2. Manually remove point clouds around the markers (as seen from the next image, the 5 different point clouds on each scan around the markers are all removed)

  3. Manually align the point clouds

  4. Mesh the combined with either marker hole filling on or off

As seen from step(3), the point clouds are complimentary based on the manual removed points around the marker and all marker point cloud are removed. However, when trying to generate the mesh, the option for marker hole filling would either reintroduce the texture of one of the scan showing 5 markers or when switched off will generate all (5+5) marker holes.

Is there be a function to allow the marker to be truly deleted in the scan/point cloud so that the post processing (meshing) side can do it without the marker texture? Or is there a function in the post processing side to extract texture from both scan instead of just one when mesh hole filling is disabled?

Hi, jinyc

The texture of marker currently can not be delete even you delete the point cloud surround markers, our texture mapping is extracting texture from both scan when do mesh hole filling.

We will take your suggestion in consider to check if there is a solution to reproduce the complete texture when there is marker on the surface, it is a difficult task.

If you want to get clean surface, you can stick markers surround the laptop irregularly or put some small crumpled paper ball surround as features for feature tracking to avoid using markers.

Wouldn’t you use the global markers function to accomplish this?

Hi,

to clarify, the texture below the scan 2’s marker are present in scan 1 as the marker in the two scans are in different positions:

e.g. scan1 and 2:

however, when combining the two scan through manual alignment, the texture from scan 1 at scan2’s marker location cannot use scan 1’s texture and result in marker’s texture in scan 2 to be used even if marker hole filling is enabled (bot left picture). if marker hole filling is disabled, then all the maker hole from both scans will be present as shown in bot right picture.

Apologies for the combined picture as new user can only embed single images

I think this is related to the problem I’m seeing in this post:

My case has the additional wrinkle that it’s ‘deleting’ markers that aren’t even on the part being scanned (so I don’t need it to do any marker removal magic anyway), but I’m also seeing that when it is removing those markers, its making holes in every scan, not just the ones affected by the markers. Effecgively its removing the markers from the finished mesh, not the source clouds.

So I wonder… if you’ve manually delete the scanned markers from the point clouds, leaving holes in the point cloud already, can you then go and edit the marker data associated with each scan, to delete the marker points, and then remesh? Without the marker data, I suspect it won’t think it has to make extra holes in things, and will just let the data from the other scan fill in the gap.

I think my case was slightly different. I am not using global markers as the eventual object to be scanned is quite large and there are some repeating patterns in the middle of the object, so markers on the object to do the tracking is necessary. Anyway, the attempt is already made to delete the point clouds around the marker. However, the marker does not get deleted and resurface as texture during the meshing

not sure what’s the issue is

Yes, but it looks like you deleted the markers using rough cutouts from the point cloud? But the resulting mesh doesn’t show those rough shapes as far as I can tell. It looks like the general area WAS filled in with data from the other scan, but then a clean round hole was added back where the marker was? So it seems like it’s sort of doing what you want, but then making new holes? On your scan results screen, you can switch from ‘edit points’ to ‘edit markers’ - it’s one of the tools at the bottom of the screen. And then you can select the bright white marker dots, and delete them. That way the software no longer thinks that there’s a marker that it needs to do something with when meshing happens. Might be worth trying to at least see if that helps.

that seems to almost be the solution, but when trying to delete marker, it says need to keep at least 4 markers per scan. so in the sample scans above originally we have 5 marker per scan, only 1 from each scan can be removed this way

Yeah, I think that’s an unnecessary restriction - seems lie you should be able to delete all of them if you don’t want to use them any more? Hopefully they fix that ASAP. But does that at least solve the problem for the 1 marker you can delete, lol?

i think it cant solve even one marker:

top2 are the original 2 projects opened.

2nd 2 are the ones with the middle 2 markers removed

3rd middle is after manual alignment showing all the point clouds looks perfect

last 2 is after meshing. somehow when using no marker hole filling, the deleted marker mesh appears. and with marker hole filling, the original marker mesh appears. it seems that its the meshing side has some bugs which mistakes its own point cloud as the other’s point cloud that is used to fill its own missing hole

That’s really weird. Why would those white dots reappear in the meshed version? You’ve deleted the dots captured in the point cloud, and deleted the marker position data. I wouldn’t have thought there was any reason for it to think there are dots there… Is there any other scan or marker dataset in the project group? I’ve noticed that it uses every project when meshing, even if they are hidden in the cloud view.

Yeah, its weird. its just these 2 scans.