UV Mapping Alterations Post _SplitDisjointMesh Operation in Rhino 8

[Julio]

Hello,

I’ve recently observed an interesting behavior in Rhino 8 that I wanted to share and discuss. It appears that when the _SplitDisjointMesh operation is performed on a set of meshes with UV Mapping attached, the UV Mapping of each individual mesh piece undergoes changes.

Here’s the process I followed:

1. I started with a set of joined meshes, each with its own UV Mapping.

2. I then performed the _SplitDisjointMesh operation on this set.
3. Post-operation, I noticed that the UV Mapping of every single piece of the now split mesh had changed.

This behavior seems unusual and I’m unsure if it’s a feature or a bug. It’s important to note that this could potentially impact workflows that rely on preserving UV Mapping through the _SplitDisjointMesh operation.

This behaviour does not happen, as expected, when performing the _Explode command as you can see from the image below

Has anyone else encountered this issue? Any insights or suggestions would be greatly appreciated.

Thank you for your time and assistance.

[BrianJ (Brian James)]

Hi @Julio ,
Thanks for the report and question, can you please upload a 3dm file when posting? A good file to see here would be one that has the original mesh with the UVs shown as intended as well as the resulting mesh after SplitDisjointMesh and the unexpected UV change.

[Julio]

Hello Brian,
you can find the file attached here
UV-Mapping-Alterations-Post-SplitDisjointMesh.3dm (781.4 KB)

Thanks for the support!

[BrianJ (Brian James)]

Thanks, filed as https://mcneel.myjetbrains.com/youtrack/issue/RH-82825 for the developers to look into ASAP.

[brian (Brian Gillespie)]

RH-82825 is fixed in Rhino 8 Service Release 10

[Julio]

Thanks! Confirmed the fix in 8.10.24198.10002 on Windows