A Meshmixer quandry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I have a single Component of my design, which consists of a single Body (in spite of it looking like t here's tons of separate components). I choose to "Save As STL" and have the result sent out to Meshmixer.
When I first bring it up in Meshmixer it generally looks pretty good, but there are some odd RED DOTS above and below each of several BoltsWithTruncatedWashers. I've never seen anything like that. Normally red things usually only show up after doing an Analysis/Inspector operation with Meshmixer.
So II then actually do an Analysis/Inspector in Meshmixer and it reports a bunch of Pink Floating Surface Errors. Interestingly those small red dots are GONE. Here's a close-up of one of those problem parts:
The pink line is pointing at what it thinks is a "Floating Surface" error. It's pointing at that very precise spot. If I move the component around within the Meshmixer view it consistently points at that very spot. So, is it pointing at that actually spot, or is it indicating a problem with that entire Bolt Head, or maybe the entire bolt and washer? But remember, this is one solid component. There really are no bolts or washers at this stage.
So, I tried clicking on JUST this individual error. Doing so attempts to CORRECT the error.
After clicking to repair this one error:
And, lo and behold, it did indeed fix it Well, at least the error indicator went way. It's not obvious what it actually did.
BUT !! I then tried using the "Repair All" option, expecting it to repair each and every one of those identical errors on identical bolt/washer locations. And I get this:
The body is totally messed up. Some of the Bolt/Washers have been obliterated.
So, what's going on?
1) What is it likely actually detecting, considering that Bolts/Washers all LOOK perfectly fine to begin with and don't look any different after doing INDIVIDUAL, one-at-a-time, fixes.
2) Why does "Auto-Correct All" do such a horrible job when doing each one individually seems to work just fine?
3) What might I do in the original Fusion 360 design to avoid having these errors pop up in Meshmixer?