@pascal @brian,
I’ve found a strange issue that seems to happen in both Rhino 7 & 8.
Surfaces that have their control vertices moved using keyboard nudges don’t cause the render mesh to update.
In the attached image, the surface on the left is a 2 x 3 degree planar surface. The middle surface has had an interior vertex nudged upward using the “Page Up” key. And the surface on the right has had a vertex moved up the same distance using the gumball. ToggleRenderMesh is activated so you can see the wireframe of the render meshes. As you can see the render mesh of the nudged surface (middle) still has the same render mesh density as the planar surface on the left. While the surface on the right has automatically updated to the mesh tolerance I have set.
Is this a bug? or is there a setting I can turn on that will force the render mesh to update if a surface control point is moved?
This is a big problem when I am trying to adjust surfaces to match scanned mesh data. I set my render mesh to be within 0.001 mm of the surface, but if the render mesh doesn’t update, then I am potentially much further off than what I am seeing. I have discovered this issue in the past sometimes when cutting sections and the section lines wouldn’t follow the render mesh - assuming that it was a mesh tolerance issue, I would increase my render mesh tolerances, which would force the render mesh to refresh and then I would readjust the surfaces.
RefreshShade is a helpful work around, now that I know what to expect. But it would be better if there is way to make the render mesh update if a control vertex is modified.
Thanks,
John
rendermesh bug.3dm (654.7 KB)
