Sure but it does not fix the bug

If previous operation uses "One other operation" setting and that "other operation" is not immediately before 3D High Speed, I get the joyous "Reporting computation error". If the "other operation" is right before 3D High Speed, it works.

This is a constant annoyance and seems completely random, as typical to mcam. When toggling between viewsheet bookmarks after file load, the viewsheet has unexpectedly switched to another WCS that has the same origin but different rotation. After setting the WCS back and re-saving the viewsheet all is working well for a while, but after a few reloads it happens again at some point.

I've been using this method for ages. Now that we have a couple of new HMC's that actually support DWO, I'm still trying to get it work the way I want (in Mazatrol world it seems to have its own will...)

Also would be nice to associate viewsheet to some reference geometry. But it'd probably take at least two Mastercam versions til it worked properly.

No Chook is needed, just a program that can read SQLite databases. It is however not a trivial task to program one - using Entity Framework's "scaffolding" process and a SQLite adapter it becomes easier; I tried that a few years back and had no problems with it.

Not enough

As a finn I've been wondering the same, so I use Sandvik Coromant's material as my reference for machining related translations. So the answer's "Overhang".

Sounds like we're all on the same page here. One of our multitasking machines is dedicated to prototyping and the occasional need of extra holders (especially the expensive hydraulic ones) makes you consider just borrow one from the standard tool rack, as they are easy to take apart and put back again. There could be many months between "standard jobs" . I would not disassemble any shrink fit holders and special tools for sure. Our tool management system has all the information required for re-assemble.

Do you disassemble and assemble tools between different jobs, or always have default tools that once assembled, are never taken apart? We are trying to reduce tooling costs and this issue came up, as a lot of assembled tools are just standing there and waiting for use.

All of sudden Analyze Distance is now showing two lines when rotating the view. Yesterday all was working without a hiccup and no Windows updates were installed since then. Did that terrible "Automatically determine Z depth" feature surreptitiously creep into analyze distance function?!

I wouldn't miss anything if that button and the dynamite one went away for good. How about adding an "isolate" button that would filter out all other operations except the ones currently selected? I use "Operation selection" often and its usability is terrible, because there is no way to isolate the selected operations. The operation tree is perhaps the oldest control still in use (?) and no amount of cosmetic changes, such as icon revamps, is going to make it better. It needs better design.

Win11 sucks is not an acceptable answer, even if it does. Is it really just me, or does nobody really use W11? This is a really annoying issue and I'm not sure if it's the cam or something with our company setup.

If there's enough demand I could try to spend some time with something that interfaces with the SQLite database using EF Core and a simple Winforms GUI for importing, exporting and mass editing tool data. I find the tool manager supplied with mcam pretty clumsy, and it's clearly not designed for power users.

I don't know where this HMC bashing is coming from, but they definitely have their place in the industry. We just invested over 3mil (in euros) in a 28 pallet 2xHMC setup with automatic tool transport system, which is used to manufacture parts that are especially designed for 4x. Sure, they are not fun to program, but someone's gotta do it. They are very sturdy machines and if you don't need the fifth axis, why bother?

Anyone else got this issue? Especially in modal dialogs (save prompt etc) left click is not working, if mcam is running.

What do you mean by "not very robust"? I've only had issues with Mirror toolpath, with which it's very easy to accidentally turn climb milling into conventional milling or left-handed threads into right-handed threads using threadmill and NCI transform, but other than that, I find it pretty robust - just lacking in features. Manual entry on first instance would also be a nice addition and being able to add or remove instances using Point transform (as in SW) would be awesome. CNC needs to give some love to HMC programmers too, it's all just fancy 5x stuff these days. And not using transform...well, if we decided to machine a second workpiece on the opposite side of the tombstone, it is certainly much faster to just use a transform op! The program may not be as fast as programming it all using separate operations (hey, how about "Optimize cut order" checkbox?), but it will save a lot of time.

I find it more surprising that sometimes clicking "cancel" will make the toolpath dirty. Cancel is cancel and should not make any changes whatsoever.

Please give us the option for toolpath transform: Force tool change on first instance only. Those who use transform extensively (HMC work) know what I'm talking about.

And now the above doesn't work anymore. For some time, it worked, now it doesn't - changing standard feed always requires regen. I can't express how frustrated I am with this, got to reprogram all thread milling ops, WTF are we paying maintenance for??

Does 2024 still have the bug where finish speed & feed (thread mill) get copied into normal speed & feed?

I wish there was an option to set top of stock relative to the depth where the tool is in contact with the edge. For many different sizes of holes/circles there will be a lot of air cutting, so you have to create different operations with different top of stock values to avoid that.

I'll wait until the third maintenance update, thank you.

Also spring pass doesn't work unless "perpendicular entry" or "start at center" is checked in lead-in. You can ask why. Also "perpendicular entry" actually means "perpendicular entry/exit"

Analyze Distance does not update the distance if you switch between two edges that are very close to each other, and because I use analyze distance a lot, it is easy to make a mistake due to this bug. Only if the cursor transitions from "edge" to "none" between the two entities, the distance is updated properly. Is this going to be fixed in 2024 ?