A new release typically gets 4-5 patches before they call it done and move on to development of the next version. 2024 has been out for several months, it's not like all this happened in the past 23 days. I have been using 2024 since release and it has run pretty well for me.

I have the same issue but haven't found a fix. I disabled the cube for now.

Can't believe it hasn't been mentioned yet but track balls don't seem popular overall. I use an Elecom EX-G Pro and love it. Switched several years ago and have never looked back. All the extra buttons are programmed to my most used hot keys and I can easily put my pointer right where I want it (and quickly) with the ball being controlled by my thumb. I have a SpaceMouse on the left of my keyboard and I used to run an auxiliary numberpad on the left as well.

If you haven't found a solution yet, try playing with the overthickness and bitangency angle parameters. Bitangency at 170° and overthickness at .01" seems to be a solid starting point in my experience.

Can you share the download for the utility you used? I'm having trouble installing 2022 beta versions and can't figure out what's going on.

File > Configuration > Screen > View and make sure "use free mode in dynamic rotation" is checked

Byte, you are the man. Thank you so much for your time and attention in helping me get this solved. Members such as yourself are the ones who make this community such a valuable resource, and we would all be well-served to try a little harder to help one another like you do for so many.

It would be much appreciated!

Byte, Thank you for all you do for the Mastercam community! I hate to continue asking for more, but it seems at some point the 2020 functionality went away. In my testing, at least one version was compatible...maybe it has to do with the version of nethook_3.dll that you used? Would it be possible to take this latest rev and get it compiled for 2020 as well? I hope that's not too much trouble for you.

Here's the library! Thanks again! Mikron.tooldb

After using it yesterday afternoon, there are two adjustments that would be the icing on the cake if they are possible! Currently it is loading two of each tool as I have them stored as a cutting tool, and as an assembly with holder in the library. It is not seeing this as a duplicate and I would like if it was able to load the assembly only. The other thing is that it is currently not loading/displaying the assembly name which would be helpful for my programmers.

I was trying to activate it via run add-in. Added it to my QAT and it's flawless. Thank you so much!

I tried again in 2020 and 2021 with these files and I still get nothing. Event log shows that it is running and exiting same as before. Makes me think I'm missing something either functionality or setup wise. I'm confident I have the files in the right place. Beyond that, could you elaborate a little more on the intended function? I had in mind that it would read the default library for the loaded machine, and bring in all those tools so that opening the toolpath parameters would show an already-populated tool list. Is that correct?

Event log attached. I did make sure to grab both files. I made all changes in a new, empty file and restarted before testing. I tried in both 2020 and 2021. I'll wait for you to recompile and see if that helps.

Ah yes pastor Bill, preach to us about positive attitudes. Computation errors often occur when user inputs are conflicting in my experience. You have a parameter limiting/preventing another from doing what it intends to do. Could be anything from drive/avoidance geometry, cut depths, depth limits, tool geometry, etc., or some combination. This is often the case in legacy paths such as high-speed pencil and flowline at least.

Unfortunately it doesn't seem to be doing anything. I tried both files in C:\programfiles\mastercam and C:\programfiles\mastercam\chooks with no luck. I also set it to run at startup via configuration but that didn't change anything.

Big time saver here! I use a similar configuration setup for various undersizes when machining electrodes.

Yes, I started with our dealer but figured I'd ask here while I wait to hear back from them. I do appreciate the different perspectives and methods presented, and while they may not be a solution to my current project I hope to apply some of these things I've learned in the future. Thanks all!

To those suggesting the template-file idea, I appreciate the idea and it seems like it would work well in many situations. While I suppose this could accomplish what I'm looking for, it makes more sense for my people to be bringing in tools every time rather than parts every time. I truly hope not to sound unappreciative of the solutions that have been offered. The situation at hand combined with our shop work flow is causing me to have a very specific goal in mind, and not changing anything would be better than making the wrong change. The library is the default in control and machine definitions, configuration, automatically load tools when machine is read into group is on in machine def, and the specific tools I want are applied in the control definition operation defaults as Millman suggested. None of this is having the desired result.

Awesome, thank you. If it speeds things up like on the official forums, there are actually four people who will be using it if/when it comes out In all seriousness I appreciate the help and we are in no rush.

If you wouldn't mind, that would be an excellent solution!

I set it as the default in the machine definition general parameters as well as checking "automatically load tools when machine is read into a machine group" and they're still not displaying automatically. Seems like that would have the intended results and maybe it's not working properly? edit: I have it set as the default library in machine and control definitions, and as the mill tool library in configuration. Is there anywhere else I could be missing?

The library is defaulted to the one they need, but they still have to go through the "select library tool" dialogue and grab it the first time it is used in a given file. I'm trying to save them this step as they will only ever use T1, T2, and T3 out of the same library over and over again.

I thought of this, but a lot of what they program are drill cycles, and the depth is set by the point selection. When using imported operations, picking the point does not update the depth which has to be done manually. This method saves them one step but adds a different one. This is exactly what I'm trying to avoid having to do in each and every file.

Hi all, Does anyone know a way of configuring operation defaults to display multiple tools when an operation is programmed in 2020? I'm trying to set up in such a way that when programmers select a given toolpath, they are presented with a list of appropriate tools automatically without having to sort and filter through tool libraries. I currently have a library with only the tools they will need, but they still have to open the library and pick the tool the first time it is used in a file. In control definition in operation defaults, it displays as I would like with three tools shown as soon as you come to the tool page within the parameters. When programming, you still have to go to the library and bring in the tools that are not selected as the default for that operation. Is there a way to populate them here automatically? I reached out to my reseller but figured I'd ask here while I wait.