Proposal: Remove OCC offset algorithm from Pocket operation

Here's the place for discussion related to CAM/CNC and the development of the Path module.
User avatar
sliptonic
Posts: 1682
Joined: Tue Oct 25, 2011 10:46 pm

Proposal: Remove OCC offset algorithm from Pocket operation

Postby sliptonic » Wed May 10, 2017 8:35 pm

The pocket operation still has the option to use either OCC offsetting or libarea.

Libarea is the default and is far superior in almost every way.

OCC can't handle islands, often produces bad paths but does have some very crude entry logic that tries to do ramp/helical if possible. I don't use it myself and I can't even say if it actually works but It's for this reason that I've left it in place.

Now that Roivai is working on an entry dressup, I'd like to remove the OCC offset option entirely and convert pocket to use the new Path.Area. This will clean up the PathPocket module and set the stage for enhanced features.

Is anyone actually using the OCC entry at this time?
chrisb
Posts: 22362
Joined: Tue Mar 17, 2015 9:14 am

Re: Proposal: Remove OCC offset algorithm from Pocket operation

Postby chrisb » Wed May 10, 2017 10:06 pm

I would like to see it removed. I don't use it but every now and then it gives me the feeling that I should at least know the differences.
danielfalck
Posts: 395
Joined: Fri Oct 07, 2011 8:58 pm
Location: Beaverton,Oregon, USA
Contact:

Re: Proposal: Remove OCC offset algorithm from Pocket operation

Postby danielfalck » Wed May 10, 2017 11:49 pm

I vote to remove it even if just to cut down on confusion with help requests and bug reports.