Nesting Algorithm Needs Work

Nesting Algorithm Needs Work

We came to Microvellum a few years ago now and the one and only thing that has never been as good as our old system has been the nesting. Normally we just use the default output and accept it as long as it matches our production managers sheet estimate (he uses a 15 year old optiplanner software that came with our old beam saw) however every now and again he comes out with fewer sheets than we do so we have to move everything manually to match his. The below example is a perfect example of that. 3 & 1/2 sheets are saved with minimal effort, no panels being squeezed in to make it work or anything. On this particular order it's not TOO bad for us to fix up as it is only 4 patterns, but when this happens on bigger jobs, this can be so very time consuming and makes us very prone to human error.

I've tried playing around with different settings (IP and non IPP), with the attached set to best yield with no part grouping and no true shape on (when it urned true shape up, instead of batching it just seperated everything onto individual sheets but with the same patterns)

It's not a deal breaker as we get by, but it happens a lot and i'd love to stop asking the boss for a copy of his patterns all the time when we are supposed to be the ones with the superior software.


    MVU eLearning



    Are You Ready to Streamline the Way You Learn?
    Follow along with RJ as he takes you on a journey to build your foundational knowledge of Toolbox.


      Follow us on: