I suspects the surface has some bug, the uv direction should be perpendicular all way around, but it’s not, and the surface display is abnormal.
The file is from my colleague, I don’t know how it happened. I could recreate the surface from curve.
Any suggestions to fix the current surface? Wild guess which surface operation brought in the bug ?
It was an architectural model, the original surface was far away from origin, I have moved it back to around origin.
Thanks. My first post.
debug_01.3dm (69.8 KB)
Hi and welcome -
Since the surface is now out-of-context, it’s impossible to tell what the correct fix is.
You can use the
Untrim command on the edge and that will create a surface that corresponds with the displayed surface, or you can run
DupBorder, explode the resulting curve and use
EdgeSrf on these 4 curves. That will give you a surface that corresponds with the visual edges.
Possibly a “far-from-origin” trimming issue in Rhino 6. Without having a model in the “pre-bad” state, it’s impossible to know for sure.
You could try
RefreshShade to see if it’s just the render mesh (which was probably created far from origin) being messed up.
Tried once, not lucky.
Above quoted method helped.
Thanks. Untrim method has brought the face to normal display.
Then I try to dup edge from the top and bottom;
bring the top curve level up with the bottom;
then extract control polygon from both curves;
“What” display info, indicates the control points of blue curve (from top) and red curve (from bottom) have same xy coordinates.
Should it be the case? As the curves are different from eyeball telling.
Is it a bad (impractical) method to judge 2 curves identical from its control points?
I figured out. The weight of one of the control points is different.