ReduceMesh API vs Manual Command: Inconsistent Face Counts in Rhino 8

I am experiencing an issue where the face count of a mesh object after using the ReduceMesh command manually in the Rhino 8 user interface (UI) is different from the count achieved using the corresponding API (C# Rhino Inside).

I am using Rhino 8 and applying what I believe to be the same reduction parameters in both cases. However, the results are inconsistent. This suggests there might be some default settings or post-processing steps in the manual command that are not being automatically applied or correctly replicated through the API.

Could anyone please provide guidance on how to match the API results with the manual command results, or point out if there are specific parameters I need to consider when using the API for mesh reduction?

Hi @Mukesh,

After the reduction, the command converts triangles to quads.

mesh.Faces.ConvertTrianglesToQuads(5.0 * Math.PI / 180.0, 2.0);

Perhaps this is the difference?

– Dale

Thanks @dale,

I tried running this method after ReduceMesh process. Unfortunately, I am still facing the issue.

mesh.Faces.ConvertTraianglesToQuads(5.0 * Math.PI / 180.0, 2.0);

Note: Previously I used below parameters to convert triangles to quads.
mesh.Faces.ConvertTraianglesToQuads(180.0 * Math.PI / 180.0, 0.1);