I am struggling to diagnose the problem I have with my tool libraries. In back plot, Edit tool assembly, Edit Tool projection, etc. the tool is shown correctly inside its holder (in this example the tool has 26mm of sickout). However, when I verify the tool is shown inside of the holder what appears to be 26mm down from the top of the holder rather than the bottom. This is a new issue for me and is making verify completely useless. Anyone know how to solve this? Are my holders defined wrong?

Thanks for the helpful info here! I figured this was the case. if anyone has other ideas please let me know. We are going metric becuase 95% of our work is metric and converting the prints back and forth is a huge waist of time and energy, better just to standardize on what the customers want. Most of the tools we use are metric anyways and the ones that are not will remain inch. Better an inch endmill in a metric machine then a metric endmill in inch machine. nothing wrong with using a 12.7mm endmill but a 0.47244094inch endmill is a little less freindly.

I have some extremely complicated programs (hundreds of toolpaths and many hours invested into them) that were programmed with Mastercam configured in Inch. I now want to "switch" these programs and Mastercam files over to metric, a quick test of doing this did not work as I had hoped. Is this possible without completely reprogramming the part? Any help here would be greatly appreciated. Thanks!

Thanks for the quick reply! All fixed now. Oversight on my part forgetting about that button.....

I just started using 2023 (was on 2022) and am noticing an annoying difference in the way toolpaths are displayed. In 2022 any toolpaths that were selected with the green check were auto displayed and any that were not checked were hidden. I still Used "T" to show or hide all. Now Toolpaths will remain shown until you go back and hide them even when they are not selected, and selected toolpaths don't automatically show up. I am not liking this new workflow very much. Is there a way in settings to revert back to the old setup?

Could someone explain the limitations of Net-hooks vs using C-hooks? From what I have been reading Net-Hooks are significantly easier to learn and implement, but C-hooks are more powerful, so what are the actual limitations here? I am not a software developer, but I am willing to invest the time to learn to be able to implement some projects like this in Mastercam and other shop projects I have planned. Looking for some advice on which platform I should be investing my time into learning. The first project I am looking to tackle: We use Heidenhain controls, these controls can upload a .T, Tool database, file to the machine that contains things such as tool name, tool length, tool radius…. That I would like to export directly from Mastercam. These are basically a CSV file. I would like to develop a C-hook the reads all the tools used in a given program and auto generates a text file for me that I can load into the machine control. This will cut down a TON of data entry on the control when setting up new jobs. Would a C-hook or a Net-Hook be more appropriate for developing this?

Hello, Is there a way to delete the Default Planes such as "Right" "Left" "Front" ETC. from your file. Or more specifically can I alter the orienttion or default planes list that import in a new mastercam file? Thanks