Notifications
Clear all

Troubleshooting Slicer Gaps  

  RSS
MindwormJim
(@mindwormjim)
New Member
Troubleshooting Slicer Gaps

PrusaSlicer has decided to savage my poor robot's kneecaps and legs and I can't seem to figure out why.

Any thoughts on the matter would be greatly appreciated. Thanks!

Project File : Broken Knees

Posted : 29/05/2021 6:32 pm
Neophyl
(@neophyl)
Illustrious Member
RE: Troubleshooting Slicer Gaps

That's because your model has LOTS of errors.  I exported it from your project to do an analysis on it.  The worst type that most slicers have trouble with are non manifold parts.  Your model has 208 non manifold edges.  It also has 20059 intersecting faces, 126 zero faces, 4 zero edges, 1 non flat face and 474 thin faces.  Now the slicer copes with many of these but it cant cope with how broken the model is.  

When I load in your 3mf PS says Auto repaired 200 errors.  Its the rest that is doing it.  If you are on Windows 10 you can right click the model in PS and use the Fix through Netfabb option.  If not then you could always use the online version or another tool to fix the model.  The fix through Netfabb does appear to work.  At least I cant see any obvious missing parts any more, but its not my model so there might be parts I'm not noticing.

If its your own model then it would be best to fix the model at source.  That way you can use it as a learning experience to not make such broken models in the future.  The models geometry is terrible.  

btw I hope you aren't going to try printing it with the settings in your project.  That model definitely needs supports enabling in places.

Posted : 29/05/2021 11:49 pm
MindwormJim
(@mindwormjim)
New Member
Topic starter answered:
RE: Troubleshooting Slicer Gaps

I confess I've been a bit sloppy because the slicer doesn't care if I stick two meshes together, as long as their is a coherent inside and outside. In this case though, my sloppiness is the cause. The geometry around the knees and elbows had some extra faces on the inside left over from an earlier build that I thought had been deleted. Removing them solved the issue.

Thanks for taking a look at it!

Posted : 30/05/2021 6:39 am
Share: