Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with 2021.1.0 (2020.1.1 gives other/better results)[question] #1380

Closed
datavizzard opened this issue Apr 16, 2021 · 7 comments
Closed
Labels
stale for issues that becomes stale (no solution) type:question

Comments

@datavizzard
Copy link

Describe the problem
Import images into Meshroom 2020.1.1, 2021.1.0, process wirh default settings, no changes.
Image orientation is not recognized in both versions, problem keeps popping up unfortunately.
Pointcloud in 2020.1.1 is more dense, the Mesh in 2021.1.0 has a lot of holes.

pointcloud

Left ist 2020.1.1, Right 2021.1.0
2021-04-16 14_45_09-MeshLab 2020 12 -  Project_1

Dataset
Data set I can also provide request at short notice

Desktop (please complete the following and other pertinent information):

  • OS: Win 1909
  • Meshroom version: 2020.1.1, 2021.1.0

Additional context
Sometimes, but not allways "Fill Holes" in the Texture node fix it. I noticed that I noticed that the 2021.1.0 introduces holes around an object earlier than it was before. I think this is more a bug than a question, even though I marked it as the latter now.

I noticed that Reality Caputure sometimes preprocesses the images and makes them clearer, which can be seen later in the finer textures. Is this perhaps as a preprocess a solution for a node in Meshroom that takes over beforehand to then refine the results?

@fabiencastan
Copy link
Member

Pointcloud in 2020.1.1 is more dense, the Mesh in 2021.1.0 has a lot of holes.

Do you mean in output of the SfM? Could you provide numbers? Did you change default parameters?

I noticed that the 2021.1.0 introduces holes around an object earlier than it was before.

This may come from the new post-processing of the tetrahedralization.
To get previous behavior, change the following parameters on the Meshing node (in the advanced params):

  • nbSolidAngleFilteringIterations=0
  • InvertTetrahedronBasedOnNeighborsNbIterations=0

@datavizzard
Copy link
Author

Pointcloud in 2020.1.1 is more dense, the Mesh in 2021.1.0 has a lot of holes.

Do you mean in output of the SfM? Could you provide numbers? Did you change default parameters?

I noticed that the 2021.1.0 introduces holes around an object earlier than it was before.

SFM, no a single Value changed. Default Settings.

This may come from the new post-processing of the tetrahedralization.
To get previous behavior, change the following parameters on the Meshing node (in the advanced params):

* nbSolidAngleFilteringIterations=0

changed

* InvertTetrahedronBasedOnNeighborsNbIterations=0

Didn't find this one in Advanced Attributes, do you mean this?:
2021-04-16 15_45_11-C__PhotoGram_frbg_Statue_pol Kirche_2021 mg_ - Meshroom 2021 1 0

@fabiencastan
Copy link
Member

SFM

How many landmarks?

InvertTetrahedronBasedOnNeighborsNbIterations=0

Yes

@datavizzard
Copy link
Author

landmarks

0, Just plain Photos from Object in Free roam, SIFT

BTW, here the results with the both settings you told me to change. Looks like its getting worse, take a look for the Ground.
2021-04-16 19_29_12-MeshLab 2020 12 -  Project_1

2021-04-16 19_28_57-MeshLab 2020 12 -  Project_1

@datavizzard
Copy link
Author

I mentioned it before but you can see how the bottom gets a second layer from the bottom as if it were a balloon. On the statue model it is very flat and very hard to remove. I have to test this again but somehow SFMTransform has a negative influence on the result.

2021-05-01 23_41_44-C__PhotoGram_Baum_baum mg_ - Meshroom 2021 1 0

@stale
Copy link

stale bot commented Sep 6, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale for issues that becomes stale (no solution) label Sep 6, 2021
@stale
Copy link

stale bot commented Sep 21, 2021

This issue is closed due to inactivity. Feel free to re-open if new information is available.

@stale stale bot closed this as completed Sep 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale for issues that becomes stale (no solution) type:question
Projects
None yet
Development

No branches or pull requests

2 participants