Hallo,
Could anyone help me how to get rid of “doubled surfaces”?
After aligning the photos i got more components. To merge them i´ve add some control points but realigning components i got some weird double surfaces. Even after adding much more control points, at least some small part “jump out” of the correct surface.
The pictures for this project were shooted with two different cameras. Could this affect the result?
Thanks a lot
Hi Tomas
Mixing of different cameras is not a problem here. But I can see a lot of control points with a high reprojection error. I highly recommend you to align a subset of images ( per camera ) and use them as COMPONENTS. It is much safer ( alignment quality ) and faster than trying to align all images at once.
In this case, try to use the POINT LASSO for the ‘flying‘ points and then use FIND CAMERAS to see which cameras are incorrectly aligned. The next step is to add some control points to get the cameras aligned properly together. And get at least 3 images per control point so that it can work properly, if you place them in COMPONENTS, then you need to have them in at least 3 images per CP.
Hi Wishgranter,
thanks for your quick answer.
Im still quite new in RC so i didnt now i can align subset of images. Could you please explain the way how to do it, and also how to manualy create a component from choosen images? (if i understood you correctly)
Or is there any tutorial which you could recommend me regarding this topic?
You are right there are many reprojection errors, but i have in every control point(43 points) around 20 images, so i tought its not a big problem if one or two shows an error. I gues i should quit them from the control point group.
Thanks
Actually I’m having a similar issue at the moment with the control point errors.
Cheers for the tips, I’m just looking into how to rectify this now 
The CP errors show the distance from where the software thinks the CP should be on the image to the spot where you marked it.
That can either be caused by you (misplacing the CP slightly, which is easier than one should think) but since you report double surfaces that indicates that the images are not aligned properly.
Once you are certain that the CPs are placed absolutely accurate, then you need to hit the align button again.
If everything goes to plan the errors should be substancially smaller, ideally <0,5 px.
If not, then your model is not ideal - either not enough coverage, wrong angles or too many problem areas like unicolored surfaces, glas or moving objects.
I think that components are explained in the offline help.
Either you put only a limited number of images into a new project, align them and then export them (workflow - export - registration). Make sure the right component is selected. If you only want a part of the aligned cameras, select them beforehand and only the selected ones will be exported.
Once you have created several components, import them (workflow - import - component) into a new project.
In the alignment settings set “align only components” to true and hit the alignment button.
If everything has been done properly it should then create one big component with all cameras.
Of course, there needs to be enough overlap between the individual components…
Many thanks.
I can’t do much right this second as I’m still calculating the large scene.
I’ll try and include a screenshot shortly.
In my case the alignment point cloud looked fine, very good and even in the draft reconstruction it was fine. Only when I hit ‘normal detail’ that it created a bit of doubling in one section. I just wanted to tidy that up for a cleaner model to look at
Since the software is doing a similar calculation to matchmove software (I only presume), perhaps if we are out with our control points there could be an indicator as to where the software assumes it should be.
I have this in 3D Equalizer (as a representation of solved 3d poistion and 2d tracked position) but where beginners fail here is assuming the rest of their solve is good, and it usually isn’t.
Just a note, I’m a matchmove artist (of 6 years professional), so I should be able to line things up but every now and then, coffee isn’t working and we all make mistakes :lol:
Hey Robo,
no problem - I still don’t know a quarter of this software’s capabilities myself!
I know that some features are hard to find since the GUI is a bit unique.
I think what you are looking for is unter scene - tick residuals (for each window individually) and it will give you orange lines representing the error…
Hi Götz,
Thanks a lot for you advices. I dint have time to test it yet but it sounds like a good solution and exactly that what i was searching for
I will also post here the result if i will be so far.
Hi Thomas,
oops, just noticed that YOU are the TO…
But all that matters is that it helps!
Götz Echtenacher wrote:
I think that components are explained in the offline help.
Either you put only a limited number of images into a new project, align them and then export them (workflow - export - registration). Make sure the right component is selected. If you only want a part of the aligned cameras, select them beforehand and only the selected ones will be exported.
Once you have created several components, import them (workflow - import - component) into a new project.
In the alignment settings set “align only components” to true and hit the alignment button.
If everything has been done properly it should then create one big component with all cameras.
Of course, there needs to be enough overlap between the individual components…
Hi Götz,
coming back to you a bit later but meanwhile i tryed your suggestion and it really helped.
I can still find some “double” surfaces but the offset of them is much smaller - can be also a problem of the shooting process. But the result is good
Thanks again.
Hey Thomas,
glad it worked!
And thanks for the feedback!
Yes, I was struggling with that too at the beginning.
It happens when those surfaces are covered in two parts of the model that aren’t connected properly.
If you are lucky, RC will filter one of them out when reconstructiong the mesh…