Show messages: All
1
2-6
From: Michael Gibson
Thanks Brian, it is definitely a bug but quite difficult to fix. The problem is occurring at the poles, one pole has that gap and the other pole has 45 little tiny curves. You can select the little curves by doing a window select.
The pole or "singularity" spot of a surface tends to be a particularly sensitive area for numeric processing.
- Michael
From: bemfarmer
Thank you Michael. It is of minor importance to myself.
I was wondering if Solids++ is evolving?
- Brian.
From: Michael Gibson
Hi Brian,
> I was wondering if Solids++ is evolving?
I don't know what their longer range plans are but no it hasn't been for a while.
- Michael
From: James (JFH)
Michael & Brian,
> I was wondering if Solids++ is evolving?
There does seems to be development happening in recent times.
According to IntegrityWare website, they have been "more than
doubling the size of the company over the past two years."
Does Solids# represent the evolution?
https://www.integrityware.com/SolidsSharp.html
Is this a kernel that MoI3d could transition to?
They have also developed a mesh to NURBS converter: "SubD-NURBS"
http://www.integrityware.com/subdnurbs.html
James
https://www.instagram.com/nodeology/
From: Michael Gibson
Hi James,
> Does Solids# represent the evolution?
>
https://www.integrityware.com/SolidsSharp.html
Sounds like it's a port of Solids++ to the C# programming language.
> Is this a kernel that MoI3d could transition to?
No, MoI does not use C#.
But maybe they will be developing Solids++ and Solids# in parallel, I don't know.
- Michael
Show messages: All
1
2-6