feature requestgood first issuemesh
Metriche repository
- Star
- (10.036 star)
- Metriche merge PR
- (Merge medio 23g 3h) (5 PR mergiate in 30 g)
Descrizione
Checklist
- I have searched for similar issues.
- For Python issues, I have tested with the latest development wheel.
- I have checked the release documentation and the latest documentation (for
mainbranch).
Proposed new feature or change
In many mesh processing workflows, UV coordinates are not preserved (e.g. mesh simplification). UV coordinates are required for many downstream tasks. One way to propagate UV coordinates through mesh processing workflows is by copying them from the original mesh. Here is an outline:
- Mesh A is processed to mesh B. Mesh A contains UV coordinates (and textures), but mesh B does not have them.
- Call
meshB.InterpolateTextureCoordinatesFrom(meshA). This does:
- Create a ray casting scene with mesh A.
- For each vertex in mesh B, find nearest point in mesh A.
- Assign UV coordinates of nearest point in mesh A to the vertex in mesh B.
- Optionally, copy over any textures from mesh B to mesh A.
References
No response
Additional information
It may be necessary to convert from per-triangle UVs to per-vertex UVs (or vice versa). The following code shows an example of how to make that conversion: https://github.com/isl-org/Open3D/blob/main/cpp/open3d/visualization/rendering/filament/TriangleMeshBuffers.cpp#L614