[FIX] Correct vertex index calculation in meshes_to_subsurface method | GEN-13490

[Leguark]

TL;DR

Fixed a bug in the mesh indexing logic when converting meshes to subsurface format.

What changed?

Modified the meshes_to_subsurface method to correctly calculate the index offset when combining multiple meshes. Instead of using the maximum value in the current simplex array, the code now adds the number of vertices in each mesh to properly increment the index counter.

How to test?

Test the meshes_to_subsurface method with multiple meshes of different sizes to verify that the vertex indices are correctly offset and that no index overlapping occurs between different meshes.

Why make this change?

The previous implementation incorrectly calculated the index offset by using the maximum value in the current simplex array. This could lead to index overlapping or gaps when combining meshes with non-sequential vertex indices. The new approach ensures that indices are properly incremented based on the actual number of vertices in each mesh, resulting in correctly connected mesh structures.

[Leguark]

• [REFACTOR] Optimize dual contouring vertex generation and add vertex overlap configuration #36
• [ENH] Implement surface-based dual contouring with optimized triangulation #35
• [REFACTOR] Modularize triangulation code with helper functions for improved readability | GEN-13490 #34
• [REFACTOR] Optimize dual contouring gradient handling and normal correction | GEN-13490 #33
• [FIX] Correct vertex index calculation in meshes_to_subsurface method | GEN-13490 #32 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Leguark]

Merge activity

• Oct 9, 10:07 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Oct 9, 10:07 AM UTC: @Leguark merged this pull request with Graphite.