I wanted to bring attention to a pretty significant issue we're experiencing with Microvellum's Solid Model Analyzer (SMA) and see whether anyone else is experiencing the same thing.
We're currently running build 26.1.803.641 and have been experiencing issues with dado machining generated from analyzed 3D solids (we have experienced similar issues on later builds, as well). Specifically, certain dados are not being properly pocketed or extended beyond the borders, requiring our engineers to manually fix the machining either in the nest or 2D Part Editor.
We opened a support ticket over a month ago, provided exported project files and tool files, and the issue was escalated to Microvellum's development team. Unfortunately, we've been informed that there is still no estimated timeline for a resolution and that we should continue manually fixing our machining as necessary.
Here's why this is such a major concern for us:
We're preparing to begin engineering several large custom architectural millwork projects. Between these projects, we anticipate potentially having tens of thousands of dados generated through SMA.
Each wrong dado takes approximately 30 seconds to find, fix, and move onto the next.
That might not sound like much, but when you're dealing with thousands dados, those seconds add up quickly.
Our conservative estimate is already over two weeks of cumulative engineering labor just to fix machining that should be generated automatically. Realistically, the impact could be three times that amount or more, and that's before considering the potential for production errors, missed issues, or disruptions to our schedules.
For a company relying heavily on SMA to engineer complex, custom millwork, this is more than an inconvenience. It directly affects productivity, engineering capacity, project timelines, and manufacturing.
I'm curious whether other users are encountering this issue.
Are you seeing dados or internal routes that aren't properly extending or pocketing when using SMA?
Have you experienced similar behavior in other builds?
Has anyone found a reliable workaround that doesn't require manually modifying individual machining?
If you've reported this issue, have you received any updates regarding a potential fix?
I understand that software bugs happen, and I appreciate the complexity involved in developing and maintaining a platform like Microvellum. However, when an issue has the potential to consume hundreds of engineering hours across large projects, I believe it deserves some serious attention.
As like everyone using Microvellum, we have a tremendous amount invested in it and depend on it every day. I'm hoping that by bringing attention this, we can better understand how widespread this issue is, share any potential workarounds, and hopefully escalate the issue so a resolution found quickly.
If you're experiencing something similar, please chime in. The more awareness to this issue we can raise the more likely it is to move up in development.
Thanks, everyone!
