The comments that I have answers for:

fenrus: fenrus: Metric bits. 1/8" shaft 2mm cut is a nice tool. yes I can type 0.078… but still. Maybe just show always both?

If you define a metric cutter it’ll show everything in metric. All of ours are basically “inch” so we don’t have any in the default library. (I know that’s not quite what you’re asking for though)

fenrus: fenrus: CC just lost my library somehow; I added a new library, new tool. then later I picked a standard Carbide 3D tool. And now my library is not on the list. The library is back once I restart Carbide Create.

Could be a bug or it could be related to how the filters are currently set at the top of the page. If you find a repatable whay to make that happen, I’m sure we can fix it.

fenrus: fenrus: In the cutter information screen, it would be great for new users to show a picture of an endmill with the elements that make up the dimensions and label the input fields to match… something like http://www.harveytool.com/secure/Content/Images/terminology_end_mill.gif

On the Todo.

fenrus: fenrus: there’s no current way to specify stepover for 2D tools. I haven’t needed to tweak that ever but I can imagine some folks do

Stepover defaults to 50% of the diameter. We debated making this more explicit but since we don’t have ramping and adaptive clearing paths you’re always going to end up slotting somewhere in the toolpath so this seemed “safer”. We may change this in the future.

fenrus: fenrus: For the Carbide 3D tools… allow an URL for ordering, so we can click easy and open a browser tab to order more tools?

Maybe in general allow an URL for a datasheet kind of link

Carbide 3D tools do have a link in the info pane to the store but we don’t have any other datasheets online yet so this is the best we have. We won’t allow linking to third-party sites because that could be a security problem.

fenrus: fenrus: Inventory feature? We all have some bits and not others… if we can somehow flag “I have this one” as a filter

Something we talked about but we’re trying to avoid creating a database app with lots of fields. Our thought was that you could just duplicate our library and delete the ones you don’t care about. Or, create an empty library and copy the ones you do care about to it.

We worked hard to distill this down to the bare minimum that could work so we don’t confuse “normal people”.

Big picture (as Edward outlined) is that we expect that more advanced users will create their own library full of goto tools, with speeds and feeds that they like, and then be able to easily share them.

Medium term, we’re planning on a “Save as a template” command that would save a toolpath and tool into a template that can easily be applied to any job you’ve got. These templates would also be easily sharable between users (That’s the plan, we’ll see if it’s a good idea).