Based on my own personal experience I usually climb-only on hard metals and will zig zag the hell out of soft stuff like alum and plastics.

That's a big ask. I can't really think of a bullet-proof way to do it unless you can physically see where the start thread is. Even that will be sketchy at best. Not sure the application but if it were my money I'd reference the Bible where it says harder metals don't "need" 75% thread engagement and drill it out for about 60% thread engagement then hand tap it with Molly D.

Actually, at least in 2020, this only toggles the toolpath(s) on. So if the toolpaths are turned off, when you toggle this the selected ops turn on. If you toggle it again the selected ops do NOT turn off, you have to turn them off manually.

Spot-on, Beanie boy. Spot-on. Speaking strictly from a v9 perspective, MP is it's own programming language and there's not much you can't do with it. I imagine it's gotten better over the years.

We're on nethasp so that might be it. So tell me, Ron... do you drink?

With additive manufacturing they're making fully functional Colt MkIVs, jet engines, buildings and even rocket ships, just to name a few. I think it was last year or the year before that when Gibbscam released their first version of additive programming software that works along side subtractive. I didn't understand why at first but the tech is growing exponentially and getting very accurate/affordable. Gibbs was ahead of the curve on that one IMO. Not that I would ever tell them that.

No, for me it takes 8 seconds every time. Even if I literally just opened and closed it then opened it again. 8 seconds. Every. Single. Time.

It's here in Commiefornia too. We got tax breaks for developing new processes at the "old place". Once a year I would have to do a couple of worksheets with projects we did that challenged us where I would explain the project scope, the expected process, the hurdles and the new processes we developed to overcome the hurdles.

Looks like you're in 2d mode. Switch to 3d.

I'm at 2020 and was considering 2023 but.... How's 2022 compared to 2020?

Parts are classified as top secret until launch but I'll see if I can butcher one and upload it.

Your request was sketch AF and you got called on it. You just didn't like the replies. Oh, we are, Turbo. We are!

Pretty sure. I've timed this with a timer over half a dozen times and the load time is within a few milliseconds Every. Single. Time. Even when I reboot the PC it's the exact same load time. This morning I started it when I got in. Then I closed it and opened it again right after. While it was sitting for 8 seconds doing absolutely nothing I had time to open IView, press C then press Enter then drag a box around the task manager to grab a screen shot of absolutely NOTHING happening. I've written enough apps with splash screens to recognize specific behavior. I'd bet anybody a cocktail of their choice there's the equivalent of a Wait() statement in the splash screen code. And I take my cocktails VERY seriously so you KNOW I'm serious.

(I turned on all levels when I started typing this reply) Thanks Tom. I hate using this method on some of our bigger files (most of them are really big, sadly) Is there another way? I've got over a thousand levels with probably a hundred thousand entities and it's taking forever to display everything. (Still waiting) (It finished while I was taking the screen shot, about 3 or 5 minutes)

I learned the trick of analyzing entities from the chain manager, but how about for optirough and drilled holes? Dynamic Optirough: How about these drilled holes?

A security/antivirus process would attach before it started loading the process. This slowdown to zero % is after the process has loaded but before the GUI is shown.

After you open it once, close it and open it again. With such a small footprint this weak little code editor should load in a second after the first time. This is intentional. Run a task manager, expand Mastercam's process tree, then start Code Expert. Jumps for a split second then dies to 0% for 8 seconds, then jumps again to load the interface then closes the splash screen. A total and complete disregard for their customer's time and money. Pathetic if you ask me.

Who at CNC Software is patting themselves on the back making us stare at that stupid splash screen for 8 seconds instead of letting us get to work faster? If you run Code Expert 10 times a day 5 days a week for 52 weeks: That's over 6 minutes a week wasted by CNC Software's ego-maniacs. That's over 25 minutes a month wasted by CNC Software's ego-maniacs. That's over 5 hours every year WASTED by CNC Software's ego-maniacs. Someone at CNC Software is inflating their ego at a cost to us of almost $1,000.00 every stinkin' year per programmer.

Any idea why using this nethook would cause all threading operations, some morph operations and some project toolpaths to go dirty? Happens when I turn it on and off. It also seems to be lagging a lot more than it was last week. Not a biggie, they regen in a couple seconds.

Excellent point. Do you use tool's speed/feed/doc etc or the material's?

I won't go back to HP for the same reasons I don't buy Bud Lite, Starbucks and Black Rifle Coffee; Principals and morals.

Yup. Nothing worse than having two (or twenty) different versions of NC files and Mastercam files. When a change is made on the floor it has to be made upstairs too.

At my last Gibbs job I shared an office with the CEO. He eventually moved out because I kept talking swearing out loud about all the bugs in the software.

No. I didn't forget. Especially considering how well the Mac version of Gibbs worked before they went to Windows. ,.l.. And I would still reluctantly use Gibbs, I've made a good living with it. I will NEVER buy an HP or HD again. Ever.

Your Man-Card is about to get revoked again. You've been doing so good, too. Two significant firsts in my life back in the 80's were such crap I will never buy them again. One was a Harley Davidson motorcycle and the other was a Hewlett Packard computer.