Include all routes for part optimization (to avoid collision during a nest)
The biggest culprit for this issue in my company is when we use our 45° miter bit, it will have a collision radius of 19mm when it's cutting 19mm deep. 3/4" one and done gap will be too large to have on a regular basis, and we only miter a few parts in the entire job, so copying a processing center just because we want those few parts not to collide with other parts is going to produce a wasteful optimization with excessive gaps between parts.
Another situation that could involve the need for this issue is when we have a lead in from outside the part border and that lead-in will essentially increase the overall footprint of that single part. If Microvellum is capable of doing fancy calculations such as "True Shape Nesting" and "Include Routes in Part Borders" I believe it's not out of the question to ask that microvellum can include all routes as a "virtual border" which is then used to place that part and avoid collision.
Am I wrong?
MVU eLearning
Grow Your Knowledge
Follow along with RJ as he takes you on a journey to build your foundational knowledge of Toolbox.