Skip to main content
D
Daniel_E12-Amethyst
12-Amethyst
August 15, 2025
Solved

Missing Toolpaths when using "Arc Only" circ_interpolation

  • August 15, 2025
  • 1 reply
  • 557 views

I'm using Creo 12.4.0

 

When changing the "circ_interpolation" factor, arc_only seems to be broken:

 

"Points Only" simulation does the cut correctly:

Daniel_E_0-1755286913681.png

 

"Arc only" simulation only does the lead-in and lead-out:

Daniel_E_1-1755287103622.png

This is for a trajectory toolpath.  But it also applies to thread milling. 

 

The "Arc Only" path cuts the lead-in/lead-out only and doesn't cut around the part like it should.  Both appear correct in the toolpath display, but on the simulation (and in real life) the paths are broken.

 

Toolpath Display for either setting:

Daniel_E_2-1755287247658.png

 

Am I doing something wrong, or is this a bug? 

 

The workaround is to choose "points only", but this makes really huge gcode files.  And if I forget to change the setting, it can crash the tools.

 

 

Best answer by Daniel_E

Thanks Martin. 

 

Here is the outcome in case by some chance it helps someone in the future.  This was an issue with my specific workstation, and in fact the specific folder my assembly resided in.

 

I worked with PTC support and discovered that it was a problem with a file in the folder that contained my manufacturing assembly.  If I do a "Save as Backup" into a new folder, and then open the file from that folder, the problem is gone.  I have thousands of files in that initial folder, so I didn't bother to figure out which one is causing the problem.

 

Moving forward, once I've created a starting mfg assembly, I plan to "save as backup" into a new folder.  This way I'm not working out of a folder with so many files in it, and the chance of interference is minimized.

1 reply

M
MartinHanak24-Ruby III
24-Ruby III
August 18, 2025

Hi,

please report the problem to PTC Support.

    D
    Daniel_E12-AmethystAuthorAnswer
    12-Amethyst
    August 18, 2025

    Thanks Martin. 

     

    Here is the outcome in case by some chance it helps someone in the future.  This was an issue with my specific workstation, and in fact the specific folder my assembly resided in.

     

    I worked with PTC support and discovered that it was a problem with a file in the folder that contained my manufacturing assembly.  If I do a "Save as Backup" into a new folder, and then open the file from that folder, the problem is gone.  I have thousands of files in that initial folder, so I didn't bother to figure out which one is causing the problem.

     

    Moving forward, once I've created a starting mfg assembly, I plan to "save as backup" into a new folder.  This way I'm not working out of a folder with so many files in it, and the chance of interference is minimized.

    Terms & ConditionsCookie settingsAccessibility statement