Invalid entities in operations? Anyone else experience this.

[Guest]

Hi,

Has anyone else experienced geometry associated with an operiation that doesn't have chains, but it shows up anyway?

 

[pro grammer]

On 3/12/2020 at 3:31 AM, Peter from S.C.C.C. said:

Hi,

Has anyone else experienced geometry associated with an operation that doesn't have chains, but it shows up anyway?

 

Not yet. But I am looking forward to it.

[Guest]

10 hours ago, pro grammer said:

Not yet. But I am looking forward to it.

It is a lot of fun, took me around 6 months to find a workaround .

[David Colin]

I'm experiencing this with 2020. It usually happens with solid chaining on my seat. I didn't find an other workaround than create a new toolpath... 

[Guest]

1 hour ago, David Colin said:

I'm experiencing this with 2020. It usually happens with solid chaining on my seat. I didn't find an other workaround than create a new toolpath... 

Yes, same, I had this issue in drilling operations, I used the api to delete the operation and copy the information and toolpath into a new operation. 

You would most likely be able to do the same, even if the api cannot create solid chains, it can most likely copy them

The SDK team said this is the only known method to mitigate these issues. 

Which operation has this issue exactly on your side?