# Depth First uncut areas

**URL:** <https://forum.grid.space/t/depth-first-uncut-areas/2187>\
**Category:** CAM\
**Created:** [October 20, 2024, 5:23am UTC](https://forum.grid.space/t/depth-first-uncut-areas/2187 "2024-10-20T05:23:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jbaz](https://forum.grid.space/user_avatar/forum.grid.space/jbaz/32/2019_2.png) [@jbaz](https://forum.grid.space/u/jbaz)\
**Post date:** [October 20, 2024, 5:23am UTC](https://forum.grid.space/t/depth-first-uncut-areas/2187/1 "2024-10-20T05:23:37Z")

</div>

Hello,  
I am loving Kiri:Moto.

I am not sure if this is a setting wrong or a bug, but I can’t seem to get Roughing to finish going to the bottom of one pocket in my design unless I uncheck Depth First. The long narrow pocket that opens to edge of the part is the problem. Milling is slower and tolerances are worse without Depth First. Here is a link to the workspace. [workspace\_Design30.kmz - Google Drive](https://drive.google.com/file/d/1H78VDp0g8Nk9zs_h3WT945oLpnNLXKfz/view?usp=sharing)

Any help is greatly appreciated.

Best Regards,  
jb

---

<div class="post-metadata">

**Author:** ![stewart](https://forum.grid.space/user_avatar/forum.grid.space/stewart/32/21_2.png) [@stewart](https://forum.grid.space/u/stewart)\
**Post date:** [October 20, 2024, 5:49am UTC](https://forum.grid.space/t/depth-first-uncut-areas/2187/2 "2024-10-20T05:49:41Z")

</div>

this does appear to be a bug with depth-first. I’m attaching a modified version of your workspace that uses pocket operations instead with depth-first disabled as a possible workaround for now.

[pocket-alternative-to-roughing.kmz](https://forum.grid.space/uploads/short-url/8nbnWyLHGaiRsXY3AyIcGC1mC89.kmz) (339.2 KB)

---

<div class="post-metadata">

**Author:** ![jbaz](https://forum.grid.space/user_avatar/forum.grid.space/jbaz/32/2019_2.png) [@jbaz](https://forum.grid.space/u/jbaz)\
**Post date:** [October 21, 2024, 3:09pm UTC](https://forum.grid.space/t/depth-first-uncut-areas/2187/3 "2024-10-21T15:09:43Z")

</div>

Thank you very much! For some reason I was under the impression that the pocket operation was not for curved features. It is very informative to see how you set up the workspace and the other settings you changed as well.

Thanks Again,  
jb

---

<div class="post-metadata">

**Author:** ![pmc](https://forum.grid.space/letter_avatar_proxy/v4/letter/p/e9c0ed/32.png) [@pmc](https://forum.grid.space/u/pmc)\
**Post date:** [November 18, 2025, 12:13am UTC](https://forum.grid.space/t/depth-first-uncut-areas/2187/4 "2025-11-18T00:13:55Z")

</div>

Here’s another example that appears similar.

A roughing op slices ok:

 ![Screenshot 2025-11-17 17.26.34](https://forum.grid.space/uploads/default/original/2X/e/e853fabf79d0f40be1cd07d620b3b396b86655c8.png)

But then a ‘preview’ the bottoms of the pockets vanish:

 ![Screenshot 2025-11-17 17.26.40](https://forum.grid.space/uploads/default/original/2X/e/eac9841d12689061d484bb24aa0bdcdd65bbac53.png)

But not with ‘depth first’ de-selected.

When it stops (depth-first selected) it looks like it stops at the level of a bunch of co-planar flats and ignores mostly-sloped surfaces below that. If I set ‘Z offset’ to lift those flats above Z=0, then preview has no trouble with the pocket bottoms below that.

[slice-ok-preview-shallow.kmz](https://forum.grid.space/uploads/short-url/6scgOIH8nTGlvWU3F6BZyDjZHAP.kmz) (188.5 KB)

In this case there aren’t a lot of pockets to jump around so breadth-first milling shouldn’t be terrible.

Depth first has been working well for long enough to forget it’s a thing. I don’t know why I thought to try without.

---

<div class="post-metadata">

**Author:** ![stewart](https://forum.grid.space/user_avatar/forum.grid.space/stewart/32/21_2.png) [@stewart](https://forum.grid.space/u/stewart)\
**Post date:** [November 18, 2025, 12:57am UTC](https://forum.grid.space/t/depth-first-uncut-areas/2187/5 "2025-11-18T00:57:40Z")

</div>

this appears to be a bug tickled by the use of `leave stock`.

I am going to rewrite most of the path planning and collision detection in the next release. it will be more reliable and support ease-down everywhere.
