I read that Rhinocommon is now opensource. For a standalone application, would it be Rhino3dmIO that I use? I’m trying that now but finding I’m missing a lot of the functions, like Mesh.CreateFromBrep. Perhaps there is something that I’m not understanding?
Indeed Rhino3dmIO is open-source, but that supports only reading and writing of the open 3dm file format and “simple” geometry operations that are part of the OpenNURBS library. The more advanced geometry operations, like Mesh.CreateFromBrep are only supported inside Rhino, because this uses the closed-source part. These more advanced operations also include brep and mesh booleans, curve intersections, closest-point finding, etc. etc.
So yes, you can use the 3dm file format and the whole geometry data structure + simple operations that comes with Rhino3dmIO, but you can’t use the more advanced functions. Think of the McNeel perspective: if they would open-source Rhino completely, another company could use their algorithms for these advanced functions and Rhino sales would most probably be affected. These algorithms are typically developed and fine-tuned over years.
That is why I was so surprised to come across an old headline saying RhinoCommon goes opensource… I should have known it wouldn’t include the recipe for the special sauce Nevertheless, the part that is open source will be enormously useful.
By chance, does there happen to be any documentation that lays out the differences between RhinoCommon and Rhino3dmIO?
What is the difference between RhinoCommonMono and Rhino3dmlo by the way?
I did get a couple errors building the project in both VS 2015 and 2017 as shown in images below.
As far as I know there should be no differences between RhinoCommon and Rhino3dmIO. Just think of the RhinoCommon being Rhino3dmIO + “the special sauce”