That's a "how many trees are in a forest?" kinda question... This comes up a lot because it's a confusing topic, but basically, multithreading will help you when you have either a lot of toolpaths to process at once or when your single toolpath can be broken up into logical pockets to be calculated simultaneously. If you're doing simple parts that primarily consist of one area, you're not going to see much benefit from multithreading. For a really quick and dirty example, using an Opti toolpath to rough this pocket: can't be effectively multithreaded because it's all one "slice," and you can't really figure out what how to cut one area without affecting another, so it all has to be processed as one chunk. In this case, clock speed is king. If the part looked like this: The top slice would be one thread, and all of the individual pockets/depths would be an individual thread. So that would (potentially) benefit from more threads

ptap$ #Canned Tap Cycle pdrlcommonb pitch = 1 / n_tap_thds$ #added 7/2/07 ADDED Peck Tapping option -09/05/2018, jmp result = newfs(17, feed) # Set for tapping Feedrate format pcan1, pbld, n$, *sgdrlref, *sgdrill, pxout, pyout, pfzout, pcout, [if peck1$ > 0, *peck1$], prdrlout, *pitch, !feed, strcantext, e$ # changed from *feed to *pitch, !feed 7/2/07 pcom_movea How I handle our Mazak's, all 41 of them

Here is how I solved it for our HCN4000. define your own variable and format it: --> fmt "F" 13 thdlead Create a routine to convert ipm to ipr: p_whichfeed # ipm to ipr for tap cycle if drillcyc$ = 3, [ thdlead = 1 / n_tap_thds$ thdlead ] else, [ *fr$ ] find where the F7.6923 is being output from , (perhaps ptap$ ?) if so, Substitute 'p_whichfeed' for '*pitch' in ptap$

For the cost of a decent laptop you can have two desktops that work better, one for at work and one for at home. Choose your processor based on this benchmark: https://www.cpubenchmark.net/singleThread.html Get a decent Quadro if you can afford it, but in my experience unless you're working on huge models Mastercam works fine on GeForce gaming cards. A $300 GeForce card will be way better than a $300 Quadro if you're budget constrained.

I'm just here fer the free coffee n bagels

My results from this benchmark 3.0 using Mastercam 2020 HLE on a Ryzen 7 3700x 3.6GHZ (4.4 ghz turbo) with a Nvidia 2060 Super gfx card, 16gb ram 3 Minutes and 58 Seconds

Ill run the benchmark 3.0 tonight in the HLE when i get to my home pc with Ryzen processor and will let you know the results if people are curious. its a just a 1300$ desktop W/ Ryzen 7 3700x 3.6GHZ (4.4 ghz turbo) with a Nvidia 2060 Super gfx card build that i got on Cyberpowerpc

From what I hear, as far as lathes go, Haas makes a pretty good VMC.

a custom drill cycle can do anything the post developer wants it to do, so I am not sure what kind of sample code you are after or what you are looking for since different applications require different custom drill cycles. What we are getting at in this topic or post is that a new toolpath is coming that puts this control at your fingertips, so instead of having an understanding of how to build a custom drill cycle in a post, in the next release all of us mastercam users now can build a custom drill cycle (whatever we might want) inside a mastercam toolpath without any need for a post edit or without any need to understand how to edit a post to add a custom drill cycle. So basically we have always had the ability to do custom drill cycles in mastercam, but before you either had to really know what you were doing with post edits or pay a post developer to do it for you, starting in 2021 the end user or Mastercam programmer has all of this ability at his fingertips right through a new and and powerful drilling toolpath. Its pretty cool all of the applications this will be able to be used for, the sky is the limit!

That is kind of my attitude I am always learning and trying new things. Don't be afraid to make mistakes and fail. Edison learned many ways not to make a light bulb before he got it correct. Had he quit like a majority of people do after he didn't get it right the first time who would have been the person to figure it out and have their name be known as the one who created the light bulb? We are not changing the world with what we do, but sometimes when you figure out or do that one thing no one thought was possible it is rewarding. I did broaching on a Vertical Mill/Turn last year for a Major Aerospace Company. I had many different ones telling me it wasn't possible and it took 3 different tools before we got it dialed in. The Verification software wasn't supporting the process correctly and I had to keep working my way through different issues, but once it was all said and done that part was beautiful and to the print. I showed them that 50 years of doing something could be improved. What I showed them has now becomes the new de-facto standard for doing the broaching. I did a project for a different Aerospace Company about 5 years ago that took a part that was taking over a 100 hours and needed 5 different machines down to one machine and no outside process to grind in the 4-8 um areas on the part. That one part was a $2.3 million ROI over 5 years verses the methods they were using before I did that work. Same company I took the roughing of a part and reduced it from 100 hours down to 40 hours. I am thankful to have been given the talent and ability the Lord has blessed me with. My advise to you is keep trying and exploring better ways in the long run you will grow in doing so.

Even after I broke it all out to just the single part program, it still misbehaved

Ahh, the good ole' MC community - it's never the software, it's always the user. Right. Just stacks and stacks of excuses from you people why your software is sub-par.