Hello all,
Wile I was playing trying to configure a this post processor I have been working on I came across this oddity using contour.
CW comp Error.png (19.84 KiB) Viewed 2360 times
If you select CW for compensation you get a circular cut into your part. See image. CCW and Compensation off give expected results. Freecad file attached.
OS: Linux Mint 17.3 Rosa
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.9822 (Git)
Build type: None
Branch: master
Hash: 0df4af4ba5e6edce825af6ecf6d024c704292633
Python version: 2.7.6
Qt version: 4.8.6
Coin version: 4.0.0a
OCC version: 6.8.0.oce-0.17
Should be fixed in the latest version - this is a side effect of the float - double changes done in Vector3D a while ago. Please let me know if this is still an issue once you updated FC.
It is not fixed in this version:
OS: Ubuntu 14.04.5 LTS
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.9842 (Git)
Build type: None
Branch: master
Hash: ea2f8731e97b8f7873094556126c42f1412e98bd
Python version: 2.7.6
Qt version: 4.8.6
Coin version: 4.0.0a
OCC version: 6.8.0.oce-0.17
but it seems to be a precision problem. If I change the radius in the sketch from 10 to 10.001 it is ok. Back to 10 not ok. 9.999 ok, and here we go: back to 10.000 is ok.
mlampert wrote:
Should be fixed in the latest version - this is a side effect of the float - double changes done in Vector3D a while ago. Please let me know if this is still an issue once you updated FC.
Still appears to be there with latest version from ppa. I think chrisb is on the right track with it being a precision problem
OS: Linux Mint 17.3 Rosa
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.9842 (Git)
Build type: None
Branch: master
Hash: ea2f8731e97b8f7873094556126c42f1412e98bd
Python version: 2.7.6
Qt version: 4.8.6
Coin version: 4.0.0a
OCC version: 6.8.0.oce-0.17
Interestingly using a face Profile instead of Contour produces the correct path. The fix I mentioned earlier does have to do with rounding - I suspect we're having more of those in the code. This is a great test piece, I'll create an issue and attach the file. Thanks for reporting, these things are hard to find, having a model like this helps!
mlampert wrote:Interestingly using a face Profile instead of Contour produces the correct path. The fix I mentioned earlier does have to do with rounding - I suspect we're having more of those in the code. This is a great test piece, I'll create an issue and attach the file. Thanks for reporting, these things are hard to find, having a model like this helps!
I was mistaken, Profile also generates the (same) wrong path if the direction is set to CW - so the path to failure is really the direction (there's probably an edge that doesn't get flipped although it should - or vice versa).
