chbergmann / CurvedShapesWorkbench

FreeCAD Workbench for creating 3D shapes from 2D curves
GNU Lesser General Public License v3.0
58 stars 10 forks source link

Bnd_Box and surface creation errors with CurvedArray #27

Open ofpkubi opened 5 months ago

ofpkubi commented 5 months ago

Hi,

There are some error messages that I can't rid of using the newest version of your workbench (not manual install though) in FreeCAD 0.21.2 and 0.22dev version.

There are no visual errors, but I'm concerned that moving forward with it would break something later on.

22:48:53  16Standard_Failure Need at least two vertices, edges or wires to create loft face
22:48:53  Creation of surface is not possible !
22:48:53  <Part> ViewProviderExt.cpp(1278): Cannot compute Inventor representation for the shape of Hull__CurvedArrayErrors#CurvedArray002: Bnd_Box is void

22:48:53  <Part> ViewProviderExt.cpp(1278): Cannot compute Inventor representation for the shape of Hull__CurvedArrayErrors#CurvedArray: Bnd_Box is void

22:48:53  <Part> ViewProviderExt.cpp(1278): Cannot compute Inventor representation for the shape of Hull__CurvedArrayErrors#CurvedArray003: Bnd_Box is void

I have 3 Curved Arrays in my model.

The first one is a solid. Note that the error is the same with surface instead of body.

The second and third are just generating the cross-sections. The second has Part:ExplodeCompound and a Part:Loft on the sections. This way, I have avoided the surface creation error that I had with the first...

I know that, strictly speaking, it is not needed, but I am using Draft:Clone of sketches (to reuse) properly as the cross-section and sometimes for bounding curves too in the CurvedArray. Can this be the problem?

Here is my model (a bit complex, so I try to reproduce the problem with something simpler later on): Hull__CurvedArrayErrors.FCStd.gz

ofpkubi commented 5 months ago

Created a simpler file. Now it is without a Draft:Clone, and with only one shape.

The problem still exists.

CurvedShapesError.zip

nicocesar commented 4 months ago

I'm having the same issue. Anyone came up with a workaround?