For some reason flat surfaces in WIP 8 won’t show isocurves here. Either deg 1 or higher, when perfectly flat no isocurves are visible. Changing their density makes no difference. Only borders can be seen. In all viewports and regardless of type of display used. Even when I open older file ( v7 ) flat surfaces are now without isocurves.
This is a new feature we’re experimenting with, and it will most likely eventually move to display settings.
You can set it in advanced settings with Rhino.Options.Display.ShowIsocurvesForFlatBrepFaces
Yes. This is a new feature. A growing number of users are modeling architectural looking objects with a lot of boxes and planes. In those models, the extra isocurves are noisy and unnecessary. But turning off isocurves globally makes it difficult to look at non-flat things very well.
This is an attempt to clean up the display for scenes with many flat objects. We plan for this to be the default in Rhino.
It’s true that it’s different: is it a problem for you, or just a curiosity? If it’s a problem, how?
It will be a problem for me if the isocurves at interior knots vanish. I use those isocurves to let me know how many spans a surface has and where the knots are located. I suppose it will okay as long as there is an option to retain them.
Do you frequently have interior knots on planar surfaces?
Thanks guys.
I don’t do architecture and I like have my isocurves showing. Old habit I guess. Making it as an option is fine with me as long as I can have them back.
I like this change!
Maybe only Deg 1 could be shown without Isocurves?
Sometimes inadvertently, and then isocurves at knots alert me of the fact.
Sometimes deliberately when I plan on modifying the planar surface to be non-planar. In those situations the isocurves at knots show me if I need to modify the number and location of interior knots.
Good to see that if I modify a planar surface in a joined polysurface and make it non-planar, that the isocurves reappear on that surface - good warning indicator. It is a bit disconcerting however to have them show up only on that non-planar surface in the joined object - not sure it that will confuse people.
I generally work without isocurves on anyway, so it’s not a real issue for me.
_Smash
Sometimes people try weird things on a FlowSrf’s flat base to correct a distortion of a flowed object. I’m not saying that it ever works…or that losing iso visualization on a planar srf is a big deal. Just saying weirdos like me exist.
In other cases, having a visual indicator that something is non/planar might be nice.
Yes - those are important points. Also… having isocurves behave differently on planar and curved surfaces is confusing. The user looses control.
Setting isocurve density to “0” is IMHO the best solution. Same effect. I would make that the default setting. No need for a new default.
I completely agree with this!
The only problem with this setting (in the properties panel) is, that it will be disabled (Rhino 6 Mac) if your selection has non-surfaces in it. So I would make sure that this setting is always available, if not already (Rhino 7, 8).
I actually disagree. Having isocurves on curved surfaces is useful and valuable.
Well… I 1000% agree with this also!
My point was that if someone doesn’t like seeing isocurves, there are plenty of ways hiding them already (isocurve density, custom display modes).
Also I like to point out that having isocurves on flat surfaces is very useful and valuable too! For example, you can select and sub select surfaces in wired and ghosted display modes by clicking the isocurves. This is very useful and valuable!
And If you decide to through with this new setting, my vote is on having it off by default Surface isocurves are the heart and soul of Rhinoceros
I agree on having Isocurves is useful and valuable.
I can add that would be even better to being able to use them like subobjects (similar to edge). For a beginner is confusing to see them and not being able to interact.
hi @Micha this has become a display option