Issue #1: When I set a preview for the “ReduseMesh” tool and I hit “OK” to convert the mesh, for some reason Rhino will not apply the already calculated geometry. Instead, it calculates it again, taking double time than necessary compared to direct conversion without a preview. Why Rhino needs to calculate exactly the same reduced mesh, in order to apply it to the selected mesh model?
Issue #2: After the mesh count is reduced, every polygon now has its own shading, producing uglier look instead of a smooth one. In my opinion, Rhino should preserve the smooth shading of the converted meshes.
3ds Max, for example, has a tool called “Smoothing groups”. It lets you set the same shading to individual polygons or the entire object with a single mouse click. Super convenient and does the job perfectly.
) is that the preview calculation takes place in the graphics card, the actual calculation is then done once more by the processor, or the data has to be fed from there to the ram, which takes some time either, i am not sure anymore but believe its any of these, but yes it seems counter intuitive.