The lines were created automatically through a script.
If I suspect correctly, there is a bug with regards to how Rhino8 derives the “direction” of the line.
Because if I remove the lines of the “empty” face and redraw a polyline (and then explode it) it works correctly.
Anyone already understood why “MeshFromLines” do not work in Rhino8, but the performance in Rhino7 is (almost) OK?
@wim thanks for the reply. I can see it is open to the public. But it is an internal (McNeel) decision whether it is going to be fixed or not, is this right? It’s not up to someone else, unless I miss something here and people outside the organisation can contibutte to fixing bugs…
A good answer would be to inform us whether effort is being put on this bug or not, to know what we expect. And if effort is being put, if it is a difficult issue to solve.
In any case, because I don’t know exactly how you work internally, I can volunteer myself and help you fix it. Is there such an internal process who can let someone volunteer to McNeel?
I’m the developer of this tool, which, in turn, is entirely a product of Weaverbird development. Nobody originally asked, other than me.
Yes, and I try to be very responsive with bugs. I fixed one other bug in Rhino 8 and then this one appeared; I can tell you I don’t immediately know why it appeared. I know that this feature doesn’t exist in these terms anywhere else. When I was writing Weaverbird, I wanted it badly and there’s not much literature on this topic.
While I’d tend to agree with you, you did not really mention that this was an important bug for you, or why, and there’s no indication that more people were impacted. Also, because you didn’t mention “the why”, it appeared this was a general “underperform” complaint, which is lower in importance than “regressions”. This is why, this went into the “long list”.
Since you are asking, I’ve put this one bug into my “shortlist”. I have a hard mesh Boolean winding direction problem that I’m working on, and it will require some of my attention next. But after that, I’ll pick this one up. Pinky promise
I hope this explains, at least a little bit. Sorry if this disrupted your work. And thank you for reporting the bug so well. Please keep on doing this.
Unfortunately not. The mesh created with “MeshPatch” is far from the expected mesh. In addition, “MeshPatch creates” many “extraordinary points”, adding many undesried lines on my mesh, which I try to avoid, that’s why I have been using “MeshFromLines” since all the way back to Rhino5, back then with Tspl plugin.
Hi @piac, I just wanted to say that it’s fantastic to have Mesh.CreateFromLines natively in RhinoCommon now. It’s super useful for many day-to-day modelling cases! That said, it would be nice if the method could take a Python list with Geometry.Line. I might be wrong, but it looks like one has to use a typed Geometry.Curve .NET array/list:
