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

[bug] When Texturing after MeshDecimate, the number of faces on the Textured Mesh does not reflect the reduction from the MeshDecimate node. #2496

Open
guizy67 opened this issue Aug 11, 2024 · 0 comments
Labels
bug for actual bugs (unsure? use type:question)

Comments

@guizy67
Copy link

guizy67 commented Aug 11, 2024

Describe the bug
In Meshroom-2023.3.0 only, the Texturing node does not reflect the reduction in vertices/faces from the previous MeshDecimate step.
In my example, MeshDecimate simplifies the mesh from 110,061 faces to 51,964 faces (based on a setting of 26,000 vertices in the node). The next step, being Texturing results in 94,176 faces instead of 51,964.

To Reproduce
Apply MeshDecimate node before the Texturing node. In the Meshroom GUI (or e.g. Meshlab), compare the nr of faces from the resulting meshes of each step. They do not match.

Expected behavior
As in previous versions of Meshroom, expected behavior is that the number of faces are equal (or show very minimal difference).

Screenshots
Pipeline:
Screenshot from 2024-08-11 16-57-58
Resulting number of faces:
Screenshot from 2024-08-11 16-57-07

@guizy67 guizy67 added the bug for actual bugs (unsure? use type:question) label Aug 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug for actual bugs (unsure? use type:question)
Projects
None yet
Development

No branches or pull requests

1 participant