Bambu's slicer creates non-manifold edges

Every few prints I upload in bambu will import perfectly fine but when I slice the model, bambu says the cut will creat non-manifold edges then fail to repair the issue it created. Is there a work around for this? Its driving me insane

Can you provide the .3mf file that this occurs with?

The slicer doesn’t create non-manifold edges, it detects them. The problem is with the geometry being imported.

You can try a program like MeshMixer. There’s also NetFabb, but that may be what Studio is using already…

Even if MeshMixer can’t fix it, it’ll show you where the error is. Many non-manifold issues are simply because of misplaced vertices. The polygon edges are still aligned with no actual gaps. These errors tend to slice fine. Slice it and then in the sliced preview, look at the layer/area MeshMixer said was bad. If it looks OK then just print it as is…

1 Like

If I understand correctly you are saying the problem arises AFTER CUTTING an object into parts…

Unfortunately this is ‘just’ an issue with the tools Bambu uses to make these cuts.
A simple box or cylinder can work out fine, something with a complex geometry will almost always result in non-manifold edges and other defects.
I prefer to do cuts and such in a modelling program as then I know I will get the expected results.

Usually Studio does a decent enough repair job.
But there are cases with often rather basic defects that result in a total mess.
A few empty triangles without faces are no big deal at all.
Something like multiple faces created for what should be a single, large face is a huge problem - for Studio and other repair programs.
Which face/geometry has to go?
Are the resulting defects from the removal part of the issue or new issues?
If this face has to go but the other faces produce similar defects then which is the best result?
The repair program can only guess while you in the modelling program can just delete the faces, remove a few stray lines and close the entire surface to get a watertight and error free model…

There is a really bad workaround to the problem…
You can create a primitive to cut off the top of you model at the set hight.
Then you import it again and repeat for the bottom of the model at the same height.
Unlike the model splitting this option usually won’t cause errors but take a bit of time…

1 Like