I’m finding that the Mesh.QuadRemesh API in Rhino.Inside produces a different mesh (different face and vertices count and Normal’s are missing through API) results than running the QuadRemesh command in the Rhino UI, even with the same target object and parameters.
My goal is to replicate the manual Rhino UI results deterministically within my Rhino.Inside C# application.
Rhino version: Rhino 8 Rhino.Inside Nuget: 9.0.5 beta Source Mesh : 92 vertices, 100 faces Rhino UI Result : 106 vertices and 103 faces with normal
Rhino.Inside API: 116 vertices and 114 faces without normal
Thanks for the response @Trav, My main focus is that the number of vertices and faces I am getting are drastically different through the API compared to the Rhino UI.