Bug in profile operations

[IMback!]

A bug causes profiling operations to sometimes output wrong profile

[chrisb]

Confirmed here, default tolerance and curve accuracy is 0.01mm. Please add your FreeCAD infos as well. You should do that with every issue found.

OS: macOS High Sierra (10.13)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17512 (Git)
Build type: Release
Branch: master
Hash: 7b315d3a15f6c0a3e796b2bf000cb791092de079
Python version: 3.7.3
Qt version: 5.9.7
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/Germany (en_DE)

[herbk]

I have the same behavior at

OS: openSUSE Leap 15.1 (KDE//usr/share/xsessions/plasma5)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.17512 (Git) AppImage
Build type: Release
Branch: master
Hash: 7b315d3a15f6c0a3e796b2bf000cb791092de079
Python version: 3.7.3
Qt version: 5.9.7
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: German/Germany (de_DE)

and

OS: openSUSE Leap 15.1
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.Unknown
Build type: Release
Python version: 3.6.5
Qt version: 5.9.7
Coin version: 3.1.3
OCC version: 7.3.0
Locale: German/Germany (de_DE)

[herbk]

If i make a part like yours (different size) with Part WB i get a regular path.

testPart_herbk.jpg (35.58 KiB) Viewed 2330 times

[chrisb]

I recreated the PartDesign model from scratch, just to make sure I didn't miss anything. Besides the sketch, where I used the same dimesnions as IMback, I used only default values for padding, job, tool, and contour.
The path in this model shows two defects:

Bildschirmfoto 2019-08-13 um 00.34.08.png (14.38 KiB) Viewed 2315 times

[evaine23]

Has anyone found a way to fix the error in the path profile operation? I'm running into the same problem. I'm pretty new to CAD work so it might be something i'm doing wrong. If I create a sketch similar to the one above using circles rather than ellipses for the rounded ends, my path appears correct. I've tried a few different versions of FreeCAD with the same results. I have run into this problem with a more complex part that I don't think i could recreate using the part workbench.



OS: Debian GNU/Linux bullseye/sid (X-Cinnamon/cinnamon)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.18213 (Git) AppImage
Build type: Release
Branch: master
Hash: 22babc09954ac6fda9135ee71d68550921659b1c
Python version: 3.7.3
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/United States (en_US)

[IMback!]

I have ben trying to figure out why this happens, but have not made mutch headway.

[herbk]

Hi,

I have run into this problem with a more complex part that I don't think i could recreate using the part workbench.

I use Part together with Sketcher only and can create each part i need till now. Maybe sometimes a few clicks more... but less probs

[chrisb]

There is no advantage when doing it in Part WB, the same deformed path is generated.

OS: macOS High Sierra (10.13)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.18095 (Git)
Build type: Release
Branch: master
Hash: 27cb54009b57c1938f7ff97026c8b35c1688233f
Python version: 3.7.3
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/Germany (en_DE)

[herbk]

There is no advantage when doing it in Part WB, the same deformed path is generated.

You are right...

Here the error occures only if i use the Sketcher tool "Create a Conic", if i use "Arc of Parabola" i get a valid path for the part.

But: If i cuse Create a Conic, i got the error message

Code: Select all

<Part> PartFeature.cpp(191): 16Standard_Failure Index out of bound: deformedPathfromPartWB_cb#Sketch002.Vertex19

I don't understand why it starts with <Part>, i work in Sketcher...