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

In Meshroom 2023.3 MeshDecimate ignores nbVertices setting #2464

Open
guizy67 opened this issue Jul 10, 2024 · 1 comment
Open

In Meshroom 2023.3 MeshDecimate ignores nbVertices setting #2464

guizy67 opened this issue Jul 10, 2024 · 1 comment
Labels
bug for actual bugs (unsure? use type:question)

Comments

@guizy67
Copy link

guizy67 commented Jul 10, 2024

Describe the bug
In Meshroom-2023.3.0 on linux (ubuntu 22.04 and 24.04), when I set nbVertices to a specific value, the resulting mesh does not match the number of vertices. Typically there is a factor of 2 or 3 times more in my case.

I am using a template file from the command line of meshroom_batch.
Extract of the template file:

        "MeshDecimate_1": {
            "nodeType": "MeshDecimate",
            "position": [
                2192,
                -184
            ],
            "inputs": {
                "input": "{MeshDenoising_1.output}",
                "nbVertices": 32000
            }
        }

To Reproduce
Steps to reproduce the behavior:

  1. Create a template .mg file containing the inputs for mesh decimate, with fixed nbVertices
  2. Run meshroom_batch -p template.mg --images imagefolder
  3. Verify number of vertices and number of faces using Meshlab (or other software)
  4. Number of vertices does not match the value specified in the template

Expected behavior
In version 2023.1.0 the number of vertices exactly match the value given in the template file. This is the expected behavior.
In version 2023.3.0 they are completely different.

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

  • OS: Ubuntu lts 22.04 and 2.04
  • Python version: 3.10 and 3.12
  • Meshroom version: release 2023.3.0
    • Binary version 2023.3.0
@guizy67 guizy67 added the bug for actual bugs (unsure? use type:question) label Jul 10, 2024
@guizy67
Copy link
Author

guizy67 commented Aug 11, 2024

This was an incorrect interpretation from my part. The MeshDecimate node works as expected, but the Texturing node does not. That is the one 'ignoring' the reduction in the number of faces.
I have created a new issue for the Texturing: #2496

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