Rendering with cuts at stock depth

I’ve noticed that, if I set up a toolpath to cut to the stock depth (Use Stock Bottom), the render does not show the cut going through the entire piece. I’m guessing that this is by design - because I haven’t heard anyone complain about it. I end up adding .0001 to the depth in order to make it render all the way through.

  1. Is this really the way it’s supposed to work?
  2. Why?

Example:
Set Stock Depth at .5000
image
Created two objects (Rectangle and Circle)
Created Toolpath for rectangle using “Use Stock Bottom”


Created Toolpath for Circle using “Use Stock Bottom” + .0001

Render:
The Square is not cut through, but the circle is. Why?
image

  • Gary

It seems to be intentional, and I suspect that it’s both easier to calculate, and makes it clear when one is overcutting and when one is not.

Yeah…but the whole idea of saying “Use stock bottom” is to cut through the material. I certainly wouldn’t want to leave an onion skin (which is what it’s showing).

I don’t think the render should be deliberately inaccurate just to make sure one’s not overcutting (if that’s the reason). Maybe @robgrz can weigh in on the intention?

Making the hole RED to indicate overcutting would be a great suggestion - and consistent with the modeling tools of Pro.

  • Gary
1 Like

I suspect it’s a floating point error or a < instead of a <= in the code. We’ll have to check it out this week.

5 Likes

Thanks Rob! That would be great. I wish I had mentioned it earlier!

Forgot to post that this got fixed in the latest beta of CC, 623.

If all goes well this weekend, 623 will become the “Stable” release next week.

It’s great Rob…thanks!

Hey Rob…before you go stable with this release, is there any possibility that you might resolve the issue relating to the saving default name of GCode files? Current version maintains not only the last gcode directory, but the name of the .nc file. If you’re working on a new design, that old file could get overwritten if you’re not careful because it’s full path is defaulted into the name.

We had discussed this back in April (this request), which admittedly is the Cadillac of solutions and maybe overkill…but at least change the code so that it does not persist the file name beyond the current session.

In other words, within a CC session, the name is retained, however, if I close and reopen CC, it forgets the file name of the last .nc file…It would still remember the directory, but the file name would be blank.

That must be a very simple change…would you consider it?

  • Gary

definitely done this a few times…

We just made the change. When 624 is released, it’ll clear the filename but keep the directory after a file is loaded. (Which doesn’t require a lot of changes or testing)

5 Likes

Thanks!!! That’s an Alka-Seltzer fix (quick relief)!

1 Like

This topic was automatically closed after 30 days. New replies are no longer allowed.