Instead of editing the jump heights, try using "automatic linking" on the Linking page.. It's more betterer.

As long as you understand what MockSim is and is not, what Vericut is and is not, what CAMplete is and is not you can make educated decisions about what fits your need. MockSim doe NOT check G-Code. Tied to a Postability post it is a good solution for most things. Again, it's not fully simulating ALL the motion in your machine like M-Codes, etc... Vericut... they simulate the actual G-Code that will run in your machine. As good as your control file and machine stuff is determines how good your simulation is. By and large it is the gold standard for simulation. You can create your own machines if you desire to learn or you can buy them from Vericut, or you can hire someone to build them for you. YOu have choices. Vericut is NOT an integrated post processing solution so you will need a post either from your CAM vendor or from ICAM, or somewhere else. CAMplete... they simulate the G-Code created from their posted code. You cannot import and edited code. CAMplete IS an integrated Post Processing solution that will simulate the factory G and M-Codes. You have almost as much control over your machine as you would in a Vericut machine. You have limited machine editing capability and you cannot create your own machines. That is not an anticipated feature. The machines are factory configured meaning Matsuura, Okuma, Kern, Mazak, Haas, etc... has given their blessing on the accuracy of the models, motion, and functionality. Because CAMplete is an intagrated Post Processing solution, you have control over the code. The NC Formats are user customizable. Typically a basic NC Format is given to the customer that will run the machine well. I've got a decade and a half's experience developing NC Formats and I've got highly tuned NC Formats that take advantage of the majority of the features and functions of the Matsuuras (since that95% of what I spend my time on) and I'm adding new stuff all the time based on customer requests. Knowing the tools, knowing their strengths, weaknesses and capabilites os the key to getting the best solution for you. For me, nothing beats CAMplete. For you, Postability and Vericut may be best, for someone else, MockSim will do the job. Know your tools.

Yep, I didn't show it on the screen (my bad!) I only put it in the comments on the video... On the toolpaths type page, add those to the "avoidance geometry"selection... Then auto linking should work fine.

Don't be! Makes my day less mundane.

Lie .... make your drive geometry longer than the actual part so the plunge move is safe.

Looky there. Way easier than jump heights. It's funny to hear my methods as something from "waaaaaay waaaaay back" LOL Can't believe I didn't look over there and see Avoidance Thanks again guys

I agree with James. Been using Camplete now for a while and have had no issues. I let the install add Fusion but have never even opened it up. Camplete is well worth the investment.

Hard to tell from that angle but it would hit

Wow thanks for the video Aaron! Looking forward to training (I'm Dave Wilson BTW :hw:) Just tried this, I have some clamps to clear, I put them in as Workholding but it still won't jump them. Wopuld I have to make the clamps and the parts one m,odel for this to work?

Mastercam will use the graphics card for certain calculations during HSM (High Speed Machining toolpaths) such as Opti, Waterline, Equal Scallop, etc. via the OpenCL (note: C, not G) standard If you're benchmarking programs using the GPU, look for GridComputeServer.exe, as that's the process that handles the GPU utilization: https://my.mastercam.com/knowledgebase/opencl-troubleshooting/ In practice, the calculations being done on the GPU are so trivial for it, that you have to be really logging a lot to notice a blip. The first question people have about using GPU processing is "Why aren't you doing ALL of the calculations on the GPU then!??!?11" The truth is the majority of the time savings of using the GPU for stuff like this is taken up by the operational overhead of managing the data and handing it back and forth from the GPU.

How many serious crashes cost less than $4,500.00 to get going again? Saving even one major crash would likely pay for itself. Another post mentioned MachSim is 98% as capable as Vericut. Not sure how different that is from Camplete but seems MachSim would be an excellent investment.