[V1 - 23] Profile Cut Width Starting at line instead of at max width (solved)

[Bob La Londe]

https://www.youtube.com/watch?v=NT--Qe4u_TI

I am at a total loss.  It seems to be the same for every single profile operation that has a cut width.

Could it be a .NET issue with the latest W10 update?  

[Bob La Londe]

Wow!  I think this may qualify as a bug.  (unless its an undocumented feature)  I had modified my default style, and somehow it I got the max crossover distance set to zero.  It affected all profile operations that had not specifically had the max crossover distance changed to a specific value non default value.  If the max crossover distance was set to zero it started at the line.  If it was set to a positive value it started at the max distance of the set cut width.  

[dh42]

Hello Bob

I get the same behavior, but only on open polylines ; on closed, even with max crossover set to 0, the cut are done in the right order. (same on 0.98 and 1.0)

I'll move this post in the Bug section

++
David

[Dragonfly]

I am using this approach with open polylines extensively to mill a wide area sideways starting from outside edge of the stock. Never noticed such behavior. On Win XP and Linux. Only it will eventually require to reverse the poly to make the profile act at the correct side.
Never used zero max crossover distance though. Once I experimented with it and crashed the tool. It seems that a value of zero affects the logic behind the toolpath generation. Not sure it is a bug or a feature.

P.S. Zero crossover should not be used IMHO.

[Bob La Londe]

I am using this approach with open polylines extensively to mill a wide area sideways starting from outside edge of the stock. Never noticed such behavior. On Win XP and Linux. Only it will eventually require to reverse the poly to make the profile act at the correct side.
Never used zero max crossover distance though. Once I experimented with it and crashed the tool. It seems that a value of zero affects the logic behind the toolpath generation. Not sure it is a bug or a feature.

P.S. Zero crossover should not be used IMHO.

There are times when I used Zero Crossover to specifically not leave cross over tool marks. 

[dh42]

Hello

P.S. Zero crossover should not be used IMHO.

I always set it to 0 for engraving to avoid "bridges" between shape that are very close each from other (like text).

++
David

[kvom]

Did you modify optimization mode?  I've seen this before and solved it by trying different modes.